For your convenience<p>wget <a href="http://www.cl.cam.ac.uk/~rja14/Papers/SEv2-{toc,pref,acks,biblio,index}.pdf" rel="nofollow">http://www.cl.cam.ac.uk/~rja14/Papers/SEv2-{toc,pref,acks,bi...</a><p>curl -O <a href="http://www.cl.cam.ac.uk/~rja14/Papers/SEv2-c[01-27].pdf" rel="nofollow">http://www.cl.cam.ac.uk/~rja14/Papers/SEv2-c[01-27].pdf</a>
One of the greatest frustration for those who have been working in infosec for a while is that the same issues keep coming up. As an industry, technology security should be getting better and it's not. This is probably the best book for developers of any level to learn how and why to make tiny code changes to hugely improve security.<p>Downloading and combining all the PDFs here is left as an exercise to the reader, but please read this book. It is a very well written explanation of how to think about making things more secure.
Direct link to the PDF of the full book linked to from the page: <a href="http://www.cl.cam.ac.uk/~rja14/musicfiles/manuscripts/SEv1.pdf" rel="nofollow">http://www.cl.cam.ac.uk/~rja14/musicfiles/manuscripts/SEv1.p...</a><p>I have to say that this is the only course book from Cambridge I've reread multiple times.