Ξ welcome to cryptostorm's member forums ~ you don't have to be a cryptostorm member to post here Ξ
∞ take a peek at our legendary cryptostorm_is twitter feed if you're into that kind of thing ∞
Ξ we're rolling out voodoo network security across cryptostorm - big things happening, indeed! Ξ
Ξ any OpenVPN configs found on the forum are likely outdated. For the latest, visit GitHub Ξ
To stay ahead of new and evolving threats, cryptostorm has always looked out past standard network security tools. Here, we discuss and fine-tune our work in bringing newly-created capabilities and newly-discovered knowledge to bear as we keep cryptostorm in the forefront of tomorrow's network security landscape.
I noticed I can access .onion sites directly without any additional suffixes in the url "i.e. torstorm"
It is widely recommended against any "TOR OVER TOR" configuration as the behaviour is described as unpredictable and its implications unknown.
Given this, how would a user of this VPN service who wants to avoid "putting all eggs in one basket" by using the VPNs built in onion routing service and instead run TBB over a crypto-VPN connect [i.e. prevent TOR fingerprints in ISP logs] but avoid the risk associated with any double TOR configs?
- Site Admin
- Posts: 994
- Joined: Wed Feb 05, 2014 3:47 am
If you're talking about accessing .onion sites in a TBB-over-CS scenario, TBB will connect to guard entry nodes which are entirely separate from the client-mode Tor node running on a given CS exit node. The routing onto the .onion network will be totally different.
Last bumped by Anonymous on Thu Apr 07, 2016 6:38 am.
Return to “cryptostorm reborn: voodoo networking, stormtokens, PostVPN exotic netsecurity”
Who is online
Users browsing this forum: No registered users and 3 guests