Custom Query (15 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (11 - 15 of 15)

1 2 3
Ticket Summary Owner
#10080 Publicize Tor Stack Exchange lunar
Description

https://tor.stackexchange.com/ now supports https.

And while it started to get a good collection of users and questions and answers, weasel informs me that it is starving now.

We should either choose to abandon it, or make it much easier to find for our users.

Assuming we choose the latter, here are some things to do:

A) Link from the "getting up to speed" list on the documentation page. Done.

B) Link from the front page of the website.

C) Link from the top / side of the blog.

D) Get all the support people to use the answers on stack exchange, and if they don't like the answers, fix them.

D2) Make the RT auto-respond mail tell people about stack exchange.

E) Put a prominent bookmark for it into TBB.

F) What else?

#9835 Backup Stack Exchange Tor site lunar
Description

It looks like we are going live with the Tor Stack Exchange Q&A site. There is going to be a lot of valuable thoughts in there, and it is probably a good idea to have our own backups in case Stack Exchange falls, fails or bails on the Tor project.

It should probably be done using a query run regularly against http://data.stackexchange.com/ or maybe using the data dumps http://www.clearbits.net/creators/146-stack-exchange-data-dump

#8518 Document the new support workflow phoul
Description

The support workflow is changing, the team is growing, I should document it.

#5553 prevent protocol leaks; Tor client connection API or protocol review howto phoul
Description

I am unhappy with the current Torify instructions.

The big bittorrent leak may happen to any application, which has not been explicitly designed for Tor or reviewed by someone. That's why safe use of Tor is at the moment somewhat limited to the few applications designed over Tor (Tor Browser) or reviewed for use over Tor.

Two ideas will follow how to solve this problem. One or another may work as solution. Feel free to propose other/better/easier/faster solutions.

Proposal 1: Write a howto, how to review an application and protocol for leak free use over Tor. "The protocol/application has to be reviewed." - That is much to vague, even for the application's developer.

For example, would the xchat developers answer "xchat over Tor: do not use dcc/ctcp... it leaks your IP/timezone..."?

What we easily could do for many applications, would be asking the application's developers. But even them could be confused by the question. The paper should define, what a protocol leak is, how to look out for them, how to prevent them.

This would hopefully enable the application developers to answer to the question regarding the protocol leak status. And if they don't want to review their own application, third party contributors could review the protocol.

Proposal 2: Provide an alternate interface for applications. An alternative to socks. Either an API or libery for developers. i2p does also provide one and loads of applications are build on top of i2p. Why there are not so many applications designed for Tor? Because there is neither an API nor an libery.

#4509 Write blog posts on strategies to avoid risk and protect online identity karen
Description

The status report actually says periodic white papers, but I figured that a few blog posts would be just as good. We could point to the bypassing censorship manual, the anonymous blogging guide etc.

The Sponsor E page had the following listed under Internet censorship awareness. I'm sure we can include it here somehow:

Guidance on ‘how best to address censorship’ manual:

  • How to interpret the source data collected and reported?
  • How do users use this data to change their actions?
1 2 3
Note: See TracQuery for help on using queries.