Ticket #1027: doc_reformat_known_issues.txt

File doc_reformat_known_issues.txt, 6.7 KB (added by freestorm, at 2010-04-24T12:37:29Z)
Line 
1Sat Apr 24 13:41:18 Paris, Madrid (heure d'été) 2010  freestorm77@gmail.com
2  * doc_reformat_known_issues.txt
3 
4      - Added heading format begining and ending by "=="
5      - Added Index
6      - Added Title
7           
8      Note: No change are made in paragraphs content
9   
10 
11
12New patches:
13
14[doc_reformat_known_issues.txt
15freestorm77@gmail.com**20100424114118
16 Ignore-this: 9577c3965d77b7ac18698988cfa06049
17 
18     - Added heading format begining and ending by "=="
19     - Added Index
20     - Added Title
21           
22     Note: No change are made in paragraphs content
23   
24 
25] {
26hunk ./docs/known_issues.txt 3
27 = Known Issues =
28 
29+1.  Overview
30+2.  Issues in Tahoe-LAFS v1.6.0, released 2010-02-01
31+  2.1.  Potential unauthorized access by JavaScript in unrelated files
32+    2.1.1.  How to manage it
33+  2.2.  Potential disclosure of file through embedded hyperlinks or JavaScript in that file
34+    2.2.1.  How to manage it
35+  2.3.  Command-line arguments are leaked to other local users
36+    2.3.1.  How to manage it
37+  2.4.  Capabilities may be leaked to web browser phishing filter servers
38+    2.4.1.  How to manage it
39+
40+== Overview ==
41+
42 Below is a list of known issues in recent releases of Tahoe-LAFS, and how to
43 manage them.  The current version of this file can be found at
44 
45hunk ./docs/known_issues.txt 27
46 
47 http://allmydata.org/source/tahoe/trunk/docs/historical/historical_known_issues.txt
48 
49-== issues in Tahoe-LAFS v1.6.0, released 2010-02-01 ==
50+== Issues in Tahoe-LAFS v1.6.0, released 2010-02-01 ==
51 
52hunk ./docs/known_issues.txt 29
53-=== potential unauthorized access by JavaScript in unrelated files ===
54+=== Potential unauthorized access by JavaScript in unrelated files ===
55 
56 If you view a file stored in Tahoe-LAFS through a web user interface,
57 JavaScript embedded in that file might be able to access other files or
58hunk ./docs/known_issues.txt 39
59 have the ability to modify the contents of those files or directories,
60 then that script could modify or delete those files or directories.
61 
62-==== how to manage it ====
63+==== How to manage it ====
64 
65 For future versions of Tahoe-LAFS, we are considering ways to close off
66 this leakage of authority while preserving ease of use -- the discussion
67hunk ./docs/known_issues.txt 51
68 malicious JavaScript.
69 
70 
71-=== potential disclosure of file through embedded
72-hyperlinks or JavaScript in that file ===
73+=== Potential disclosure of file through embedded hyperlinks or JavaScript in that file ===
74 
75 If there is a file stored on a Tahoe-LAFS storage grid, and that file
76 gets downloaded and displayed in a web browser, then JavaScript or
77hunk ./docs/known_issues.txt 67
78 browsers, so being careful which hyperlinks you click on is not
79 sufficient to prevent this from happening.
80 
81-==== how to manage it ====
82+==== How to manage it ====
83 
84 For future versions of Tahoe-LAFS, we are considering ways to close off
85 this leakage of authority while preserving ease of use -- the discussion
86hunk ./docs/known_issues.txt 80
87 written to maliciously leak access.
88 
89 
90-=== command-line arguments are leaked to other local users ===
91+=== Command-line arguments are leaked to other local users ===
92 
93 Remember that command-line arguments are visible to other users (through
94 the 'ps' command, or the windows Process Explorer tool), so if you are
95hunk ./docs/known_issues.txt 89
96 arguments.  This includes directory caps that you set up with the "tahoe
97 add-alias" command.  Use "tahoe create-alias" for that purpose instead.
98 
99-==== how to manage it ====
100+==== How to manage it ====
101 
102 Bypass add-alias and edit the NODEDIR/private/aliases file directly, by
103 adding a line like this:
104hunk ./docs/known_issues.txt 106
105 there is a "tahoe create-alias" command that does this for you.
106 
107 
108-=== capabilities may be leaked to web browser phishing filter servers ===
109+=== Capabilities may be leaked to web browser phishing filter servers ===
110 
111 Internet Explorer includes a "phishing filter", which is turned on by
112 default, and which sends any URLs that it deems suspicious to a central
113hunk ./docs/known_issues.txt 124
114 default). Firefox briefly included a phishing filter in previous versions,
115 but abandoned it.
116 
117-==== how to manage it ====
118+==== How to manage it ====
119 
120 If you use Internet Explorer's phishing filter or a similar add-on
121 for another browser, consider either disabling it, or not using the WUI
122}
123
124Context:
125
126[docs: install.html http-equiv refresh to quickstart.html
127zooko@zooko.com**20100421165708
128 Ignore-this: 52b4b619f9dde5886ae2cd7f1f3b734b
129]
130[docs: install.html -> quickstart.html
131zooko@zooko.com**20100421155757
132 Ignore-this: 6084e203909306bed93efb09d0e6181d
133 It is not called "installing" because that implies that it is going to change the configuration of your operating system. It is not called "building" because that implies that you need developer tools like a compiler. Also I added a stern warning against looking at the "InstallDetails" wiki page, which I have renamed to "AdvancedInstall".
134]
135[Fix another typo in tahoe_storagespace munin plugin
136david-sarah@jacaranda.org**20100416220935
137 Ignore-this: ad1f7aa66b554174f91dfb2b7a3ea5f3
138]
139[Add dependency on windmill >= 1.3
140david-sarah@jacaranda.org**20100416190404
141 Ignore-this: 4437a7a464e92d6c9012926b18676211
142]
143[licensing: phrase the OpenSSL-exemption in the vocabulary of copyright instead of computer technology, and replicate the exemption from the GPL to the TGPPL
144zooko@zooko.com**20100414232521
145 Ignore-this: a5494b2f582a295544c6cad3f245e91
146]
147[munin-tahoe_storagespace
148freestorm77@gmail.com**20100221203626
149 Ignore-this: 14d6d6a587afe1f8883152bf2e46b4aa
150 
151 Plugin configuration rename
152 
153]
154[setup: add licensing declaration for setuptools (noticed by the FSF compliance folks)
155zooko@zooko.com**20100309184415
156 Ignore-this: 2dfa7d812d65fec7c72ddbf0de609ccb
157]
158[setup: fix error in licensing declaration from Shawn Willden, as noted by the FSF compliance division
159zooko@zooko.com**20100309163736
160 Ignore-this: c0623d27e469799d86cabf67921a13f8
161]
162[CREDITS to Jacob Appelbaum
163zooko@zooko.com**20100304015616
164 Ignore-this: 70db493abbc23968fcc8db93f386ea54
165]
166[desert-island-build-with-proper-versions
167jacob@appelbaum.net**20100304013858]
168[docs: a few small edits to try to guide newcomers through the docs
169zooko@zooko.com**20100303231902
170 Ignore-this: a6aab44f5bf5ad97ea73e6976bc4042d
171 These edits were suggested by my watching over Jake Appelbaum's shoulder as he completely ignored/skipped/missed install.html and also as he decided that debian.txt wouldn't help him with basic installation. Then I threw in a few docs edits that have been sitting around in my sandbox asking to be committed for months.
172]
173[TAG allmydata-tahoe-1.6.1
174david-sarah@jacaranda.org**20100228062314
175 Ignore-this: eb5f03ada8ea953ee7780e7fe068539
176]
177Patch bundle hash:
178fdd36f7db5f759ac536ab740fc019360d83bbba2