At [DeepSec] last year i had the pleasure of hearing Ivan Krsti? speak. While some of his arguments had (small) holes in them (which the audience were quick to pounce on), he raised the ugly fact that people like me like to ignore.. That some of us spend a lot more time thinking of elaborate ways to break stuff than we do designing less breakable stuff..
I think for most security "breakers" its an argument that sometimes hits hard, and makes you wonder if you should be refocusing your efforts..
Ivan designed the bitfrost security system for the OLPC and is/was a Harvard academic with strong ties to the Python community. (you can follow his talk schedule here).
It seems, he has just taken a position at [Apple]
We recently wrote a paper contrasting the built in memory protection mechanisms on OSX and its windows counterparts, and concluded the paper with the following lines:
"It can be postulated that OS X currently sits in an unusual niche, staying off the radar of server-attackers while below the threshold to make it an attractive target for attackers wishing to capture large volumes of desktop computers (for botnets or similar activities). Apple would be well advised to make good use of their time in this niche to learn from the mistakes made by those before them, because as their market share steadily rises, they steadily inch closer to moving out of this protected space.... .. We hope that Apple is able to make the necessary improvements before it too is forced into altering its views on generic OS protection mechanisms through the media frenzy that follows public security breaches."
It would seem like with a move like this, Apple are thinking these thoughts too..
/mh








A good builder should have as much fun as a breaker to outsmart his/her opponent.
It's the same game, just at opposite sides.
Just my 2 cnts.
Though I gotta say, lots of bugs are the same, and there's nothing interesting in them...
I think I've heard some people propose that we need more builders than breakers in security, but I don't see why security should be anything other than breakers, builders by their definition are primarily either developers or architects or sysadmins, etc, and their focus is on building things, keeping them operational, making them scale, etc and security is only ever going to be a small part of that, hence it's not really feasible for those people to understand how things break. I fear for a world where se
curity people are actually building systems, we'll fix a few esoteric things, but leave whole other avenues unexplored.
Anyway, every time I think I need to expand my horizons, I try to do something outside of what I know I enjoy, it usually ends up being really, really boring, so I'm over doing what I think I *should* do, and am sticking to what's fun.
Again though, i must confess that in moments of navel gazing i end up wondering if i should be doing more to attack the problem from the other end.. -shrug- old age i think..
1) Where is this paper you publishes and can we have a copy?
2) Do what your good at, and make sure you do it in a way that brings as much benefit. If you are only a breaker, but you disclose appropriately and actively help in fix development, then yay. If you can cross the boundry, then do it. Some people can't be breakers and spend their time defending/fixing let them do what they are good at. Ultimately, the combination of both is needed.
1) As soon as the conf accepts (or kicks it out) we will make it available
2)Yes
:>