··· welcome, welcome to cryptostorm's member forums [you don't have to be a cryptostorm member to post here] Ξ if you'd prefer a break from detail-heavy tech, our cryptohaven.net blog & @cryptohaven twitter feed take a broader view of network security & what it all means Ξ ∞ or if you can't get enough deep-dive details our crypto.cricket fills that need, whilst seekers of bleeding-edge netsec insight will heart our legendary @cryptostorm_is feed ∞
DeepDNS.dk & leakblock.org - cryptostorm's anti-leak technologies A core mission of cryptostorm is ensuring consistent, reliable network security with minimal fuss & drama. From DNS-based services like our DeepDNS in-browser native .onion/.i2p site access, through grounbreaking research on IP6 leakblocking, & to firewall-based structures to enable "fail-closed" security, this is where we discuss & develop cryptostorm-style leakblock tech.
privacy seppuku: data, tasks, brainstorming "Privacy seppuku" is the decision by privacy-oriented projects to voluntarily shut down, rather than be coerced into collaboration with the surveillance regime and concomitant betrayal of customer trust. The 'seppuku pledge' is a public pre-commitment to the principles of privacy seppuku, This is a place to review & discuss...
undervulns: hypervisor vulns, BIOS hacks, & hardware holes [cryptostorm.org/undervulns] Nowadays, most server (and many desktop) resources run in virtualized architectures - hypervisors supporting VMs, decoupled from the metal. This ends up having enormous security implications, which are only slowly being identified & studied. This subforum is a central location for gathering such research data, discussing it, and enabling a new cateogry of security wisdom.