Analyze "vpwns" FOCI12 paper
We should analyze https://www.usenix.org/conference/foci12/vpwns-virtual-pwned-networks and decide what we should do.
Being discussed on tails-dev, starting with https://mailman.boum.org/pipermail/tails-dev/2012-August/001487.html
#1 Updated by BitingBird over 5 years ago
- Description updated (diff)
- Target version set to Hole in the Roof
- Starter set to No
Setting priority according to https://mailman.boum.org/pipermail/tails-dev/2014-March/005265.html
#7 Updated by ioerror about 5 years ago
I realized that while the firewall rules must be updated, the browser also needs an update - I had forgotten that the LAN Foxyproxy rule was in place by default. I've added a second patch - please merge both of these patches to fix the leaks in the browser and the firewall.
#10 Updated by intrigeri almost 5 years ago
- QA Check deleted (
Ready for QA)
(Removing "Ready for QA", as this ticket is about researching how much of the problem applies to Tails, before we can discuss what we want to do, and then we'll have another ticket about implementing the chosen solution, which may be Jake's proposed one, or something else.)
#21 Updated by intrigeri over 4 years ago
- Target version changed from Tails_1.4 to Hole in the Roof
We've been postponing this analysis for way too long. We decided it was a Hole in the Roof a year ago, then someone committed to work on it and 10 months later we're basically at the same point, as far as I can see => setting back to Hole in the Roof (and will ask someone to unassign it, since I don't manage to do it via Redmine email interface).