Tor and Wikipedia Roger Dingledine The Free Haven Project 1 - - PowerPoint PPT Presentation

tor and wikipedia
SMART_READER_LITE
LIVE PREVIEW

Tor and Wikipedia Roger Dingledine The Free Haven Project 1 - - PowerPoint PPT Presentation

Tor and Wikipedia Roger Dingledine The Free Haven Project 1 Motivation China blocks Wikipedia; Wikipedia blocks Tor edits. Thousands(?) of Tor users would like to edit Wikipedia but can't. (I'm not saying you must allow Tor edits


slide-1
SLIDE 1

1

Tor and Wikipedia

Roger Dingledine The Free Haven Project

slide-2
SLIDE 2

2

Motivation

  • China blocks Wikipedia; Wikipedia

blocks Tor edits.

  • Thousands(?) of Tor users would like

to edit Wikipedia but can't.

  • (I'm not saying you must allow Tor

edits – I just want to explain some technical possibilities.)

slide-3
SLIDE 3

3

We have to make some assumptions about what the attacker can do.

Alice Anonymity network Bob watch (or be!) Bob! watch Alice! Control part of the network! Etc, etc.

slide-4
SLIDE 4

4

Anonymity serves different interests for different user groups.

Anonymity Private citizens Governments Businesses “It's privacy!”

slide-5
SLIDE 5

5

Anonymity serves different interests for different user groups.

Anonymity Private citizens Governments Businesses “It's network security!” “It's privacy!”

slide-6
SLIDE 6

6

Anonymity serves different interests for different user groups.

Anonymity Private citizens Governments Businesses “It's traffic-analysis resistance!” “It's network security!” “It's privacy!”

slide-7
SLIDE 7

7

The simplest designs use a single relay to hide connections.

Bob2 Bob1 Bob3 Alice2 Alice1 Alice3 Relay Bob3,“X” Bob1, “Y” B

  • b

2 , “ Z ” “Y” “Z” “X” (ex: some commercial proxy providers)

slide-8
SLIDE 8

8

So, add multiple relays so that no single one can betray Alice.

Bob Alice R1 R2 R3 R4 R5

slide-9
SLIDE 9

9

Alice makes a session key with R1

Bob Alice R1 R2 R3 R4 R5

slide-10
SLIDE 10

10

Alice makes a session key with R1 ...And then tunnels to R2

Bob Alice R1 R2 R3 R4 R5

slide-11
SLIDE 11

11

Alice makes a session key with R1 ...And then tunnels to R2...and to R3

Bob Alice R1 R2 R3 R4 R5

slide-12
SLIDE 12

12

Can multiplex many connections through the encrypted circuit

Bob Alice R1 R2 R3 R4 R5 Bob2

slide-13
SLIDE 13

13

Some problems with IP addresses as authenticators

  • AOL has a dozen IP addresses.
  • Open proxies, misconfigured computers,

botnets, ...

  • Dynamic IPs
  • Universities (and countries!) with only a few IP

addresses

  • Tor
slide-14
SLIDE 14

14

slide-15
SLIDE 15

15

Tor and Abuse

  • Tor has hundreds of thousands of active users

these days, and pushes >600Mbps of traffic, mostly web browsing.

  • We have our share of jerks, just like the Internet

in general.

  • If an anonymity system works well, nobody hears

about it. So “hearsay” is not on our side.

slide-16
SLIDE 16

16

Bug 550 and its solution (Thanks Tim!)

  • Two new config options:

For some IP addresses,

–Let people edit, but only if they're

logged in.

–Don't let people create new accounts.

slide-17
SLIDE 17

17

Still some problems

  • People can create accounts

elsewhere and “spend” them at

  • nce.
  • People who don't have unblocked

IPs still lose.

slide-18
SLIDE 18

18

Key concept

  • Add speedbumps only for blocked IPs.

Yes, IP addresses can give you a hint, but they're not authenticators.

  • 1) edits need to prove that they're

worthwhile; or better,

  • 2) accounts need to prove that they're

worthwhile.

slide-19
SLIDE 19

19

But slowing down users is bad!

  • AKA: “it's hard to do CAPTCHAs

that work for blind people”

  • You're blocking them completely

right now. At least this way, we let some of them edit.

slide-20
SLIDE 20

20

How much abuse then?

  • “But there will be so much abuse to wade

through, this can't possibly work.”

  • If the abuse doesn't go directly to the

website, the jerks will go to a new avenue – so the number of edits/accounts we need to approve will be pretty much the actual number.