Open GoogleCodeExporter opened 9 years ago
Original comment by prof7...@gmail.com
on 13 Jan 2011 at 1:18
Original comment by prof7...@gmail.com
on 13 Jan 2011 at 1:19
The way it is now though, when closing a conversation window causes an instant
amnesia (providing neither side logs the conversation and there are no delayed
messages) is more 'humanly' secure, I think. It is also mentally easier to
understand and consistent with the paradigm of 'chatting on tor' (i.e. what I
don't see, doesn't exist any longer...).
I was actually already concerned by the _offline.txt files that can be
inadvertently recorded and then silently left behind after TorChat quits,
unless overwritten/deleted by hand.
Original comment by ojtam...@gmail.com
on 22 Nov 2011 at 7:37
A related issue/question: I take it that the content of a conversation(s) is
held in RAM? Is is explicitly wiped from memory when TorChat exits (or the
conversation window is closed)?
There was a question previously on preventing TorChat from writing to the swap
file - wouldn't the above take care of that (or at least part of it) as well?
Cheers!
Original comment by ojtam...@gmail.com
on 22 Nov 2011 at 10:20
And the last (somewhat related) question: the queued/delayed messages are
random-bit? overwritten before being deleted? - does that apply to *both*
manual 'Clear' as well as automatic delete when they are sent?
Original comment by ojtam...@gmail.com
on 22 Nov 2011 at 11:00
every file that is deleted will be overwritten before it is unlinked. (file
transfer temporary files, log files, offline messages, everything)
I don't have a solution for the RAM and the swap file yet.
Original comment by prof7...@gmail.com
on 23 Nov 2011 at 10:40
Original issue reported on code.google.com by
bobby.qu...@gmail.com
on 13 Jan 2011 at 4:41