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

Quote

This commit is contained in:
Bob Mottram 2016-02-19 18:14:21 +00:00
parent fa4bc831c5
commit 220e62ccfa
2 changed files with 20 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/EN/faq.org
View File

@ -94,6 +94,12 @@ sudo control
Select "reset tripwire" using cursors and space bar then enter.
* Is metadata protected?
#+BEGIN_QUOTE
"/We kill people based on metadata/"
-- Michael Hayden
#+END_QUOTE
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?
#+BEGIN_SRC bash

19
website/EN/faq.html
View File

@ -3,7 +3,7 @@
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<!-- 2016-02-15 Mon 09:22 -->
<!-- 2016-02-19 Fri 18:11 -->
<meta http-equiv="Content-Type" content="text/html;charset=utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1" />
<title></title>
@ -75,8 +75,7 @@
td.org-left { text-align: left; }
td.org-center { text-align: center; }
dt { font-weight: bold; }
.footpara:nth-child(2) { display: inline; }
.footpara { display: block; }
.footpara { display: inline; }
.footdef { margin-bottom: 1em; }
.figure { padding: 1em; }
.figure p { text-align: center; }
@ -151,7 +150,7 @@ for the JavaScript code in this tag.
<a name="top" id="top"></a>
</div>
<div id="content">
<div class="center">
<div class="org-center">
<div class="figure">
<p><img src="images/logo.png" alt="logo.png" />
@ -163,7 +162,7 @@ for the JavaScript code in this tag.
<h1>Frequently Asked Questions</h1>
</center>
<div class="center">
<div class="org-center">
<table border="-1" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
@ -386,6 +385,16 @@ Select "reset tripwire" using cursors and space bar then enter.
<div id="outline-container-orgheadline9" class="outline-2">
<h2 id="orgheadline9">Is metadata protected?</h2>
<div class="outline-text-2" id="text-orgheadline9">
<blockquote>
<p>
"<i>We kill people based on metadata</i>"
</p>
<p>
&#x2013; Michael Hayden
</p>
</blockquote>
<p>
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>