--- On Mon, 12/11/12, and...@torproject.is <and...@torproject.is> wrote:
>The first question
> you asked is: "Does TBB write user content to disk?" The
> answer
> to the first question is no, it uses ram cache only.

And so most people would think does setting disk cache to 0 on bog standard 
Firefox, but it still leaves content identifying flash cookies on the HD. So 
"no" is a strange confusing answer imo. I take it that swap qualifies as the 
OS's fault ..seems like dealing with pedantic legal technicalities when it's 
obvious what a laymenis trying to ask! 




> I suppose a third question you imply is "what does tails
> write
> to disk?" 

I've no idea why you thought that!


> And now you blur TBB with Tails, they
> are two separate entities. 

Again, i'm pretty sure there's is no confusion between the two here. I'm 
assuming Tails has it's entire gubbins in RAM; that's the whole point of it. 
But it does include Tor/Vidalia but older versions of them. I was imagining ( 
it's probably nonsense) that Tails could act as some type of VM (to insure no 
traces of anything end up on disk), whilst a separate installation of TBB say 
on a USB could run inside it like the other apps, and it take care of anonymity 
online instead of the older Tor that comes with it. Probably rubbish, but it 
seems Tails and TBB have different specialised strengths at the moment.

The question of swap files and hibernation raised by someone else is pretty 
fundamental. It's pointless and misleading just talking pedantically about disk 
cache as it doesn't matter to the user exactly what blows the gaff.

As far as I can tell: if you want to keep the computer clean, then use Tails. 
If you want to be anonymous, best bet is latest TBB. If you want both...then 
who knows ...

Some of you guys need a bit more understanding for us noobs who don't know what 
we're talking about.



_______________________________________________
tor-talk mailing list
tor-talk@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

Reply via email to