| 1 | == Security Talk from 2014 WebKit Contributors Meeting == |
| 2 | |
| 3 | No notes were taken during the meeting, but below are some resources of subjects talked about during the session. |
| 4 | |
| 5 | === Clang Address Sanitizer (ASan) === |
| 6 | |
| 7 | Google Code page for clang's address sanitizer: [https://code.google.com/p/address-sanitizer/ Google address-sanitizer project] |
| 8 | |
| 9 | Documentation for Clang 3.5 for ASan and others: [http://clang.llvm.org/docs/UsersManual.html#controlling-code-generation Clang Sanitizers] |
| 10 | |
| 11 | === Fuzzing === |
| 12 | |
| 13 | Please contact David Kilzer (ddkilzer on IRC) if you want to discuss Apple's fuzzing efforts. |
| 14 | |
| 15 | === Clang Undefined Behavior Sanitizer (UBSan) === |
| 16 | |
| 17 | Documentation for Clang 3.5 for UBSan and others: [http://clang.llvm.org/docs/UsersManual.html#controlling-code-generation Clang Sanitizers] |
| 18 | |
| 19 | Chris Lattner's excellent three-part series about undefined behavior in C (and C++): |
| 20 | * [http://blog.llvm.org/2011/05/what-every-c-programmer-should-know.html What Every C Programmer Should Know About Undefined Behavior #1/3] |
| 21 | * [http://blog.llvm.org/2011/05/what-every-c-programmer-should-know_14.html What Every C Programmer Should Know About Undefined Behavior #2/3] |
| 22 | * [http://blog.llvm.org/2011/05/what-every-c-programmer-should-know_21.html What Every C Programmer Should Know About Undefined Behavior #3/3] |