that it faced in its infancy. ❖ Connections were unreliable, so there is a lot of error checking. ❖ Memory was scarce, so protocols are low on overhead.
six dumbest ideas. ❖ We built it that way, but we couldn't fix it. ❖ Too many people depended on it. ❖ We were too busy building the next addition (which repeated the 6 dumbest ideas)
on a regular basis. There are probably another 20 or 30 installed that I use every couple of months or so. I still don't understand why operating systems are so dumb that they let any old virus or piece of spyware execute without even asking me. That's 'Default Permit.'" -Marcus Ranum
of everyone that is NOT allowed to take money out of your checking account. ❖ - OR - ❖ Make a list of everyone that IS allowed to take money out of your checking account.
it means that you already screwed up somewhere. ❖ Combat this with "Artificial Ignorance." ❖ Enumerating badness is internal evidence of our security failures.
to external evidence of our failures. ❖ If your system is hacked, then you know there is a flaw. Patching is a quick fix until you can re-engineer the problem away.
shouldn't apply vendor patches. ❖ You have to work with the security tools that you're given. ❖ This does NOT mean that you shouldn't patch software you write. ❖ But you better be working on fixing the root cause or you'll just find yourself writing another patch next month.
packet will make your database crash. ❖ Good Idea: Issue a patch to stop that packet while you study the problem and fix the underlying issue. ❖ Dumb Idea: Issue a patch to stop that packet.
I don't think there is much you can do about it. ❖ We all marvel at Danny Ocean stealing from the Bellagio. ❖ We don't marvel at the guy that built a safe so secure that it took 11 people months of planning to break in.
this one. ❖ It isn't the first time that Marcus and I have disagreed. ❖ What he is trying to say is that rather than educate users, we should engineer systems so that the user doesn't need to be educated.
real world where people didn't engineer things that way. ❖ My modified rule: if user education is the only thing standing between you and failure, then prepare to fail.
people want to upgrade a working system just for the sake of upgrading. ❖ Changes are the enemy of stability, we learned that last 2 weeks ago. We should only change when we have a compelling reason to change.
show up whenever we see one of the six dumbest ideas in this course. ❖ Marcus didn't give me permission to do that. He will likely punch me when he finds out.