[tor-relays] issues with a fresh new tor server

Toralf Förster toralf.foerster at gmx.de
Sun Aug 21 16:51:44 UTC 2016


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 08/21/2016 06:35 PM, Tom van der Woerdt wrote:
> Side-note wrt your setup :
> 
> You're storing the keys on the disk, and while they're removed
> immediately after, that potentially leaves them on the physical storage.
> Since you're already passing them through ssh, consider just having ssh
> do the stdin bit :
> 
> cat ~/.cryptoPass | ssh user at host "sudo -u tor e4crypt add_key -S $(cat
> ~/.cryptoSalt) /var/lib/tor"
> 
> The salt will end up in the sudo log (/var/log/secure, usually) but the
> password will never hit the disk. No scp needed, and no files to rm
> afterwards.
> 
> Tom

Thx for your hints - I'll test your advice soon.

FWIW I do have 
	Defaults !syslog,!pam_session
in /etc/sudoers, therefore sudo commands shouldn't be logged I hope. And I do have /tmp as a tmpfs. And finally "tor" is just a technical user w/o login or so.


- -- 
Toralf
PGP: C4EACDDE 0076E94E, OTR: 420E74C8 30246EE7
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iF4EAREIAAYFAle53CAACgkQxOrN3gB26U7zXQD9HXerMKNjq3o8z7ByeS2yaI3s
1mbru/OrXLBEoKycwZwA/1AwQR+zEguL05d76hBAMN0ejfeFNl6VTbC2hpAuDn8M
=kBrc
-----END PGP SIGNATURE-----


More information about the tor-relays mailing list