tor-webwml.git

1) ## translation metadata

2) # Revision: $Revision$

3) # Translation-Priority: 3-low
4) 
5) #include "head.wmi" TITLE="Tor Project: Contact" CHARSET="UTF-8"
6) 
7) <div id="content" class="clearfix">
8) 	<div id="breadcrumbs">

9)     <a href="<page index>">Home &raquo; </a>

10)     <a href="<page about/overview>">About &raquo; </a>

11)     <a href="<page about/contact>">Contact</a>
12)   </div>
13)   <div id="maincol">
14)     <h2>Tor: Contact</h2>

15)     <ul>

16)     <li><a href="#support">Support</a></li>

17)     <li><a href="#irc">IRC</a></li>

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>

22)     <li><a href="#email">Email</a></li>

23)     <li><a href="#mail">Mailing Address</a></li>

24)     </ul>

25) 

26)     <a id="support"></a>

27)     <h3><a class="anchor" href="#support">Support</a></h3>

28) 

29)     <!--

30)     <p><i>help@rt.torproject.org</i> is the address to use for

31)     questions about all things Tor, volunteering, and offering
32)     resources. This is best effort service with no guarantees. We

33)     generally respond within 48 hours. For support in other languages,
34)     try:</p>
35) 
36)     <ul>
37)       <li><i>help-ar@rt.torproject.org</i> for Arabic</li>
38)       <li><i>help-es@rt.torproject.org</i> for Spanish</li>
39)       <li><i>help-fa@rt.torproject.org</i> for Farsi</li>
40)       <li><i>help-fr@rt.torproject.org</i> for French</li>
41)       <li><i>help-zh@rt.torproject.org</i> for Mandarin</li>
42)     </ul>

43)     -->

44) 

45)     <p>If you have questions about using Tor:</p>
46)     <ol>

47)     <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>

48)     <li>See if your question is asked or answered on our

49)     <a href="https://tor.stackexchange.com/">StackExchange page</a>. If
50)     it isn't, please consider asking it there! Then everybody else can
51)     benefit from your question and the answer to it.</li>

52)     <li>Join the <a href="#irc">#tor irc channel</a>, state the issue,
53)     and wait patiently for help.</li>
54)     <li>Read through the archives of the
55)     <a href="<page docs/documentation>#MailingLists">mailing lists</a>
56)     to see if anybody else has raised your issue recently. Note that
57)     you need to subscribe to the mailing lists before you can post.</li>
58)     </ol>
59) 
60)     <p>If you find your answer, please stick around to contribute back
61)     and help others who were once in your position.</p>
62) 

63)     <a id="irc"></a>

64)     <h3><a class="anchor" href="#irc">IRC</a></h3>

65)     <p>Tor users and developers can also be found in the following channels on <a

66)     href="https://www.oftc.net/">OFTC</a>:</p>

67) 

68)     <ul>

69)       <li><i>#tor</i> - For questions about using Tor (as a client, as
70)       a relay, as an onion service). Having trouble running Tor or have
71)       a question for other Tor users? Then this is the spot for you.</li>

72)       <li><i>#tor-dev</i> - Channel for people who want to do development.

73)       Discussions about Tor-related coding, protocols, and <a href="<page

74)       getinvolved/volunteer>">project ideas</a> are all welcome.</li>

75)       <li><i>#tor-project</i> - Organization discussions unrelated to
76)       software development. A great place to discuss Tor community events,

77)       outreach, translation, or website improvements.</li>

78)       <li><i>#tor-meeting</i> - The various Tor teams, like the network
79)       team, the browser team, the UX team, and the metrics team, hold
80)       periodic <a href="http://meetbot.debian.net/tor-meeting/">publicly
81)       logged</a> meetings in this channel.</li>

82)     </ul>

83) 

84)     <a id="twitter"></a>
85)     <h3><a class="anchor" href="#twitter">Twitter</a></h3>

86)     <p>Follow us on Twitter:</p>

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) 

92)     <a id="bugs"></a>
93)     <h3><a class="anchor" href="#bugs">Bug Tracker</a></h3>
94)     <p>You can report bugs other than <a href="#security">security
95)     issues</a> using our <a href="https://trac.torproject.org/projects/tor"
96)     >bug tracker</a>. Our
97)     <a href="<page getinvolved/volunteer>">volunteer page</a> has
98)     convenient links to <a href="<page getinvolved/volunteer>#Projects">
99)     project-related queries</a>.</p>
100) 
101)     <a id="security"></a>
102)     <h3><a class="anchor" href="#security">Security Issues</a></h3>
103)     <p>If you've found a security issue in one of our projects or in our
104)     infrastructure, please email tor-security@lists.torproject.org.
105)     You can get the GPG public key for the list by contacting
106)     tor-security-sendkey@lists.torproject.org or from
107)     pool.sks-keyservers.net. Here is the fingerprint:
108) <blockquote><pre>
109) gpg --fingerprint tor-security@lists.torproject.org
110) pub   4096R/1A7BF184 2017-03-13
111)       Key fingerprint = 8B90 4624 C5A2 8654 E453  9BC2 E135 A8B4 1A7B F184
112) uid                  tor-security@lists.torproject.org <tor-security@lists.torproject.org>
113) uid                  tor-security@lists.torproject.org <tor-security-owner@lists.torproject.org>
114) uid                  tor-security@lists.torproject.org <tor-security-request@lists.torproject.org>
115) sub   4096R/C00942E4 2017-03-13
116) </pre></blockquote>
117)     </p>

118) 

119)     <a id="badrelays"></a>
120)     <h3><a class="anchor" href="#badrelays">Report Bad Relays</a></h3>
121)     <p>If you find a relay that you think is malicious, misconfigured,
122)     or otherwise broken, please check out our
123)     <a href="https://trac.torproject.org/projects/tor/wiki/doc/ReportingBadRelays">
124)     wiki page</a> and <a href="https://blog.torproject.org/how-report-bad-relays"
125)     >blog post</a> on how to report it.</p>

126) 
127) 

128)     <a id="email"></a>

129)     <h3><a class="anchor" href="#email">Email</a></h3>
130)     <p>If you have Tor questions, please try to help yourself via the

131)     above support venues. Please don't use this contact address

132)     for helpdesk or user requests — we all get too much mail and
133)     we won't be able to help you there.</p>
134) 
135)     <ul>

136)       <li><i>frontdesk@rt.torproject.org</i> is for questions and
137)       comments about Tor the non-profit organization: funding and
138)       donations, trademark questions,
139)       affiliation and coordination, major gifts, contract inquiries, etc.
140)       Please note that email is not a great approach for safe
141)       communication, so if you need privacy consider reaching us some
142)       other way. Also note that the frontdesk is currently handled by
143)       volunteers, so please be patient.
144)       </li>

145)     </ul>
146) 

147)     <a id="mail"></a>
148)     <h3><a class="anchor" href="#mail">Mailing Address</a></h3>

149)     <p>Should you need to reach us via old-fashioned mail, our mailing
150)     address is:</p>
151) <address>The Tor Project<br>
152) 217 1st Ave South #4903<br>

153) Seattle, WA 98194 USA<br><br>

154) </address>

155) 

156)   </div>
157)   <!-- END MAINCOL -->
158)   <div id = "sidecol">
159) #include "side.wmi"
160) #include "info.wmi"
161)   </div>
162)   <!-- END SIDECOL -->
163) </div>
164) <!-- END CONTENT -->