As long as this matter is in its current state, I wouldn't even bother thinking about the minute details of the "suggestions" on the page.

This whole thing is just absurdly smelling like Lavabit.

They're not only not convenient, they're also not secure in the sense that in order to work with your data, you have to decrypt it _somewhere_. Unless you secure erase your free drive space after zipping your files back up and deleting the unencrypted copies, I wouldn't consider that data to be secure anymore, at all.

It's not as if 7.1a is suddenly unexecutable...

There is no job you can do if the other party is not trustworthy - other than limiting your communication. All this convoluted header bullshit is useless.

Stop crying for a legal solution when there's a perfect technical one: STOP TALKING TO TRACKING SERVERS! Advertisers had their chance. They failed it. So ignore them and let them sulk in their own bullshit.

You base the choice about which router and firmware to run on a measly side-feature, that also locks you into the router vendor? What. The. Fuck.

My bad. Somehow I was assuming the server is in your home LAN.

It's a common notation among official OpenBSD developers to refer to individuals by their mail user name - without the openbsd.org domain. You see it in almost every commit and in mails when the person's role as an official developer is emphasized.

OpenVPN with --tls-auth protecting the TLS layer. That protection made OpenVPN safe against Heartbleed. Doesn't work if you have untrusted users, obviously.

Don't VPN directly into your LAN. Use a hardened node in a heavily firewalled DMZ and use SSH from there.

OpenVPN and OpenSSH simultaneously having a vulnerability is pretty unlikely.

If you've never heard of him, you're not part of any important "tech community". Period.

The whole design of including a variable-sized payload into a heartbeat is completely retarded.

This was either deliberate or Seggelmann is the dumbest fuck on earth.

Wait, you assume it was a mistake?

I've read an assessment that says if you wanted to plant a perfect backdoor, it would look exactly like this.

Wrong, in 1.0.1.

An inherent property of security theater is that both success and failure lead to increased funding.

"It worked!" "Great, but we need to prepare for future's technology. Let's expand the system."

"It didn't work!" "We need to expand the system."

This madness needs to be stopped.

Genius!

Just use a current search engine but with a future database and actch all terrorists! Why didn't anyone think of that?!

If you don't increase your mining more and more, others will do it and your global share of future Bitcoins shrinks and shrinks, since more and more mining power means less and less Bitcoins per GH/s due to difficulty adjustment.