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.
Trump dice que EE.UU. atacó una zona portuaria venezolana, que sería la primera ofensiva terrestre en el país caribeño
El presidente de Estados Unidos, DonaldRTVE.es/Agencias (RTVE.es)
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).
TL;dr: Master-keyed locks have fundamental, exploitable weaknesses.
But I wasn't ready for what happened next.
1/
Fellas I went to a professional sports game tonight and it was $15 for a can or tap beer.
FIFTEEN DOLL HAIRS
Matt Blaze
in reply to Matt Blaze • • •Unexpectedly, my paper got some press attention. @jswatz_tx found it and wrote a short piece in the NY Times.
And then locksmiths freaked out. I mean completely lost it. They were very upset, not so much that a very common lock design had a basic security flaw, but that an "outsider" found it and had the poor moral character to make it public.
I started getting weird death threats. They doxed me ("let's see what kind of lock the bastard has on HIS house")
2/
Matt Blaze
in reply to Matt Blaze • • •A trade publication called The National Locksmith ran monthly guest editorials in which prominent members of that profession were invited to denounce me. My favorite quote, from a locksmith named Billy Edwards, who had written a book on master keying, and who took my paper rather personally.
3/
Matt Blaze
in reply to Matt Blaze • • •I should point out that master keying was about a century old at the time, and while the mechanical details weren't secret, locksmiths tended to regard the inner workings of locks as "restricted knowledge", rather like a medieval trade guild. I didn't understand this.
What took me by surprise was how different the physical security wold's attitude was compared with that of my community, where the ethics of discussion of vulnerabilities has long been essentially settled in favor of openness.
4/
Matt Blaze
in reply to Matt Blaze • • •Essentially, their argument was that this would be a huge pain and expense to fix, and so we are all better off just keeping it on the down low. And that kind of worked, for about a hundred years, until more open communities - like computer security research - started looking seriously at locks (as both metaphors and as interesting mechanisms in their own right).
I see their point, even if I personally reject it. But in the age of the Internet, you just can't keep this kind of stuff secret.
5/
Matt Blaze
in reply to Matt Blaze • • •Anyway, my intent in looking at locks and publishing my paper wasn't to disrupt the lock industry. I believed, as I still do, that mechanical locks and physical security have quite a bit to teach computing, but also that the abstract techniques of cryptography and computer security can illuminate weaknesses that are hard to see when looking at systems in strictly mechanical terms.
My attack is intuitive and obvious to cryptographers, but rather subtle without our field's tools.
6/
Matt Blaze
in reply to Matt Blaze • • •I never did reach a truce with the locksmiths. A couple years later, I met Billy Edwards, the author of that editorial denouncing me, at a trade show, and when he learned who I was he refused to shake my hand and asked me to leave him alone.
I wish he had seen things differently, but I can respect that he was coming from a place of genuine concern, even if I think his approach was wrong.
To this day, I worry that I'm pretty screwed if I get locked out of my house.
7/7
Matt Blaze
in reply to Matt Blaze • • •NB: While I never intended to piss off locksmiths with my master keying paper, I did write a followup a couple years later about safes and safecracking, partly out of spite.
mattblaze.org/papers/safelocks…
TL;dr: We can learn a lot from safes and safe locks, and the frameworks of cryptography and computer security are applicable there, too. The fact that our learning about this subject makes people in that industry upset is just a bonus.
Matt Blaze
in reply to Matt Blaze • • •Matt Blaze
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.
Matt Blaze
in reply to Matt Blaze • • •