3 ms·
Hm, the problem with this kind of tools is that if you're not willing to read the documentation to get a good understanding of what you're doing, you might end
by atmosx 10y ago
Hm, the problem with this kind of tools is that if you're not willing to read the documentation to get a good understanding of what you're doing, you might end up thinking you're secure instead of being secure which is the worst case scenario.
- infogulch 10y agoIs there a way to configure the tool to not be secure? Why is the secure configuration not the default? Can a secure default be easier to set up?
- ryukafalz 10y agoBecause normally, the context here is that you're trying to set up an existing internet service over the Tor network. Your web server, for example, typically doesn't know anything about Tor, and will happily serve up pages to normal internet users unless you configure it not to. Services designed for Tor don't have this issue and can be secure by default. Ricochet[1], for example, advertises itself as a hidden service automatically and doesn't communicate outside the Tor network. 1: https://ricochet.im/ https://ricochet.im/
- lazaroclapp 10y agoSure, but you could always have something like a script that takes a Vagrant VM or a docker container and turns it into a hidden service on Tor. The script would take care of making sure the only access to the VM is through Tor and that the VM learns nothing (under normal operations, I am not even thinking about patching side-channel attacks and escalation-to-host attacks here) about the host's identity or location. I am thinking something like: vagrant up --provider=tor my-service Where my-service is any Vagrant node (a config file for setting up a generic VM with whatever software / conf you specify) and the vagrant command outputs the Tor hidden service address in the last line, after loading the VM locally on top of VirtualBox or similar.