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 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.
Each year, they should look at the number of accidents. If you had none, you don't pay _any_ insurance. If you had one, you pay a one time fee as high as the damage you caused.
Yeah, because what we need the most - besides people who do everything to save a penny - is said people to think about their money first when they encounter a dangerous situation where they _have_ to brake hard. Driving like a turtle on Valium doesn't eliminate other stupid drivers.
I, too, have transcended the need to see a motor and gear operating. However, I'm required to keep my car fit for public traffic. If it's broken and I can't fix it myself, I don't come up with an armchair diagnosis and then run off to the first forum I find on the Internet in a crappy attempt to handle the situation myself.
I go to a fucking repair shop.
But nooo, criminally negligent operation of an Internet connection is perfectly OK and don't you dare to attack the ignorant unique snowflake. Also, fuck the local PC industry, Mr. unique snowflake can perfectly handle this. With MAC addresses on the Internet and all that.
The next time you have to delete another spam mail, thank the OP.
For the record: logs from a consumer router imitation mean jack shit.
They stuff all these sophisticated "attack detections" into these crappy devices that constantly bark at pure background noise so the customer feels he bought a good product because it's "constantly fending off the bad guys".
It's all fucking bullshit. You can't defend from a DoS at the edge device that's being hit because the packets already saturated your line when they hit it and there's nothing you can do about it.
My guess about the "article": Clueless armchair admin sees his suckass router barking at him and is making up some elaborate attack scenario because he knows shit.
Because that's the current generation of armchair admins for you. Either that, or his "live production system" is really just his basement porn server.
Liberties going down the drain, secret laws, secret courts, secret prisons, killing people without any trial, but at least we still have stupid nerd jokes in the form of funny HTTP headers.
Private keys are not sent anywhere, ever. If someone is generating your private key for you, in a browser nonetheless, you are doing PKI wrong. Period.
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.
So far, all I've gathered from his disclosures are gross violations of rights. What did he disclose that is not that?
Snowden did nothing wrong. He broke a wrong law. That's not wrong.
How about only hashing files with identical file sizes?
Sounds awesome - and you're not even running any applications yet. Some people just don't have that amount of time to piss away, though.
So you say being a disgustingly fat pig is genetics' fault?
Newsflash Sherlock: You're fat if your energy intake is greater than your energy spending. The End.
I have an idea!
Each year, they should look at the number of accidents. If you had none, you don't pay _any_ insurance. If you had one, you pay a one time fee as high as the damage you caused.
Maximum optimisation insurance!
Yeah, because what we need the most - besides people who do everything to save a penny - is said people to think about their money first when they encounter a dangerous situation where they _have_ to brake hard. Driving like a turtle on Valium doesn't eliminate other stupid drivers.
I, too, have transcended the need to see a motor and gear operating. However, I'm required to keep my car fit for public traffic. If it's broken and I can't fix it myself, I don't come up with an armchair diagnosis and then run off to the first forum I find on the Internet in a crappy attempt to handle the situation myself.
I go to a fucking repair shop.
But nooo, criminally negligent operation of an Internet connection is perfectly OK and don't you dare to attack the ignorant unique snowflake. Also, fuck the local PC industry, Mr. unique snowflake can perfectly handle this. With MAC addresses on the Internet and all that.
The next time you have to delete another spam mail, thank the OP.
For the record: logs from a consumer router imitation mean jack shit.
They stuff all these sophisticated "attack detections" into these crappy devices that constantly bark at pure background noise so the customer feels he bought a good product because it's "constantly fending off the bad guys".
It's all fucking bullshit. You can't defend from a DoS at the edge device that's being hit because the packets already saturated your line when they hit it and there's nothing you can do about it.
My guess about the "article": Clueless armchair admin sees his suckass router barking at him and is making up some elaborate attack scenario because he knows shit.
The worst religious country - whose religion preaches love thy neighbor - actually has the worst social care? Color me surprised. Or maybe not.
Because that's the current generation of armchair admins for you. Either that, or his "live production system" is really just his basement porn server.
You'd be surprised how many people do backups but never test restore.
In the name of all Germans I want to apologize for this. It was a huge mistake...
Sorry.
Liberties going down the drain, secret laws, secret courts, secret prisons, killing people without any trial, but at least we still have stupid nerd jokes in the form of funny HTTP headers.
Haha, I'm so not laughing.
Stop writing. Just stop.
Private keys are not sent anywhere, ever. If someone is generating your private key for you, in a browser nonetheless, you are doing PKI wrong. Period.