While I don't feel buffer overflows are something to ignore, from what I see the developer never actually said "unexploitable."

From the "skeptical glibc developer" link:

> if not maybe the one byte overflow is still exploitable.

Hmm. How likely is that? It overflows in to malloc metadata, and the
glibc malloc hardening should catch that these days.

Probably to protect him from more reporters who like to find obsessively private people, poke them with a stick and post everything online.

At least they'd have a good reason this time.

But 4K ought to be enough for anybody!

... but I'm not sure how it's a "Relativity Shock" as the second links suggests.

Upon thinking about a marble rolling on a rubber sheet I immediately see two big differences between it and a planet moving in space: (i) the marble.. well.. rolls along the sheet, which planets don't do while moving through space; and (ii) the rubber sheet doesn't propagate disturbances at the speed of light (or anywhere close to it).

And BSD is obviously a particularly good example for networking code.

Tell them you feel strongly about retaining your rights over your software and see if they maintain that it's required to transfer rights to them. Get the facts from them. If they say you have to, but you really don't want to, don't take the job. Of course, make sure you get it in writing.