[tor-bugs] #31378 [Core Tor/Tor]: Run in ram mode

[Tor Bug Tracker & Wiki]

#31378: Run in ram mode
--+--
 Reporter:  daealc|  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Component:  Core Tor/Tor
  Version:|   Severity:  Normal
 Keywords:  readonly ram  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
 allow --ram-only or --ro-filesystem which disable writing to disk, instead
 keeping all information in ram

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #31378 [Core Tor/Tor]: Run in ram mode

[Tor Bug Tracker & Wiki]

#31378: Run in ram mode
--+
 Reporter:  daealc|  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  readonly ram  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by arma):

 This seems like a risky idea. For clients, discarding your entry guards is
 potentially very hazardous. For relays, ...actually ok for relays it might
 not be crazy.

 The current answer is to either make a ramdisk and put your datadirectory
 there, or for more normal users, to use Tails.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #31378 [Core Tor/Tor]: Run in ram mode

[Tor Bug Tracker & Wiki]

#31378: Run in ram mode
--+
 Reporter:  daealc|  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  readonly ram  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+

Comment (by daealc):

 It seems at least to me that for a piece of software that is primarily
 aimed at people who may be in a 'tight spot' it would be far more sane to
 allow the tor daemon to run anywhere, if information is written to a
 permanent location it can be a sign of tor running.

 However ... if it was to run purely in ram especially the chances of
 discovering evidence of tor usage is minimized, on top of that it would
 also allow for operators who wish to contribute to the network to simply
 'run tor with x settings' and not have to worry about where its writing
 to.

 There really is very little that is bad about adding this option, as for
 entry points if you say tails/memory disks are the answer to my
 enhancement, surely remembering the fingerprint of a trusted entry-point
 is easier. Bearing in mind tails requires rebooting into it and facing
 potential hardware difficulties and using memory disks requires root
 access. Either of which may not be availible.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #31378 [Core Tor/Tor]: Run in ram mode

[Tor Bug Tracker & Wiki]

#31378: Run in ram mode
--+--
 Reporter:  daealc|  Owner:  (none)
 Type:  enhancement   | Status:  new
 Priority:  Medium|  Milestone:  Tor: unspecified
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  readonly ram  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--
Changes (by dgoulet):

 * milestone:   => Tor: unspecified


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs