[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-talk] TBB: Rixstep 30MB "steaming faeces"
A separate thread to pull in mentions from other tor subthreads.
Rixstep seems to be making the point to remember watch your
code and execution, not only during normal times, but during intense
times when you're more easily distracted from malfeasance slipping in.
Other than that, and it not really being links to more general developments
and directions in overall tor news for interested parties, balance,
journalism, transparency, discussion, or whatever,
Rixstep does seem better thought of and handled as a bug report.
So determine...
1) Is anything sensitive [1] being written to disk, perhaps in the
sqlite files that Rixstep listed, or remaining in slack space?
2) Is evidence of simple usage being written to disk, or remaining
in slack space?
If either of those bother you, fix it.
Or work around it with another layer like disk crypto.
Source of the subject thread references, with list of files...
http://rixstep.com/2/2/20160817,00.shtml
http://rixstep.com/2/2/20160717,00.shtml
[1] History, cookies, auth, meta, data...
--
tor-talk mailing list - tor-talk@xxxxxxxxxxxxxxxxxxxx
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk