USENIX WOOT 2015 Call for Papers
usenix.org
usenix.org
USENIX WOOT is the academic equivalent of Black Hat or CanSec. It's a software security conference with a special focus on "offensive" security: vulnerability research, exploit development, and technology failures that lead to those things.
If you were going to summarize the point of WOOT in one sentence: it's an effort to cross-pollinate academic research with industry research that works by getting the kind of work that would normally be submitted to Black Hat, CanSec, Defcon, RECON, and ShmooCon and also getting it into the academic cite record.
I'm trying to get WOOT to do a better job of engaging the open source and startup communities.
WOOT does a pretty good job of getting contributions from the "software security industry" (consultancies, security product companies, security research labs). But more and more interesting and relevant work is being done in the context of small projects. If you've built, say, a website that processes financial transactions, and had to build up countermeasures for fraud that's work that's relevant to WOOT, and WOOT is interested in publishing it. If you've build a NoSQL database and had to come up with a threat model to deal with new kinds of injection attacks, or to deal with malicious cluster nodes: totally WOOT-worthy. As long as the work focuses on the "attacker" side of the security problem, it's relevant to us.
You don't need to write a paper to submit! We're interested in outlines and sketches of work, and will help you turn that work into a paper. You don't have to write speculatively for us.
WOOT is relatively high profile. An accepted WOOT paper is a meaningful contribution to the academic literature. We'd like to see more of it come from the kinds of people who contribute to HN.
The proceedings from the previous 8 years of WOOT are available online. Check out last year's, which includes (for instance) some pretty great work from Dan Boneh, Grant Ho, Niels Provos and Lucas Ballard:
https://www.usenix.org/conference/woot14/workshop-program
Happy to answer questions!
I am less excited however, that with these goals you decided to have the workshop so close to CCC Camp. I assume that was USENIX scheduling, but kinda rough for people going to CCC Camp to go to WOOT too.
Edit: I originally thought this was during CCC Camp and freaked out. My calendar was wrong, sorry about that.
I'm glad what we're trying to do this year makes sense. Shoot me ideas for program committee members! We really want to get some new faces this year.
Unlike in theoretical CS, a lot of work in WOOT's domain is done in the industry. So WOOT makes an effort to solicit contributions from the industry.
Does that make more sense?
† I hate that term, but look at the topics in the CFP to see what it means
The thing is technology companies, unlike pharmaceutical companies, automative companies, defence companies, or any other direct application of hard sciences, are more open to the idea of sharing their work with the rest of the community (academic or otherwise). People at Google for example has written highly cited papers about distributed systems, early compilers work has been largely influenced by industry (think FORTRAN). Even academics developed many ideas about their "academic" work while producing work in the industry. One example is the Norcroft compiler suite (first ARM compiler), is developed by two Cambridge academics and then lead to influential papers in compiler optimisations.
I think it is just the case that people in computer science do not look down on people who did not go through rigorous academic training. The barriers to entry for computer science in most areas is fairly low compared hard sciences because you do not need a fancy laboratory to get results.
Also you clearly have not even bothered to look through previous workshops more than half of the papers have university associations.
This science, unlike physics, or biology, is still at its infancy. People of all sort of backgrounds can contribute massively and they do so.
The WOOT Program Committee selects papers; I'm just one of them. But I should be able to give pretty good feedback.
Being on the PC isn't a huge time commitment; it's just reading papers and calling out the particularly interesting ones.