Annotated edit history of
SecureCodingReview version 3, including all changes.
View license author blame.
| Rev |
Author |
# |
Line |
| 1 |
DanielLawson |
1 |
Secure Coding: Designing and Implementing Secure Applications -- an [O'Reilly] book by Mark G. Graff and Kenneth R. van Wyk. |
| |
|
2 |
|
| |
|
3 |
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. |
| |
|
4 |
|
| |
|
5 |
Due to it's abstract nature, it isn't tied to one programming language or platform and shouldn't date too quickly. |
| |
|
6 |
|
| 2 |
StuartYeates |
7 |
I (StuartYeates) read it cover-to-cover on a plane trip after I got it at [OpenSourceConvention]. |
| |
|
8 |
|
| |
|
9 |
The [O'Rielly page|http://www.oreilly.com/catalog/securecdng/] and the [authors page| http://www.securecoding.org/] for the book. |
| 1 |
DanielLawson |
10 |
|
| |
|
11 |
---- |
| 3 |
AristotlePagaltzis |
12 |
CategoryBookReview |
