Philae’s Troubled Landing (2018)
publications.computer.org
publications.computer.org
(At least, that's my reading of the brief quotes from the original report; so much of the context has been removed or aggressively summarized that it's hard to be sure what they're talking about.)
The "developer's confession" part seems to insinuate that a software problem was to blame, but nowhere in the article is that actually stated.
When you are a lighweigg tlander in a very low gravity of a comet, the last thing you need to be doing is shooting harpoons at the icy ground. The harpoons are not going to stick well/at all and the very act of firing them is going to send you careening off back into space.
The referenced scientific article is titled "A Comet Revisited: Lessons Learned from Philae's Landing". It deals with more mistakes than just the crash.
So he is not even in contradiction with the experts.
Given the nature of the comms- to a device in the expanse of space- securing the transmission from malicious users seems like the last thing they should worry about. It’s more the accidental corruption of data, hence something like a CRC or simple MAC are sufficient for the circumstances. Why waste energy and CPU cycles on something you don’t actually need?