The greatest piece of advice I was ever given was this: when you stop work for the day, never stop at a 'clean' break point; stop in the middle of something you can finish easily.

That way the next morning you're not confronted with a a dauntingly blank page or an empty function to write, but a half-finished one you can get back into without difficulty.

I can't remember who gave me that advice, but I've stuck to it dogmatically whenever I can.

This entry was edited (9 hours ago)

I was recently reminded of this.

A couple decades ago, I wrote a short paper that described how the basic approaches of cryptography and computer security lead to an efficient and practical privilege escalation attack against master-keyed mechanical locks, which I published in IEEE Security and Privacy (a nerdy computing technical journal).

mattblaze.org/papers/mk.pdf

TL;dr: Master-keyed locks have fundamental, exploitable weaknesses.

But I wasn't ready for what happened next.

1/

This entry was edited (1 day ago)
in reply to Matt Blaze

It occurs to me that people outside the security field might find it odd that we openly publish stuff like this. Why help people who might use the knowledge to do bad things?

There are a number of reasons. The first is that only through open discussion are we able to identify and fix problems. Another, which is what motivated my work, is educational: you can't learn to defend systems unless you understand how they are attacked.

Unknown parent

pleroma - Link to source

feld

@lain wife saw the had wine next to the beer taps. She goes to get wine. No signs saying size of pour, no glasses in sight

$16. They tricked her. It was about a 3.5oz pour in a ridiculous cup that made me think of a child's tea time set

@lain
This entry was edited (1 hour ago)