Forgot your password?

Comment: Re:Whatever you may think ... (Score 1) 445

by idontgno (#46728181) Attached to: Heartbleed Coder: Bug In OpenSSL Was an Honest Mistake

The WTF part of this (the kind that lives on) is that the RFC, which he co-authored, has this strong and specific warning:

If the payload_length of a received HeartbeatMessage is too large, the received HeartbeatMessage MUST be discarded silently.

He knew about the risk. He documented the risk. But come coding time, he forgot the risk.

Ya gotta feel for that. How many times have I gotten up bleeding and dazed and said to myself "I knew that was a bad idea."

Comment: Re:Not malicious but not honest? (Score 1) 445

by idontgno (#46728125) Attached to: Heartbleed Coder: Bug In OpenSSL Was an Honest Mistake

The bug itself had to do with allowing a mismatch between the amount of data sent and the amount retransmitted in what's essentially an echo command that TLS implements. A hardened malloc() would make it impossible to exploit that, but OpenSSL would still have a bug even with one, just one that couldn't (probably, maybe, perhaps) be used to get confidential data.

Right. Instead of a remotely-exploitable information leak, it's most probably reduced to (at worst) a low-grade denial-of-service attack caused by crashing HTTPS server processes no faster than they can respawn.

By that critereon alone, I do surely wish OpenSSL had just stuck to the dog-standard malloc() rather than cowboying up their own.

Comment: Re:This may be a dumb question, but... (Score 1) 445

by idontgno (#46728065) Attached to: Heartbleed Coder: Bug In OpenSSL Was an Honest Mistake

Many compilers precalculate arithmetic expressions consisting of constants, replacing them at compile-time with the result value constant.

I believe the different constants can be deduced from Section 4 of the original RFC proposing the TLS hearbeat message:

4. Heartbeat Request and Response Messages

The Heartbeat protocol messages consist of their type and an
arbitrary payload and padding.

struct {
HeartbeatMessageType type;
uint16 payload_length;
opaque payload[HeartbeatMessage.payload_length];
opaque padding[padding_length];
} HeartbeatMessage;

The total length of a HeartbeatMessage MUST NOT exceed 2^14 or
max_fragment_length when negotiated as defined in [RFC6066].

type: The message type, either heartbeat_request or

payload_length: The length of the payload.

payload: The payload consists of arbitrary content.

padding: The padding is random content that MUST be ignored by the
receiver. The length of a HeartbeatMessage is TLSPlaintext.length
for TLS and DTLSPlaintext.length for DTLS. Furthermore, the
length of the type field is 1 byte, and the length of the
payload_length is 2. Therefore, the padding_length is
TLSPlaintext.length - payload_length - 3 for TLS and
DTLSPlaintext.length - payload_length - 3 for DTLS. The
padding_length MUST be at least 16.

HeartbeatMessageType is a single-byte enumeration (documented in Section 3) and the payload_length is a uint16 (two bytes)... and the packet always requires 16 bytes of padding, so that's the 1, the 2, and the 16.

Comment: Re:Power? (Score 1) 630

by idontgno (#46708977) Attached to: Navy Debuts New Railgun That Launches Shells at Mach 7

I remember hearing a proposal that the barrel (or rail) would be magazine-fed along with the armature and round. Kinda defeats the probable space/weight advantages over a chemically-propelled round, but at least you don't have tons of explosive propellants in the magazine.

I don't know how serious the proposal was. But it would solve the rate-of-fire issue.

Comment: Re:It's not trending. (Score 1) 371

by idontgno (#46696667) Attached to: Smart Car Tipping Trending In San Francisco

So, this explains why you were tipping those "Smarts".

What about your criminal confederates? More illegal thrill-seeking? Someone secretly paying to have the cars tipped? Voices in their heads? Hatred of tiny four-wheeled tin boxes arrogantly pretending to be cars?

The last is the reason I do it. I mean, would do it. Although I don't. Really.

Comment: Re:Application and driver compatibility (Score 1) 245

by idontgno (#46683509) Attached to: Slashdot Asks: Will You Need the Windows XP Black Market?

It is if you have operators and engineers that have any brains

But out here in reality, what operators and engineers have in brains they make up for by the absence of give-a-damn. Laziness can trump smarts every day of the week, and the path of least resistance is a damn fine malware vector.

that have any brains, There are tons

Speaking of brains... that's a comma splice. If English is your first language, please return to third grade to learn not to do that.

There are tons of CNC machines not being infected out there.

There were tons of numerically controlled machines out there infected by this very mechanism. The fact that it wasn't CNC machines this time doesn't mean it can't be CNC any time in the future. The attack is feasible.

Comment: Re:modular but never taken advantage of (Score 1) 62

You're not the target demographic. That doesn't mean it's a bad idea. These kinds of phones will be bought by tech nerds in their 20s.

Glassholes, you mean.

modular IBMPC / overclocking crowd.

Modular PC. Not exactly the stirring precedent I'd go looking for.

Shortest distance between two jokes = A straight line