Browse code
make it clearer that tor-security@ doesn't *need* encrypted mail
Roger Dingledine authored on 19/04/2018 00:07:35
Showing 1 changed files
| ... | ... |
@@ -102,7 +102,8 @@ |
| 102 | 102 |
<h3><a class="anchor" href="#security">Security Issues</a></h3> |
| 103 | 103 |
<p>If you've found a security issue in one of our projects or in our |
| 104 | 104 |
infrastructure, please email tor-security@lists.torproject.org. |
| 105 |
- You can get the GPG public key for the list by contacting |
|
| 105 |
+ If you want to encrypt your mail, you can get the GPG public key |
|
| 106 |
+ for the list by contacting |
|
| 106 | 107 |
tor-security-sendkey@lists.torproject.org or from |
| 107 | 108 |
pool.sks-keyservers.net. Here is the fingerprint: |
| 108 | 109 |
<blockquote><pre> |
Browse code
i think you can't finish a </ul> with a </p>
Roger Dingledine authored on 19/04/2018 00:06:15
Showing 1 changed files
| ... | ... |
@@ -83,12 +83,11 @@ |
| 83 | 83 |
|
| 84 | 84 |
<a id="twitter"></a> |
| 85 | 85 |
<h3><a class="anchor" href="#twitter">Twitter</a></h3> |
| 86 |
- <p>Follow us on Twitter: |
|
| 86 |
+ <p>Follow us on Twitter:</p> |
|
| 87 | 87 |
<ul> |
| 88 | 88 |
<li>English account: <a href="https://twitter.com/TorProject">@TorProject</a></li> |
| 89 | 89 |
<li>Farsi (Persian) account: <a href="https://twitter.com/torproject_fa">@TorProject_fa</a></li> |
| 90 | 90 |
</ul> |
| 91 |
- </p> |
|
| 92 | 91 |
|
| 93 | 92 |
<a id="bugs"></a> |
| 94 | 93 |
<h3><a class="anchor" href="#bugs">Bug Tracker</a></h3> |
Browse code
normalize whitespace
| ... | ... |
@@ -27,7 +27,7 @@ |
| 27 | 27 |
<h3><a class="anchor" href="#support">Support</a></h3> |
| 28 | 28 |
|
| 29 | 29 |
<!-- |
| 30 |
- <p><i>help@rt.torproject.org</i> is the address to use for |
|
| 30 |
+ <p><i>help@rt.torproject.org</i> is the address to use for |
|
| 31 | 31 |
questions about all things Tor, volunteering, and offering |
| 32 | 32 |
resources. This is best effort service with no guarantees. We |
| 33 | 33 |
generally respond within 48 hours. For support in other languages, |
| ... | ... |
@@ -84,49 +84,49 @@ |
| 84 | 84 |
<a id="twitter"></a> |
| 85 | 85 |
<h3><a class="anchor" href="#twitter">Twitter</a></h3> |
| 86 | 86 |
<p>Follow us on Twitter: |
| 87 |
- <ul> |
|
| 88 |
- <li>English account: <a href="https://twitter.com/TorProject">@TorProject</a></li> |
|
| 89 |
- <li>Farsi (Persian) account: <a href="https://twitter.com/torproject_fa">@TorProject_fa</a></li> |
|
| 90 |
- </ul> |
|
| 87 |
+ <ul> |
|
| 88 |
+ <li>English account: <a href="https://twitter.com/TorProject">@TorProject</a></li> |
|
| 89 |
+ <li>Farsi (Persian) account: <a href="https://twitter.com/torproject_fa">@TorProject_fa</a></li> |
|
| 90 |
+ </ul> |
|
| 91 |
+ </p> |
|
| 92 |
+ |
|
| 93 |
+ <a id="bugs"></a> |
|
| 94 |
+ <h3><a class="anchor" href="#bugs">Bug Tracker</a></h3> |
|
| 95 |
+ <p>You can report bugs other than <a href="#security">security |
|
| 96 |
+ issues</a> using our <a href="https://trac.torproject.org/projects/tor" |
|
| 97 |
+ >bug tracker</a>. Our |
|
| 98 |
+ <a href="<page getinvolved/volunteer>">volunteer page</a> has |
|
| 99 |
+ convenient links to <a href="<page getinvolved/volunteer>#Projects"> |
|
| 100 |
+ project-related queries</a>.</p> |
|
| 101 |
+ |
|
| 102 |
+ <a id="security"></a> |
|
| 103 |
+ <h3><a class="anchor" href="#security">Security Issues</a></h3> |
|
| 104 |
+ <p>If you've found a security issue in one of our projects or in our |
|
| 105 |
+ infrastructure, please email tor-security@lists.torproject.org. |
|
| 106 |
+ You can get the GPG public key for the list by contacting |
|
| 107 |
+ tor-security-sendkey@lists.torproject.org or from |
|
| 108 |
+ pool.sks-keyservers.net. Here is the fingerprint: |
|
| 109 |
+<blockquote><pre> |
|
| 110 |
+gpg --fingerprint tor-security@lists.torproject.org |
|
| 111 |
+pub 4096R/1A7BF184 2017-03-13 |
|
| 112 |
+ Key fingerprint = 8B90 4624 C5A2 8654 E453 9BC2 E135 A8B4 1A7B F184 |
|
| 113 |
+uid tor-security@lists.torproject.org <tor-security@lists.torproject.org> |
|
| 114 |
+uid tor-security@lists.torproject.org <tor-security-owner@lists.torproject.org> |
|
| 115 |
+uid tor-security@lists.torproject.org <tor-security-request@lists.torproject.org> |
|
| 116 |
+sub 4096R/C00942E4 2017-03-13 |
|
| 117 |
+</pre></blockquote> |
|
| 91 | 118 |
</p> |
| 92 | 119 |
|
| 93 |
- <a id="bugs"></a> |
|
| 94 |
- <h3><a class="anchor" href="#bugs">Bug Tracker</a></h3> |
|
| 95 |
- <p>You can report bugs other than <a href="#security">security |
|
| 96 |
- issues</a> using our <a href="https://trac.torproject.org/projects/tor" |
|
| 97 |
- >bug tracker</a>. Our |
|
| 98 |
- <a href="<page getinvolved/volunteer>">volunteer page</a> has |
|
| 99 |
- convenient links to <a href="<page getinvolved/volunteer>#Projects"> |
|
| 100 |
- project-related queries</a>.</p> |
|
| 101 |
- |
|
| 102 |
- <a id="security"></a> |
|
| 103 |
- <h3><a class="anchor" href="#security">Security Issues</a></h3> |
|
| 104 |
- <p>If you've found a security issue in one of our projects or in our |
|
| 105 |
- infrastructure, please email tor-security@lists.torproject.org. |
|
| 106 |
- You can get the GPG public key for the list by contacting |
|
| 107 |
- tor-security-sendkey@lists.torproject.org or from |
|
| 108 |
- pool.sks-keyservers.net. Here is the fingerprint: |
|
| 109 |
- <blockquote><pre> |
|
| 110 |
- gpg --fingerprint tor-security@lists.torproject.org |
|
| 111 |
- pub 4096R/1A7BF184 2017-03-13 |
|
| 112 |
- Key fingerprint = 8B90 4624 C5A2 8654 E453 9BC2 E135 A8B4 1A7B F184 |
|
| 113 |
- uid tor-security@lists.torproject.org <tor-security@lists.torproject.org> |
|
| 114 |
- uid tor-security@lists.torproject.org <tor-security-owner@lists.torproject.org> |
|
| 115 |
- uid tor-security@lists.torproject.org <tor-security-request@lists.torproject.org> |
|
| 116 |
- sub 4096R/C00942E4 2017-03-13 |
|
| 117 |
- </pre></blockquote> |
|
| 118 |
- </p> |
|
| 119 |
- |
|
| 120 |
- <a id="badrelays"></a> |
|
| 121 |
- <h3><a class="anchor" href="#badrelays">Report Bad Relays</a></h3> |
|
| 122 |
- <p>If you find a relay that you think is malicious, misconfigured, |
|
| 123 |
- or otherwise broken, please check out our |
|
| 124 |
- <a href="https://trac.torproject.org/projects/tor/wiki/doc/ReportingBadRelays"> |
|
| 125 |
- wiki page</a> and <a href="https://blog.torproject.org/how-report-bad-relays" |
|
| 126 |
- >blog post</a> on how to report it.</p> |
|
| 127 |
- |
|
| 128 |
- |
|
| 129 |
- <a id="email"></a> |
|
| 120 |
+ <a id="badrelays"></a> |
|
| 121 |
+ <h3><a class="anchor" href="#badrelays">Report Bad Relays</a></h3> |
|
| 122 |
+ <p>If you find a relay that you think is malicious, misconfigured, |
|
| 123 |
+ or otherwise broken, please check out our |
|
| 124 |
+ <a href="https://trac.torproject.org/projects/tor/wiki/doc/ReportingBadRelays"> |
|
| 125 |
+ wiki page</a> and <a href="https://blog.torproject.org/how-report-bad-relays" |
|
| 126 |
+ >blog post</a> on how to report it.</p> |
|
| 127 |
+ |
|
| 128 |
+ |
|
| 129 |
+ <a id="email"></a> |
|
| 130 | 130 |
<h3><a class="anchor" href="#email">Email</a></h3> |
| 131 | 131 |
<p>If you have Tor questions, please try to help yourself via the |
| 132 | 132 |
above support venues. Please don't use this contact address |
Browse code
Update with info about tor-security and its public key. (#9186)
kat authored on 09/01/2018 19:53:34
Showing 1 changed files
| ... | ... |
@@ -101,12 +101,21 @@ |
| 101 | 101 |
|
| 102 | 102 |
<a id="security"></a> |
| 103 | 103 |
<h3><a class="anchor" href="#security">Security Issues</a></h3> |
| 104 |
- <p>If you've found a security issue in one of our projects or our |
|
| 105 |
- infrastructure, please email the respective maintainer. You can find |
|
| 106 |
- their GPG fingerprint/key on our <a |
|
| 107 |
- href="https://db.torproject.org">developer ldap search page</a>. Due |
|
| 108 |
- to the many different projects we have, we do not offer a single |
|
| 109 |
- list for security issues.</p> |
|
| 104 |
+ <p>If you've found a security issue in one of our projects or in our |
|
| 105 |
+ infrastructure, please email tor-security@lists.torproject.org. |
|
| 106 |
+ You can get the GPG public key for the list by contacting |
|
| 107 |
+ tor-security-sendkey@lists.torproject.org or from |
|
| 108 |
+ pool.sks-keyservers.net. Here is the fingerprint: |
|
| 109 |
+ <blockquote><pre> |
|
| 110 |
+ gpg --fingerprint tor-security@lists.torproject.org |
|
| 111 |
+ pub 4096R/1A7BF184 2017-03-13 |
|
| 112 |
+ Key fingerprint = 8B90 4624 C5A2 8654 E453 9BC2 E135 A8B4 1A7B F184 |
|
| 113 |
+ uid tor-security@lists.torproject.org <tor-security@lists.torproject.org> |
|
| 114 |
+ uid tor-security@lists.torproject.org <tor-security-owner@lists.torproject.org> |
|
| 115 |
+ uid tor-security@lists.torproject.org <tor-security-request@lists.torproject.org> |
|
| 116 |
+ sub 4096R/C00942E4 2017-03-13 |
|
| 117 |
+ </pre></blockquote> |
|
| 118 |
+ </p> |
|
| 110 | 119 |
|
| 111 | 120 |
<a id="badrelays"></a> |
| 112 | 121 |
<h3><a class="anchor" href="#badrelays">Report Bad Relays</a></h3> |
Browse code
Add sections for trac (#18586) and reporting bad relays (#22412).
Add sections.
Move security section to directly follow trac section.
kat authored on 03/12/2017 20:59:18
Showing 1 changed files
| ... | ... |
@@ -16,9 +16,11 @@ |
| 16 | 16 |
<li><a href="#support">Support</a></li> |
| 17 | 17 |
<li><a href="#irc">IRC</a></li> |
| 18 | 18 |
<li><a href="#twitter">Twitter</a></li> |
| 19 |
+ <li><a href="#bugs">Bug Tracker</a></li> |
|
| 20 |
+ <li><a href="#security">Security Issues</a></li> |
|
| 21 |
+ <li><a href="#badrelays">Report Bad Relays</a></li> |
|
| 19 | 22 |
<li><a href="#email">Email</a></li> |
| 20 | 23 |
<li><a href="#mail">Mailing Address</a></li> |
| 21 |
- <li><a href="#security">Security Issues</a></li> |
|
| 22 | 24 |
</ul> |
| 23 | 25 |
|
| 24 | 26 |
<a id="support"></a> |
| ... | ... |
@@ -88,7 +90,34 @@ |
| 88 | 90 |
</ul> |
| 89 | 91 |
</p> |
| 90 | 92 |
|
| 91 |
- <a id="email"></a> |
|
| 93 |
+ <a id="bugs"></a> |
|
| 94 |
+ <h3><a class="anchor" href="#bugs">Bug Tracker</a></h3> |
|
| 95 |
+ <p>You can report bugs other than <a href="#security">security |
|
| 96 |
+ issues</a> using our <a href="https://trac.torproject.org/projects/tor" |
|
| 97 |
+ >bug tracker</a>. Our |
|
| 98 |
+ <a href="<page getinvolved/volunteer>">volunteer page</a> has |
|
| 99 |
+ convenient links to <a href="<page getinvolved/volunteer>#Projects"> |
|
| 100 |
+ project-related queries</a>.</p> |
|
| 101 |
+ |
|
| 102 |
+ <a id="security"></a> |
|
| 103 |
+ <h3><a class="anchor" href="#security">Security Issues</a></h3> |
|
| 104 |
+ <p>If you've found a security issue in one of our projects or our |
|
| 105 |
+ infrastructure, please email the respective maintainer. You can find |
|
| 106 |
+ their GPG fingerprint/key on our <a |
|
| 107 |
+ href="https://db.torproject.org">developer ldap search page</a>. Due |
|
| 108 |
+ to the many different projects we have, we do not offer a single |
|
| 109 |
+ list for security issues.</p> |
|
| 110 |
+ |
|
| 111 |
+ <a id="badrelays"></a> |
|
| 112 |
+ <h3><a class="anchor" href="#badrelays">Report Bad Relays</a></h3> |
|
| 113 |
+ <p>If you find a relay that you think is malicious, misconfigured, |
|
| 114 |
+ or otherwise broken, please check out our |
|
| 115 |
+ <a href="https://trac.torproject.org/projects/tor/wiki/doc/ReportingBadRelays"> |
|
| 116 |
+ wiki page</a> and <a href="https://blog.torproject.org/how-report-bad-relays" |
|
| 117 |
+ >blog post</a> on how to report it.</p> |
|
| 118 |
+ |
|
| 119 |
+ |
|
| 120 |
+ <a id="email"></a> |
|
| 92 | 121 |
<h3><a class="anchor" href="#email">Email</a></h3> |
| 93 | 122 |
<p>If you have Tor questions, please try to help yourself via the |
| 94 | 123 |
above support venues. Please don't use this contact address |
| ... | ... |
@@ -116,15 +145,6 @@ |
| 116 | 145 |
Seattle, WA 98194 USA<br><br> |
| 117 | 146 |
</address> |
| 118 | 147 |
|
| 119 |
- <a id="security"></a> |
|
| 120 |
- <h3><a class="anchor" href="#security">Security Issues</a></h3> |
|
| 121 |
- <p>If you've found a security issue in one of our projects or our |
|
| 122 |
- infrastructure, please email the respective maintainer. You can find |
|
| 123 |
- their GPG fingerprint/key on our <a |
|
| 124 |
- href="https://db.torproject.org">developer ldap search page</a>. Due |
|
| 125 |
- to the many different projects we have, we do not offer a single |
|
| 126 |
- list for security issues. |
|
| 127 |
- |
|
| 128 | 148 |
</div> |
| 129 | 149 |
<!-- END MAINCOL --> |
| 130 | 150 |
<div id = "sidecol"> |
Browse code
Fix grammatical error (you -> you've) in security section.
kat authored on 10/11/2017 22:50:43
Showing 1 changed files
| ... | ... |
@@ -118,7 +118,7 @@ Seattle, WA 98194 USA<br><br> |
| 118 | 118 |
|
| 119 | 119 |
<a id="security"></a> |
| 120 | 120 |
<h3><a class="anchor" href="#security">Security Issues</a></h3> |
| 121 |
- <p>If you found a security issue in one of our projects or our |
|
| 121 |
+ <p>If you've found a security issue in one of our projects or our |
|
| 122 | 122 |
infrastructure, please email the respective maintainer. You can find |
| 123 | 123 |
their GPG fingerprint/key on our <a |
| 124 | 124 |
href="https://db.torproject.org">developer ldap search page</a>. Due |
Browse code
swap in the frontdesk address for execdir and donations
see ticket 23697 for more discussion
Roger Dingledine authored on 05/10/2017 11:24:46
Showing 1 changed files
| ... | ... |
@@ -91,20 +91,20 @@ |
| 91 | 91 |
<a id="email"></a> |
| 92 | 92 |
<h3><a class="anchor" href="#email">Email</a></h3> |
| 93 | 93 |
<p>If you have Tor questions, please try to help yourself via the |
| 94 |
- above support venues. Please don't use these contact addresses |
|
| 94 |
+ above support venues. Please don't use this contact address |
|
| 95 | 95 |
for helpdesk or user requests — we all get too much mail and |
| 96 | 96 |
we won't be able to help you there.</p> |
| 97 | 97 |
|
| 98 | 98 |
<ul> |
| 99 |
- <li><i>donations@torproject.org</i> is for questions and comments about <a |
|
| 100 |
- href="https://donate.torproject.org">getting money to the developers</a>. More |
|
| 101 |
- donations means <a href="<page docs/faq>#Funding">more |
|
| 102 |
- Tor</a>. We're happy to help think about creative ways for you |
|
| 103 |
- to contribute.</li> |
|
| 104 |
- <li><i>execdir@torproject.org</i> is for questions and comments about |
|
| 105 |
- Tor the non-profit corporation: trademark questions, affiliation |
|
| 106 |
- and coordination, major gifts, contract inquiries, licensing and |
|
| 107 |
- certification, etc.</li> |
|
| 99 |
+ <li><i>frontdesk@rt.torproject.org</i> is for questions and |
|
| 100 |
+ comments about Tor the non-profit organization: funding and |
|
| 101 |
+ donations, trademark questions, |
|
| 102 |
+ affiliation and coordination, major gifts, contract inquiries, etc. |
|
| 103 |
+ Please note that email is not a great approach for safe |
|
| 104 |
+ communication, so if you need privacy consider reaching us some |
|
| 105 |
+ other way. Also note that the frontdesk is currently handled by |
|
| 106 |
+ volunteers, so please be patient. |
|
| 107 |
+ </li> |
|
| 108 | 108 |
</ul> |
| 109 | 109 |
|
| 110 | 110 |
<a id="mail"></a> |
Browse code
link to the new #tor-meeting irc channel
see
https://lists.torproject.org/pipermail/tor-project/2017-September/001459.html
for more details
Roger Dingledine authored on 28/09/2017 21:37:09
Showing 1 changed files
| ... | ... |
@@ -73,6 +73,10 @@ |
| 73 | 73 |
<li><i>#tor-project</i> - Organization discussions unrelated to |
| 74 | 74 |
software development. A great place to discuss Tor community events, |
| 75 | 75 |
outreach, translation, or website improvements.</li> |
| 76 |
+ <li><i>#tor-meeting</i> - The various Tor teams, like the network |
|
| 77 |
+ team, the browser team, the UX team, and the metrics team, hold |
|
| 78 |
+ periodic <a href="http://meetbot.debian.net/tor-meeting/">publicly |
|
| 79 |
+ logged</a> meetings in this channel.</li> |
|
| 76 | 80 |
</ul> |
| 77 | 81 |
|
| 78 | 82 |
<a id="twitter"></a> |
Browse code
Modify contact page w support
hiromipaw authored on 07/08/2017 18:48:52
Showing 1 changed files
| ... | ... |
@@ -42,8 +42,7 @@ |
| 42 | 42 |
|
| 43 | 43 |
<p>If you have questions about using Tor:</p> |
| 44 | 44 |
<ol> |
| 45 |
- <li>Read through the <a href="<page docs/faq>">FAQ</a> and the |
|
| 46 |
- <a href="<page docs/documentation>">documentation</a>.</li> |
|
| 45 |
+ <li>Check our <a href="https://trac.torproject.org/projects/tor/wiki/org/teams/CommunityTeam/Support">support wiki</a> for answers to some of the most frequently asked questions about Tor.</li> |
|
| 47 | 46 |
<li>See if your question is asked or answered on our |
| 48 | 47 |
<a href="https://tor.stackexchange.com/">StackExchange page</a>. If |
| 49 | 48 |
it isn't, please consider asking it there! Then everybody else can |
Browse code
Clean up unused donate pages
Sebastian Hahn authored on 23/11/2016 02:29:29
Showing 1 changed files
| ... | ... |
@@ -94,7 +94,7 @@ |
| 94 | 94 |
|
| 95 | 95 |
<ul> |
| 96 | 96 |
<li><i>donations@torproject.org</i> is for questions and comments about <a |
| 97 |
- href="<page donate/donate>">getting money to the developers</a>. More |
|
| 97 |
+ href="https://donate.torproject.org">getting money to the developers</a>. More |
|
| 98 | 98 |
donations means <a href="<page docs/faq>#Funding">more |
| 99 | 99 |
Tor</a>. We're happy to help think about creative ways for you |
| 100 | 100 |
to contribute.</li> |
Browse code
Update OFTC link.
Patch credit goes to cypherpunks on #19165
Sebastian Hahn authored on 21/06/2016 05:44:32
Showing 1 changed files
| ... | ... |
@@ -62,7 +62,7 @@ |
| 62 | 62 |
<a id="irc"></a> |
| 63 | 63 |
<h3><a class="anchor" href="#irc">IRC</a></h3> |
| 64 | 64 |
<p>Tor users and developers can also be found in the following channels on <a |
| 65 |
- href="http://www.oftc.net/oftc/">OFTC</a>:</p> |
|
| 65 |
+ href="https://www.oftc.net/">OFTC</a>:</p> |
|
| 66 | 66 |
|
| 67 | 67 |
<ul> |
| 68 | 68 |
<li><i>#tor</i> - For questions about using Tor (as a client, as |
Browse code
make the address more readable
Roger Dingledine authored on 23/05/2016 21:30:51
Showing 1 changed files
Browse code
change our postal address in the two remaining places
Roger Dingledine authored on 23/05/2016 20:44:55
Showing 1 changed files
| ... | ... |
@@ -106,12 +106,12 @@ |
| 106 | 106 |
|
| 107 | 107 |
<a id="mail"></a> |
| 108 | 108 |
<h3><a class="anchor" href="#mail">Mailing Address</a></h3> |
| 109 |
- <p>Should you need to reach us via old reliable mail, our mailing |
|
| 110 |
- address is: |
|
| 111 |
- <p>The Tor Project, Inc<br> |
|
| 112 |
- 7 Temple Street, Suite A<br> |
|
| 113 |
- Cambridge, MA 02139-2403 USA</p> |
|
| 114 |
- </p> |
|
| 109 |
+ <p>Should you need to reach us via old-fashioned mail, our mailing |
|
| 110 |
+ address is:</p> |
|
| 111 |
+<address>The Tor Project<br> |
|
| 112 |
+217 1st Ave South #4903<br> |
|
| 113 |
+Seattle, WA 98194 USA |
|
| 114 |
+</address> |
|
| 115 | 115 |
|
| 116 | 116 |
<a id="security"></a> |
| 117 | 117 |
<h3><a class="anchor" href="#security">Security Issues</a></h3> |
Browse code
move email farther down the page (suggested by kate)
Roger Dingledine authored on 18/04/2016 08:10:37
Showing 1 changed files
| ... | ... |
@@ -14,9 +14,9 @@ |
| 14 | 14 |
<h2>Tor: Contact</h2> |
| 15 | 15 |
<ul> |
| 16 | 16 |
<li><a href="#support">Support</a></li> |
| 17 |
- <li><a href="#email">Email</a></li> |
|
| 18 | 17 |
<li><a href="#irc">IRC</a></li> |
| 19 | 18 |
<li><a href="#twitter">Twitter</a></li> |
| 19 |
+ <li><a href="#email">Email</a></li> |
|
| 20 | 20 |
<li><a href="#mail">Mailing Address</a></li> |
| 21 | 21 |
<li><a href="#security">Security Issues</a></li> |
| 22 | 22 |
</ul> |
| ... | ... |
@@ -59,25 +59,6 @@ |
| 59 | 59 |
<p>If you find your answer, please stick around to contribute back |
| 60 | 60 |
and help others who were once in your position.</p> |
| 61 | 61 |
|
| 62 |
- <a id="email"></a> |
|
| 63 |
- <h3><a class="anchor" href="#email">Email</a></h3> |
|
| 64 |
- <p>If you have Tor questions, please try to help yourself via the |
|
| 65 |
- above support venues. Please don't use these contact addresses |
|
| 66 |
- for helpdesk or user requests — we all get too much mail and |
|
| 67 |
- we won't be able to help you there.</p> |
|
| 68 |
- |
|
| 69 |
- <ul> |
|
| 70 |
- <li><i>donations@torproject.org</i> is for questions and comments about <a |
|
| 71 |
- href="<page donate/donate>">getting money to the developers</a>. More |
|
| 72 |
- donations means <a href="<page docs/faq>#Funding">more |
|
| 73 |
- Tor</a>. We're happy to help think about creative ways for you |
|
| 74 |
- to contribute.</li> |
|
| 75 |
- <li><i>execdir@torproject.org</i> is for questions and comments about |
|
| 76 |
- Tor the non-profit corporation: trademark questions, affiliation |
|
| 77 |
- and coordination, major gifts, contract inquiries, licensing and |
|
| 78 |
- certification, etc.</li> |
|
| 79 |
- </ul> |
|
| 80 |
- |
|
| 81 | 62 |
<a id="irc"></a> |
| 82 | 63 |
<h3><a class="anchor" href="#irc">IRC</a></h3> |
| 83 | 64 |
<p>Tor users and developers can also be found in the following channels on <a |
| ... | ... |
@@ -104,6 +85,25 @@ |
| 104 | 85 |
</ul> |
| 105 | 86 |
</p> |
| 106 | 87 |
|
| 88 |
+ <a id="email"></a> |
|
| 89 |
+ <h3><a class="anchor" href="#email">Email</a></h3> |
|
| 90 |
+ <p>If you have Tor questions, please try to help yourself via the |
|
| 91 |
+ above support venues. Please don't use these contact addresses |
|
| 92 |
+ for helpdesk or user requests — we all get too much mail and |
|
| 93 |
+ we won't be able to help you there.</p> |
|
| 94 |
+ |
|
| 95 |
+ <ul> |
|
| 96 |
+ <li><i>donations@torproject.org</i> is for questions and comments about <a |
|
| 97 |
+ href="<page donate/donate>">getting money to the developers</a>. More |
|
| 98 |
+ donations means <a href="<page docs/faq>#Funding">more |
|
| 99 |
+ Tor</a>. We're happy to help think about creative ways for you |
|
| 100 |
+ to contribute.</li> |
|
| 101 |
+ <li><i>execdir@torproject.org</i> is for questions and comments about |
|
| 102 |
+ Tor the non-profit corporation: trademark questions, affiliation |
|
| 103 |
+ and coordination, major gifts, contract inquiries, licensing and |
|
| 104 |
+ certification, etc.</li> |
|
| 105 |
+ </ul> |
|
| 106 |
+ |
|
| 107 | 107 |
<a id="mail"></a> |
| 108 | 108 |
<h3><a class="anchor" href="#mail">Mailing Address</a></h3> |
| 109 | 109 |
<p>Should you need to reach us via old reliable mail, our mailing |
Browse code
kate points out that press is already at the top of the page
Roger Dingledine authored on 18/04/2016 08:08:35
Showing 1 changed files
| ... | ... |
@@ -72,7 +72,6 @@ |
| 72 | 72 |
donations means <a href="<page docs/faq>#Funding">more |
| 73 | 73 |
Tor</a>. We're happy to help think about creative ways for you |
| 74 | 74 |
to contribute.</li> |
| 75 |
- <li><i>press@torproject.org</i> is for press/media.</li> |
|
| 76 | 75 |
<li><i>execdir@torproject.org</i> is for questions and comments about |
| 77 | 76 |
Tor the non-profit corporation: trademark questions, affiliation |
| 78 | 77 |
and coordination, major gifts, contract inquiries, licensing and |
Browse code
be more explicit that users should ask questions on stackexchange
Roger Dingledine authored on 17/04/2016 07:12:00
Showing 1 changed files
| ... | ... |
@@ -45,7 +45,9 @@ |
| 45 | 45 |
<li>Read through the <a href="<page docs/faq>">FAQ</a> and the |
| 46 | 46 |
<a href="<page docs/documentation>">documentation</a>.</li> |
| 47 | 47 |
<li>See if your question is asked or answered on our |
| 48 |
- <a href="https://tor.stackexchange.com/">StackExchange page</a>.</li> |
|
| 48 |
+ <a href="https://tor.stackexchange.com/">StackExchange page</a>. If |
|
| 49 |
+ it isn't, please consider asking it there! Then everybody else can |
|
| 50 |
+ benefit from your question and the answer to it.</li> |
|
| 49 | 51 |
<li>Join the <a href="#irc">#tor irc channel</a>, state the issue, |
| 50 | 52 |
and wait patiently for help.</li> |
| 51 | 53 |
<li>Read through the archives of the |
| ... | ... |
@@ -60,7 +62,7 @@ |
| 60 | 62 |
<a id="email"></a> |
| 61 | 63 |
<h3><a class="anchor" href="#email">Email</a></h3> |
| 62 | 64 |
<p>If you have Tor questions, please try to help yourself via the |
| 63 |
- above support venues. Please don't use the below contact addresses |
|
| 65 |
+ above support venues. Please don't use these contact addresses |
|
| 64 | 66 |
for helpdesk or user requests — we all get too much mail and |
| 65 | 67 |
we won't be able to help you there.</p> |
| 66 | 68 |
|
Browse code
get rid of the orphan "telephone" header
(and also the commented out text, since it's unlikely we're going to
be turning that back on anytime soon)
Roger Dingledine authored on 16/04/2016 21:35:34
Showing 1 changed files
| ... | ... |
@@ -17,7 +17,6 @@ |
| 17 | 17 |
<li><a href="#email">Email</a></li> |
| 18 | 18 |
<li><a href="#irc">IRC</a></li> |
| 19 | 19 |
<li><a href="#twitter">Twitter</a></li> |
| 20 |
- <li><a href="#phone">Telephone</a></li> |
|
| 21 | 20 |
<li><a href="#mail">Mailing Address</a></li> |
| 22 | 21 |
<li><a href="#security">Security Issues</a></li> |
| 23 | 22 |
</ul> |
| ... | ... |
@@ -104,16 +103,6 @@ |
| 104 | 103 |
</ul> |
| 105 | 104 |
</p> |
| 106 | 105 |
|
| 107 |
-<!-- |
|
| 108 |
- <a id="phone"></a> |
|
| 109 |
- <h3><a class="anchor" href="#phone">Telephone</a></h3> |
|
| 110 |
- <p>Please be aware that your |
|
| 111 |
- phone company and ours (and everyone in between) could listen to |
|
| 112 |
- the call. Please do not call for technical support. Instead, email |
|
| 113 |
- <em>help@rt.torproject.org</em>. Technical support phone calls are not |
|
| 114 |
- returned.</p> |
|
| 115 |
- |
|
| 116 | 106 |
<a id="mail"></a> |
| 117 | 107 |
<h3><a class="anchor" href="#mail">Mailing Address</a></h3> |
| 118 | 108 |
<p>Should you need to reach us via old reliable mail, our mailing |
Browse code
try to make it clearer that execdir/donations/etc are not helpdesk
Roger Dingledine authored on 11/04/2016 07:02:33
Showing 1 changed files
| ... | ... |
@@ -61,7 +61,9 @@ |
| 61 | 61 |
<a id="email"></a> |
| 62 | 62 |
<h3><a class="anchor" href="#email">Email</a></h3> |
| 63 | 63 |
<p>If you have Tor questions, please try to help yourself via the |
| 64 |
- above support venues.</p> |
|
| 64 |
+ above support venues. Please don't use the below contact addresses |
|
| 65 |
+ for helpdesk or user requests — we all get too much mail and |
|
| 66 |
+ we won't be able to help you there.</p> |
|
| 65 | 67 |
|
| 66 | 68 |
<ul> |
| 67 | 69 |
<li><i>donations@torproject.org</i> is for questions and comments about <a |
Browse code
make clear that #tor is for tor questions, not "discussion"
Roger Dingledine authored on 11/03/2016 22:43:06
Showing 1 changed files
| ... | ... |
@@ -82,14 +82,14 @@ |
| 82 | 82 |
href="http://www.oftc.net/oftc/">OFTC</a>:</p> |
| 83 | 83 |
|
| 84 | 84 |
<ul> |
| 85 |
- <li><i>#tor</i> - User and relay operation discussions. Having trouble |
|
| 86 |
- running Tor or a question for other Tor users? Then this is the spot for |
|
| 87 |
- you.</li> |
|
| 85 |
+ <li><i>#tor</i> - For questions about using Tor (as a client, as |
|
| 86 |
+ a relay, as an onion service). Having trouble running Tor or have |
|
| 87 |
+ a question for other Tor users? Then this is the spot for you.</li> |
|
| 88 | 88 |
<li><i>#tor-dev</i> - Channel for people who want to do development. |
| 89 | 89 |
Discussions about Tor-related coding, protocols, and <a href="<page |
| 90 | 90 |
getinvolved/volunteer>">project ideas</a> are all welcome.</li> |
| 91 |
- <li><i>#tor-project</i> - Organization discussions unrelated to |
|
| 92 |
- software development. A great place to discuss Tor community events, |
|
| 91 |
+ <li><i>#tor-project</i> - Organization discussions unrelated to |
|
| 92 |
+ software development. A great place to discuss Tor community events, |
|
| 93 | 93 |
outreach, translation, or website improvements.</li> |
| 94 | 94 |
</ul> |
| 95 | 95 |
|
Browse code
resurrect the support section. remove the telephone section.
Roger Dingledine authored on 11/03/2016 22:31:17
Showing 1 changed files
| ... | ... |
@@ -22,10 +22,10 @@ |
| 22 | 22 |
<li><a href="#security">Security Issues</a></li> |
| 23 | 23 |
</ul> |
| 24 | 24 |
|
| 25 |
- <!-- |
|
| 26 | 25 |
<a id="support"></a> |
| 27 | 26 |
<h3><a class="anchor" href="#support">Support</a></h3> |
| 28 | 27 |
|
| 28 |
+ <!-- |
|
| 29 | 29 |
<p><i>help@rt.torproject.org</i> is the address to use for |
| 30 | 30 |
questions about all things Tor, volunteering, and offering |
| 31 | 31 |
resources. This is best effort service with no guarantees. We |
| ... | ... |
@@ -41,19 +41,29 @@ |
| 41 | 41 |
</ul> |
| 42 | 42 |
--> |
| 43 | 43 |
|
| 44 |
+ <p>If you have questions about using Tor:</p> |
|
| 45 |
+ <ol> |
|
| 46 |
+ <li>Read through the <a href="<page docs/faq>">FAQ</a> and the |
|
| 47 |
+ <a href="<page docs/documentation>">documentation</a>.</li> |
|
| 48 |
+ <li>See if your question is asked or answered on our |
|
| 49 |
+ <a href="https://tor.stackexchange.com/">StackExchange page</a>.</li> |
|
| 50 |
+ <li>Join the <a href="#irc">#tor irc channel</a>, state the issue, |
|
| 51 |
+ and wait patiently for help.</li> |
|
| 52 |
+ <li>Read through the archives of the |
|
| 53 |
+ <a href="<page docs/documentation>#MailingLists">mailing lists</a> |
|
| 54 |
+ to see if anybody else has raised your issue recently. Note that |
|
| 55 |
+ you need to subscribe to the mailing lists before you can post.</li> |
|
| 56 |
+ </ol> |
|
| 57 |
+ |
|
| 58 |
+ <p>If you find your answer, please stick around to contribute back |
|
| 59 |
+ and help others who were once in your position.</p> |
|
| 60 |
+ |
|
| 44 | 61 |
<a id="email"></a> |
| 45 | 62 |
<h3><a class="anchor" href="#email">Email</a></h3> |
| 46 |
- <!-- Please email <ew>help@rt.torproject.org</em> for general questions. |
|
| 47 |
- |
|
| 48 |
- A few other addresses are more specific: --> |
|
| 63 |
+ <p>If you have Tor questions, please try to help yourself via the |
|
| 64 |
+ above support venues.</p> |
|
| 49 | 65 |
|
| 50 | 66 |
<ul> |
| 51 |
- <li><i>tor-talk@lists.torproject.org</i> is for all discussion |
|
| 52 |
- about theory, design, development, and use of Onion Routing. |
|
| 53 |
- <i>tor-dev@lists.torproject.org</i> is for Tor research and |
|
| 54 |
- development. For both of these <a href="<page |
|
| 55 |
- docs/documentation>#MailingLists">mailing lists</a>, |
|
| 56 |
- you must subscribe before you can post.</li> |
|
| 57 | 67 |
<li><i>donations@torproject.org</i> is for questions and comments about <a |
| 58 | 68 |
href="<page donate/donate>">getting money to the developers</a>. More |
| 59 | 69 |
donations means <a href="<page docs/faq>#Funding">more |
| ... | ... |
@@ -92,6 +102,7 @@ |
| 92 | 102 |
</ul> |
| 93 | 103 |
</p> |
| 94 | 104 |
|
| 105 |
+<!-- |
|
| 95 | 106 |
<a id="phone"></a> |
| 96 | 107 |
<h3><a class="anchor" href="#phone">Telephone</a></h3> |
| 97 | 108 |
<p>Please be aware that your |
| ... | ... |
@@ -99,6 +110,7 @@ |
| 99 | 110 |
the call. Please do not call for technical support. Instead, email |
| 100 | 111 |
<em>help@rt.torproject.org</em>. Technical support phone calls are not |
| 101 | 112 |
returned.</p> |
| 113 |
+--> |
|
| 102 | 114 |
|
| 103 | 115 |
<a id="mail"></a> |
| 104 | 116 |
<h3><a class="anchor" href="#mail">Mailing Address</a></h3> |
Browse code
Update Contact page
- Remove references to RT until we have the support desk back
- Remove the phone number for press queries since it is no longer active
- Stop advertising the #nottor channel
Sukhbir Singh authored on 09/03/2016 14:08:18
• Sebastian Hahn committed on 09/03/2016 14:24:20
Showing 1 changed files
| ... | ... |
@@ -22,6 +22,7 @@ |
| 22 | 22 |
<li><a href="#security">Security Issues</a></li> |
| 23 | 23 |
</ul> |
| 24 | 24 |
|
| 25 |
+ <!-- |
|
| 25 | 26 |
<a id="support"></a> |
| 26 | 27 |
<h3><a class="anchor" href="#support">Support</a></h3> |
| 27 | 28 |
|
| ... | ... |
@@ -38,12 +39,13 @@ |
| 38 | 39 |
<li><i>help-fr@rt.torproject.org</i> for French</li> |
| 39 | 40 |
<li><i>help-zh@rt.torproject.org</i> for Mandarin</li> |
| 40 | 41 |
</ul> |
| 42 |
+ --> |
|
| 41 | 43 |
|
| 42 | 44 |
<a id="email"></a> |
| 43 | 45 |
<h3><a class="anchor" href="#email">Email</a></h3> |
| 44 |
- Please email <ew>help@rt.torproject.org</em> for general questions. |
|
| 46 |
+ <!-- Please email <ew>help@rt.torproject.org</em> for general questions. |
|
| 45 | 47 |
|
| 46 |
- A few other addresses are more specific: |
|
| 48 |
+ A few other addresses are more specific: --> |
|
| 47 | 49 |
|
| 48 | 50 |
<ul> |
| 49 | 51 |
<li><i>tor-talk@lists.torproject.org</i> is for all discussion |
| ... | ... |
@@ -79,8 +81,6 @@ |
| 79 | 81 |
<li><i>#tor-project</i> - Organization discussions unrelated to |
| 80 | 82 |
software development. A great place to discuss Tor community events, |
| 81 | 83 |
outreach, translation, or website improvements.</li> |
| 82 |
- <li><i>#nottor</i> - This is where Tor people hang out to talk about |
|
| 83 |
- stuff that is not related to Tor.</li> |
|
| 84 | 84 |
</ul> |
| 85 | 85 |
|
| 86 | 86 |
<a id="twitter"></a> |
| ... | ... |
@@ -100,8 +100,6 @@ |
| 100 | 100 |
<em>help@rt.torproject.org</em>. Technical support phone calls are not |
| 101 | 101 |
returned.</p> |
| 102 | 102 |
|
| 103 |
- <p>For press inquiries only, please call +1-617-902-0208.</p> |
|
| 104 |
- |
|
| 105 | 103 |
<a id="mail"></a> |
| 106 | 104 |
<h3><a class="anchor" href="#mail">Mailing Address</a></h3> |
| 107 | 105 |
<p>Should you need to reach us via old reliable mail, our mailing |
Browse code
that was silly
Sebastian Hahn authored on 28/12/2015 10:22:29
Showing 1 changed files
| ... | ... |
@@ -53,7 +53,7 @@ |
| 53 | 53 |
docs/documentation>#MailingLists">mailing lists</a>, |
| 54 | 54 |
you must subscribe before you can post.</li> |
| 55 | 55 |
<li><i>donations@torproject.org</i> is for questions and comments about <a |
| 56 |
- href="<page donate/donate-1>">getting money to the developers</a>. More |
|
| 56 |
+ href="<page donate/donate>">getting money to the developers</a>. More |
|
| 57 | 57 |
donations means <a href="<page docs/faq>#Funding">more |
| 58 | 58 |
Tor</a>. We're happy to help think about creative ways for you |
| 59 | 59 |
to contribute.</li> |
Browse code
add stretch to debian download page
Sebastian Hahn authored on 28/12/2015 10:06:01
Showing 1 changed files
| ... | ... |
@@ -53,7 +53,7 @@ |
| 53 | 53 |
docs/documentation>#MailingLists">mailing lists</a>, |
| 54 | 54 |
you must subscribe before you can post.</li> |
| 55 | 55 |
<li><i>donations@torproject.org</i> is for questions and comments about <a |
| 56 |
- href="<page donate/donate>">getting money to the developers</a>. More |
|
| 56 |
+ href="<page donate/donate-1>">getting money to the developers</a>. More |
|
| 57 | 57 |
donations means <a href="<page docs/faq>#Funding">more |
| 58 | 58 |
Tor</a>. We're happy to help think about creative ways for you |
| 59 | 59 |
to contribute.</li> |
Browse code
Remove the bad-relays ml from contact page
Very sensible request from phw, we should direct actual reporters of
issues to that list rather than attracting everyone to it who skims the
page.
Sebastian Hahn authored on 06/09/2015 20:38:41
Showing 1 changed files
| ... | ... |
@@ -62,9 +62,6 @@ |
| 62 | 62 |
Tor the non-profit corporation: trademark questions, affiliation |
| 63 | 63 |
and coordination, major gifts, contract inquiries, licensing and |
| 64 | 64 |
certification, etc.</li> |
| 65 |
- <li><i>bad-relays@lists.torproject.org</i> is for reporting exit relays |
|
| 66 |
- observed to be misconfigured or malicious. (This is not the same as bad |
|
| 67 |
- users!)</li> |
|
| 68 | 65 |
</ul> |
| 69 | 66 |
|
| 70 | 67 |
<a id="irc"></a> |
Browse code
Do not mention the phone on the website; it is being deprecated for now.
Nick Mathewson authored on 30/04/2015 22:39:09
Showing 1 changed files
| ... | ... |
@@ -97,13 +97,13 @@ |
| 97 | 97 |
|
| 98 | 98 |
<a id="phone"></a> |
| 99 | 99 |
<h3><a class="anchor" href="#phone">Telephone</a></h3> |
| 100 |
- <p>The Tor office is reachable at +1-781-948-1982. Please be aware that your |
|
| 100 |
+ <p>Please be aware that your |
|
| 101 | 101 |
phone company and ours (and everyone in between) could listen to |
| 102 | 102 |
the call. Please do not call for technical support. Instead, email |
| 103 | 103 |
<em>help@rt.torproject.org</em>. Technical support phone calls are not |
| 104 | 104 |
returned.</p> |
| 105 | 105 |
|
| 106 |
- <p>For press inquiries, please call +1-617-902-0208.</p> |
|
| 106 |
+ <p>For press inquiries only, please call +1-617-902-0208.</p> |
|
| 107 | 107 |
|
| 108 | 108 |
<a id="mail"></a> |
| 109 | 109 |
<h3><a class="anchor" href="#mail">Mailing Address</a></h3> |
Browse code
adding @torproject_fa to the twitter section
Nima Fatemi authored on 29/04/2015 19:42:43
Showing 1 changed files
| ... | ... |
@@ -88,7 +88,12 @@ |
| 88 | 88 |
|
| 89 | 89 |
<a id="twitter"></a> |
| 90 | 90 |
<h3><a class="anchor" href="#twitter">Twitter</a></h3> |
| 91 |
- <p>Follow <a href="https://twitter.com/torproject">@TorProject</a> on Twitter!</p> |
|
| 91 |
+ <p>Follow us on Twitter: |
|
| 92 |
+ <ul> |
|
| 93 |
+ <li>English account: <a href="https://twitter.com/TorProject">@TorProject</a></li> |
|
| 94 |
+ <li>Farsi (Persian) account: <a href="https://twitter.com/torproject_fa">@TorProject_fa</a></li> |
|
| 95 |
+ </ul> |
|
| 96 |
+ </p> |
|
| 92 | 97 |
|
| 93 | 98 |
<a id="phone"></a> |
| 94 | 99 |
<h3><a class="anchor" href="#phone">Telephone</a></h3> |
Browse code
Switch press contact number away from main office number.
Nick Mathewson authored on 16/04/2015 18:47:24
Showing 1 changed files
| ... | ... |
@@ -94,10 +94,12 @@ |
| 94 | 94 |
<h3><a class="anchor" href="#phone">Telephone</a></h3> |
| 95 | 95 |
<p>The Tor office is reachable at +1-781-948-1982. Please be aware that your |
| 96 | 96 |
phone company and ours (and everyone in between) could listen to |
| 97 |
- the call. Please do not call for technical support, rather email |
|
| 97 |
+ the call. Please do not call for technical support. Instead, email |
|
| 98 | 98 |
<em>help@rt.torproject.org</em>. Technical support phone calls are not |
| 99 | 99 |
returned.</p> |
| 100 | 100 |
|
| 101 |
+ <p>For press inquiries, please call +1-617-902-0208.</p> |
|
| 102 |
+ |
|
| 101 | 103 |
<a id="mail"></a> |
| 102 | 104 |
<h3><a class="anchor" href="#mail">Mailing Address</a></h3> |
| 103 | 105 |
<p>Should you need to reach us via old reliable mail, our mailing |
Browse code
point to the press list in two places
Roger Dingledine authored on 02/04/2015 11:48:22
Showing 1 changed files
| ... | ... |
@@ -57,13 +57,14 @@ |
| 57 | 57 |
donations means <a href="<page docs/faq>#Funding">more |
| 58 | 58 |
Tor</a>. We're happy to help think about creative ways for you |
| 59 | 59 |
to contribute.</li> |
| 60 |
- <li><i>execdir@torproject.org</i> is for press/media, questions and comments about |
|
| 60 |
+ <li><i>press@torproject.org</i> is for press/media.</li> |
|
| 61 |
+ <li><i>execdir@torproject.org</i> is for questions and comments about |
|
| 61 | 62 |
Tor the non-profit corporation: trademark questions, affiliation |
| 62 | 63 |
and coordination, major gifts, contract inquiries, licensing and |
| 63 | 64 |
certification, etc.</li> |
| 64 | 65 |
<li><i>bad-relays@lists.torproject.org</i> is for reporting exit relays |
| 65 |
- observed to be misconfigured or malicious. You do not need to subscribe |
|
| 66 |
- before posting.</li> |
|
| 66 |
+ observed to be misconfigured or malicious. (This is not the same as bad |
|
| 67 |
+ users!)</li> |
|
| 67 | 68 |
</ul> |
| 68 | 69 |
|
| 69 | 70 |
<a id="irc"></a> |
Browse code
Add note about security issues
Sebastian Hahn authored on 08/02/2015 18:27:53
Showing 1 changed files
| ... | ... |
@@ -19,6 +19,7 @@ |
| 19 | 19 |
<li><a href="#twitter">Twitter</a></li> |
| 20 | 20 |
<li><a href="#phone">Telephone</a></li> |
| 21 | 21 |
<li><a href="#mail">Mailing Address</a></li> |
| 22 |
+ <li><a href="#security">Security Issues</a></li> |
|
| 22 | 23 |
</ul> |
| 23 | 24 |
|
| 24 | 25 |
<a id="support"></a> |
| ... | ... |
@@ -105,6 +106,15 @@ |
| 105 | 106 |
Cambridge, MA 02139-2403 USA</p> |
| 106 | 107 |
</p> |
| 107 | 108 |
|
| 109 |
+ <a id="security"></a> |
|
| 110 |
+ <h3><a class="anchor" href="#security">Security Issues</a></h3> |
|
| 111 |
+ <p>If you found a security issue in one of our projects or our |
|
| 112 |
+ infrastructure, please email the respective maintainer. You can find |
|
| 113 |
+ their GPG fingerprint/key on our <a |
|
| 114 |
+ href="https://db.torproject.org">developer ldap search page</a>. Due |
|
| 115 |
+ to the many different projects we have, we do not offer a single |
|
| 116 |
+ list for security issues. |
|
| 117 |
+ |
|
| 108 | 118 |
</div> |
| 109 | 119 |
<!-- END MAINCOL --> |
| 110 | 120 |
<div id = "sidecol"> |
Browse code
Add twitter to contact page.
This will eventually get our twitter account verified!
Nima Fatemi authored on 24/11/2014 23:18:43
• Sebastian Hahn committed on 03/12/2014 03:10:50
Showing 1 changed files
| ... | ... |
@@ -16,6 +16,7 @@ |
| 16 | 16 |
<li><a href="#support">Support</a></li> |
| 17 | 17 |
<li><a href="#email">Email</a></li> |
| 18 | 18 |
<li><a href="#irc">IRC</a></li> |
| 19 |
+ <li><a href="#twitter">Twitter</a></li> |
|
| 19 | 20 |
<li><a href="#phone">Telephone</a></li> |
| 20 | 21 |
<li><a href="#mail">Mailing Address</a></li> |
| 21 | 22 |
</ul> |
| ... | ... |
@@ -83,6 +84,10 @@ |
| 83 | 84 |
stuff that is not related to Tor.</li> |
| 84 | 85 |
</ul> |
| 85 | 86 |
|
| 87 |
+ <a id="twitter"></a> |
|
| 88 |
+ <h3><a class="anchor" href="#twitter">Twitter</a></h3> |
|
| 89 |
+ <p>Follow <a href="https://twitter.com/torproject">@TorProject</a> on Twitter!</p> |
|
| 90 |
+ |
|
| 86 | 91 |
<a id="phone"></a> |
| 87 | 92 |
<h3><a class="anchor" href="#phone">Telephone</a></h3> |
| 88 | 93 |
<p>The Tor office is reachable at +1-781-948-1982. Please be aware that your |
Browse code
remove identica from contact
seems like no one's maintaining that account anymore.
who uses identica anyways! all the cool kids have moved to twitter!
Nima Fatemi authored on 24/11/2014 23:03:36
• Sebastian Hahn committed on 03/12/2014 03:10:27
Showing 1 changed files
| ... | ... |
@@ -15,7 +15,6 @@ |
| 15 | 15 |
<ul> |
| 16 | 16 |
<li><a href="#support">Support</a></li> |
| 17 | 17 |
<li><a href="#email">Email</a></li> |
| 18 |
- <li><a href="#identica">Identi.ca</a></li> |
|
| 19 | 18 |
<li><a href="#irc">IRC</a></li> |
| 20 | 19 |
<li><a href="#phone">Telephone</a></li> |
| 21 | 20 |
<li><a href="#mail">Mailing Address</a></li> |
| ... | ... |
@@ -65,11 +64,6 @@ |
| 65 | 64 |
before posting.</li> |
| 66 | 65 |
</ul> |
| 67 | 66 |
|
| 68 |
- <a id="identica"></a> |
|
| 69 |
- <h3><a class="anchor" href="#identica">Identi.ca</a></h3> |
|
| 70 |
- <p>Contact us via our microblogging Identi.ca account <a |
|
| 71 |
- href="https://identi.ca/torproject">@torproject</a>.</p> |
|
| 72 |
- |
|
| 73 | 67 |
<a id="irc"></a> |
| 74 | 68 |
<h3><a class="anchor" href="#irc">IRC</a></h3> |
| 75 | 69 |
<p>Tor users and developers can also be found in the following channels on <a |
Browse code
Add bad-relays@ to contact page
Matthew Finkel authored on 28/07/2014 05:52:28
Showing 1 changed files
| ... | ... |
@@ -60,6 +60,9 @@ |
| 60 | 60 |
Tor the non-profit corporation: trademark questions, affiliation |
| 61 | 61 |
and coordination, major gifts, contract inquiries, licensing and |
| 62 | 62 |
certification, etc.</li> |
| 63 |
+ <li><i>bad-relays@lists.torproject.org</i> is for reporting exit relays |
|
| 64 |
+ observed to be misconfigured or malicious. You do not need to subscribe |
|
| 65 |
+ before posting.</li> |
|
| 63 | 66 |
</ul> |
| 64 | 67 |
|
| 65 | 68 |
<a id="identica"></a> |
Browse code
Introducing the tor-project IRC channel.
Matt Pagan authored on 23/05/2014 04:23:03
Showing 1 changed files
| ... | ... |
@@ -79,6 +79,9 @@ |
| 79 | 79 |
<li><i>#tor-dev</i> - Channel for people who want to do development. |
| 80 | 80 |
Discussions about Tor-related coding, protocols, and <a href="<page |
| 81 | 81 |
getinvolved/volunteer>">project ideas</a> are all welcome.</li> |
| 82 |
+ <li><i>#tor-project</i> - Organization discussions unrelated to |
|
| 83 |
+ software development. A great place to discuss Tor community events, |
|
| 84 |
+ outreach, translation, or website improvements.</li> |
|
| 82 | 85 |
<li><i>#nottor</i> - This is where Tor people hang out to talk about |
| 83 | 86 |
stuff that is not related to Tor.</li> |
| 84 | 87 |
</ul> |
Browse code
add mailing address.
Andrew Lewman authored on 11/03/2014 20:10:02
Showing 1 changed files
| ... | ... |
@@ -18,6 +18,7 @@ |
| 18 | 18 |
<li><a href="#identica">Identi.ca</a></li> |
| 19 | 19 |
<li><a href="#irc">IRC</a></li> |
| 20 | 20 |
<li><a href="#phone">Telephone</a></li> |
| 21 |
+ <li><a href="#mail">Mailing Address</a></li> |
|
| 21 | 22 |
</ul> |
| 22 | 23 |
|
| 23 | 24 |
<a id="support"></a> |
| ... | ... |
@@ -84,14 +85,21 @@ |
| 84 | 85 |
|
| 85 | 86 |
<a id="phone"></a> |
| 86 | 87 |
<h3><a class="anchor" href="#phone">Telephone</a></h3> |
| 87 |
- <p>If none of the above appeal to you, calling +1-781-948-1982 |
|
| 88 |
- will reach the Tor office. Should there be no answer, please |
|
| 89 |
- leave a message with a way to reach you. Please be aware that your |
|
| 88 |
+ <p>The Tor office is reachable at +1-781-948-1982. Please be aware that your |
|
| 90 | 89 |
phone company and ours (and everyone in between) could listen to |
| 91 | 90 |
the call. Please do not call for technical support, rather email |
| 92 |
- <em>help@rt.torproject.org</em>. Technical support calls are not |
|
| 91 |
+ <em>help@rt.torproject.org</em>. Technical support phone calls are not |
|
| 93 | 92 |
returned.</p> |
| 94 | 93 |
|
| 94 |
+ <a id="mail"></a> |
|
| 95 |
+ <h3><a class="anchor" href="#mail">Mailing Address</a></h3> |
|
| 96 |
+ <p>Should you need to reach us via old reliable mail, our mailing |
|
| 97 |
+ address is: |
|
| 98 |
+ <p>The Tor Project, Inc<br> |
|
| 99 |
+ 7 Temple Street, Suite A<br> |
|
| 100 |
+ Cambridge, MA 02139-2403 USA</p> |
|
| 101 |
+ </p> |
|
| 102 |
+ |
|
| 95 | 103 |
</div> |
| 96 | 104 |
<!-- END MAINCOL --> |
| 97 | 105 |
<div id = "sidecol"> |
Browse code
Dropping references to tor-translation@
Oops, we removed this list but the site still references it. Caught by qbi
on...
https://trac.torproject.org/10718
Damian Johnson authored on 24/01/2014 18:01:47
Showing 1 changed files
| ... | ... |
@@ -50,9 +50,6 @@ |
| 50 | 50 |
development. For both of these <a href="<page |
| 51 | 51 |
docs/documentation>#MailingLists">mailing lists</a>, |
| 52 | 52 |
you must subscribe before you can post.</li> |
| 53 |
- <li><i>tor-translation@lists.torproject.org</i> can put new <a |
|
| 54 |
- href="<page getinvolved/translation>">translations</a> into place, |
|
| 55 |
- and help answer questions about existing and new translations.</li> |
|
| 56 | 53 |
<li><i>donations@torproject.org</i> is for questions and comments about <a |
| 57 | 54 |
href="<page donate/donate>">getting money to the developers</a>. More |
| 58 | 55 |
donations means <a href="<page docs/faq>#Funding">more |
Browse code
change the phone number.
Andrew Lewman authored on 07/11/2013 17:13:47
Showing 1 changed files
| ... | ... |
@@ -17,7 +17,6 @@ |
| 17 | 17 |
<li><a href="#email">Email</a></li> |
| 18 | 18 |
<li><a href="#identica">Identi.ca</a></li> |
| 19 | 19 |
<li><a href="#irc">IRC</a></li> |
| 20 |
- <li><a href="#sms">SMS/Text Messaging</a></li> |
|
| 21 | 20 |
<li><a href="#phone">Telephone</a></li> |
| 22 | 21 |
</ul> |
| 23 | 22 |
|
| ... | ... |
@@ -86,16 +85,9 @@ |
| 86 | 85 |
stuff that is not related to Tor.</li> |
| 87 | 86 |
</ul> |
| 88 | 87 |
|
| 89 |
- <a id="sms"></a> |
|
| 90 |
- <h3><a class="anchor" href="#sms">SMS/Text Messaging</a></h3> |
|
| 91 |
- <p>We've started an experimental SMS/Text Messaging contact |
|
| 92 |
- system. The following number can receive SMS/Text Messages from |
|
| 93 |
- anywhere: +15088010746. Please be aware that your phone company and |
|
| 94 |
- ours (and everyone in between) could see the messages.</p> |
|
| 95 |
- |
|
| 96 | 88 |
<a id="phone"></a> |
| 97 | 89 |
<h3><a class="anchor" href="#phone">Telephone</a></h3> |
| 98 |
- <p>If none of the above appeal to you, calling +1-508-801-0746 |
|
| 90 |
+ <p>If none of the above appeal to you, calling +1-781-948-1982 |
|
| 99 | 91 |
will reach the Tor office. Should there be no answer, please |
| 100 | 92 |
leave a message with a way to reach you. Please be aware that your |
| 101 | 93 |
phone company and ours (and everyone in between) could listen to |
Browse code
update contact info
Andrew Lewman authored on 10/07/2013 21:11:19
Showing 1 changed files
| ... | ... |
@@ -95,11 +95,13 @@ |
| 95 | 95 |
|
| 96 | 96 |
<a id="phone"></a> |
| 97 | 97 |
<h3><a class="anchor" href="#phone">Telephone</a></h3> |
| 98 |
- <p>If none of the above appeal to you, calling +1-781-948-1982 |
|
| 99 |
- will reach the Tor office. Should there be no answer, please leave |
|
| 100 |
- a message with a way to reach you. Please be aware that your phone |
|
| 101 |
- company and ours (and everyone in between) could listen to the |
|
| 102 |
- call. Please email <em>help@rt.torproject.org</em> for support.</p> |
|
| 98 |
+ <p>If none of the above appeal to you, calling +1-508-801-0746 |
|
| 99 |
+ will reach the Tor office. Should there be no answer, please |
|
| 100 |
+ leave a message with a way to reach you. Please be aware that your |
|
| 101 |
+ phone company and ours (and everyone in between) could listen to |
|
| 102 |
+ the call. Please do not call for technical support, rather email |
|
| 103 |
+ <em>help@rt.torproject.org</em>. Technical support calls are not |
|
| 104 |
+ returned.</p> |
|
| 103 | 105 |
|
| 104 | 106 |
</div> |
| 105 | 107 |
<!-- END MAINCOL --> |
Browse code
commit a clarification that's been sitting in my inbox
Roger Dingledine authored on 08/07/2013 02:20:15
Showing 1 changed files
| ... | ... |
@@ -46,9 +46,11 @@ |
| 46 | 46 |
|
| 47 | 47 |
<ul> |
| 48 | 48 |
<li><i>tor-talk@lists.torproject.org</i> is for all discussion |
| 49 |
- about theory, design, development, and use of Onion Routing.</li> |
|
| 50 |
- <li><i>tor-dev@lists.torproject.org</i> is for all discussion |
|
| 51 |
- regarding Tor research and development.</li> |
|
| 49 |
+ about theory, design, development, and use of Onion Routing. |
|
| 50 |
+ <i>tor-dev@lists.torproject.org</i> is for Tor research and |
|
| 51 |
+ development. For both of these <a href="<page |
|
| 52 |
+ docs/documentation>#MailingLists">mailing lists</a>, |
|
| 53 |
+ you must subscribe before you can post.</li> |
|
| 52 | 54 |
<li><i>tor-translation@lists.torproject.org</i> can put new <a |
| 53 | 55 |
href="<page getinvolved/translation>">translations</a> into place, |
| 54 | 56 |
and help answer questions about existing and new translations.</li> |
Browse code
add non-english support addresses
Runa A. Sandvik authored on 28/03/2013 17:27:09
Showing 1 changed files