free
/
freedombone
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update note about metadata

This commit is contained in:
Bob Mottram 2016-01-02 23:44:54 +00:00
parent cedfa2de48
commit 353bdc675d
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/EN/faq.org
View File

@ -77,7 +77,7 @@ sudo control
Select "reset tripwire" using cursors and space bar then enter. Select "reset tripwire" using cursors and space bar then enter.
* Is metadata protected? * Is metadata protected?
Even when using Freedombone metadata analysis by third parties is still possible. They might have a much harder time knowing what the content is, but they can potentially construct extensive dossiers based upon who communicated with your server when. Metadata leakage is a general problem with most current web systems and it is hoped that more secure technology will become available in future. But for now if metadata protection is your main concern using Freedombone on its own won't help. You may be able to use Tor Messenger to protect the metadata of XMPP chat communications to some extent. Even when using Freedombone metadata analysis by third parties is still possible. This can be mitigated by accessing your blog, or other web services, via their /onion addresses/, rather than via more conventional domain names. In that case your ISP and any government which they might be compelled to report back to will know when your system is being accessed, but not necessarily /which/ services are being accessed /or by whom/. So for instance using a Tor browser and the onion address people may be able to safely read your blog or wiki and be reasonably confident that metadata isn't being gathered about what they read (or more concisely the metadata which can be gathered by a third party may just not be very useful or personally identifiable). On the other hand if you access the system via conventional domain names and dynamic DNS then it's safe to assume that metadata can and will be collected by third parties.
* How do I create email processing rules? * How do I create email processing rules?
#+BEGIN_SRC bash #+BEGIN_SRC bash
ssh username@domainname -p 2222 ssh username@domainname -p 2222

4
website/EN/faq.html
View File

@ -3,7 +3,7 @@
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"> <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head> <head>
<!-- 2015-12-19 Sat 19:41 --> <!-- 2016-01-02 Sat 23:44 -->
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" /> <meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" /> <meta name="viewport" content="width=device-width, initial-scale=1" />
<title></title> <title></title>
@ -332,7 +332,7 @@ Select "reset tripwire" using cursors and space bar then enter.
<h2 id="orgheadline6">Is metadata protected?</h2> <h2 id="orgheadline6">Is metadata protected?</h2>
<div class="outline-text-2" id="text-orgheadline6"> <div class="outline-text-2" id="text-orgheadline6">
<p> <p>
Even when using Freedombone metadata analysis by third parties is still possible. They might have a much harder time knowing what the content is, but they can potentially construct extensive dossiers based upon who communicated with your server when. Metadata leakage is a general problem with most current web systems and it is hoped that more secure technology will become available in future. But for now if metadata protection is your main concern using Freedombone on its own won't help. You may be able to use Tor Messenger to protect the metadata of XMPP chat communications to some extent. Even when using Freedombone metadata analysis by third parties is still possible. This can be mitigated by accessing your blog, or other web services, via their <i>onion addresses</i>, rather than via more conventional domain names. In that case your ISP and any government which they might be compelled to report back to will know when your system is being accessed, but not necessarily <i>which</i> services are being accessed <i>or by whom</i>. So for instance using a Tor browser and the onion address people may be able to safely read your blog or wiki and be reasonably confident that metadata isn't being gathered about what they read (or more concisely the metadata which can be gathered by a third party may just not be very useful or personally identifiable). On the other hand if you access the system via conventional domain names and dynamic DNS then it's safe to assume that metadata can and will be collected by third parties.
</p> </p>
</div> </div>
</div> </div>