Differences between current version and predecessor to the previous major change of SecureCodingReview.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 3 | Last edited on Thursday, September 23, 2004 5:06:06 pm | by AristotlePagaltzis | |
| Older page: | version 1 | Last edited on Sunday, August 22, 2004 7:29:52 pm | by DanielLawson | Revert |
@@ -3,8 +3,10 @@
A great book on the philosophy and theory behind secure design and implementation of applications and systems. Includes a great deal of insight and any number of things to ponder, but no code to steal or hard-coded list of absolute priorities. So while it won't help if you're shipping an program at the end of the week and it __has__ to be secure, it will help you understand the security trade-offs in your next system and point you towards where you might start improving things.
Due to it's abstract nature, it isn't tied to one programming language or platform and shouldn't date too quickly.
-I (StuartYeates) read it cover-to-cover on a plane trip after I got it at [OpenSourceConvention]
+I (StuartYeates) read it cover-to-cover on a plane trip after I got it at [OpenSourceConvention].
+
+The [O'Rielly page|http://www.oreilly.com/catalog/securecdng/] and the [authors page| http://www.securecoding.org/] for the book.
----
-CategoryBookReviews
+CategoryBookReview
