free
/
freedombone
Watch 1
Star 0
Fork 0
Code Issues 0 Pull Requests 0 Releases 0 Wiki Activity
Browse Source

Quote

Bob Mottram 9 years ago
parent
fa4bc831c5
commit
220e62ccfa
2 changed files with 20 additions and 5 deletions
Unified View Show Diff Stats
  1. 6
    0
      doc/EN/faq.org
  2. 14
    5
      website/EN/faq.html

+ 6
- 0
doc/EN/faq.org View File

94
94
95 
 Select "reset tripwire" using cursors and space bar then enter.
 95 
 Select "reset tripwire" using cursors and space bar then enter.
96 
 * Is metadata protected?
 96 
 * Is metadata protected?
97 
+#+BEGIN_QUOTE
98 
+"/We kill people based on metadata/"
99 
+
100 
+-- Michael Hayden
101 
+#+END_QUOTE
102 
+
97 
 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.
 103 
 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.
98 
 * How do I create email processing rules?
 104 
 * How do I create email processing rules?
99 
 #+BEGIN_SRC bash
 105 
 #+BEGIN_SRC bash

+ 14
- 5
website/EN/faq.html View File

3 
 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
 3 
 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
4 
 <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
 4 
 <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
5 
 <head>
 5 
 <head>
6 
-<!-- 2016-02-15 Mon 09:22 -->
6 
+<!-- 2016-02-19 Fri 18:11 -->
7 
 <meta  http-equiv="Content-Type" content="text/html;charset=utf-8" />
 7 
 <meta  http-equiv="Content-Type" content="text/html;charset=utf-8" />
8 
 <meta  name="viewport" content="width=device-width, initial-scale=1" />
 8 
 <meta  name="viewport" content="width=device-width, initial-scale=1" />
9 
 <title></title>
 9 
 <title></title>
75 
   td.org-left   { text-align: left;   }
 75 
   td.org-left   { text-align: left;   }
76 
   td.org-center { text-align: center; }
 76 
   td.org-center { text-align: center; }
77 
   dt { font-weight: bold; }
 77 
   dt { font-weight: bold; }
78 
-  .footpara:nth-child(2) { display: inline; }
79 
-  .footpara { display: block; }
78 
+  .footpara { display: inline; }
80 
   .footdef  { margin-bottom: 1em; }
 79 
   .footdef  { margin-bottom: 1em; }
81 
   .figure { padding: 1em; }
 80 
   .figure { padding: 1em; }
82 
   .figure p { text-align: center; }
 81 
   .figure p { text-align: center; }
151 
 <a name="top" id="top"></a>
 150 
 <a name="top" id="top"></a>
152 
 </div>
 151 
 </div>
153 
 <div id="content">
 152 
 <div id="content">
154 
-<div class="center">
153 
+<div class="org-center">
155
154
156 
 <div class="figure">
 155 
 <div class="figure">
157 
 <p><img src="images/logo.png" alt="logo.png" />
 156 
 <p><img src="images/logo.png" alt="logo.png" />
163 
 <h1>Frequently Asked Questions</h1>
 162 
 <h1>Frequently Asked Questions</h1>
164 
 </center>
 163 
 </center>
165
164
166 
-<div class="center">
165 
+<div class="org-center">
167 
 <table border="-1" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
 166 
 <table border="-1" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
168
167
169
168
386 
 <div id="outline-container-orgheadline9" class="outline-2">
 385 
 <div id="outline-container-orgheadline9" class="outline-2">
387 
 <h2 id="orgheadline9">Is metadata protected?</h2>
 386 
 <h2 id="orgheadline9">Is metadata protected?</h2>
388 
 <div class="outline-text-2" id="text-orgheadline9">
 387 
 <div class="outline-text-2" id="text-orgheadline9">
388 
+<blockquote>
389 
+<p>
390 
+"<i>We kill people based on metadata</i>"
391 
+</p>
392 
+
393 
+<p>
394 
+&#x2013; Michael Hayden
395 
+</p>
396 
+</blockquote>
397 
+
389 
 <p>
 398 
 <p>
390 
 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.
 399 
 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.
391 
 </p>
 400 
 </p>