I was initially quite pessimistic when I realised this issue existed:
https://git.eff.org/?p=sovereign-keys.git;a=blob;f=issues/bridge-exposure.txt;h=f5a259056f59d23487cdd008cef5a1fa8a937c4d;hb=HEAD
In a sense, it undercuts one of the main design objectives of SKs ("fall back
to censorship-resistant secure routing, but only when required"). The fall
back to secure routing part is still ok, but it turns out that it's hard to
only be censorship resitant when you're actually being censored.
--
Peter Eckersley [email protected]
Technology Projects Director Tel +1 415 436 9333 x131
Electronic Frontier Foundation Fax +1 415 436 9993
