Timeline for Secure software development checklist [closed]
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 19, 2015 at 9:05 | vote | accept | BrainSCAN | ||
| Mar 18, 2015 at 8:38 | history | closed |
Eric G Jens Erat RoraΖ Iszi M'vy |
Not suitable for this site | |
| Mar 17, 2015 at 20:45 | answer | added | Steve Sether | timeline score: 2 | |
| Mar 17, 2015 at 18:29 | answer | added | atdre | timeline score: 0 | |
| Mar 17, 2015 at 17:24 | answer | added | Eric G | timeline score: 3 | |
| Mar 17, 2015 at 17:23 | review | Close votes | |||
| Mar 18, 2015 at 8:38 | |||||
| Mar 15, 2015 at 19:36 | answer | added | Jacques | timeline score: 0 | |
| Mar 15, 2015 at 19:25 | answer | added | John Deters | timeline score: 0 | |
| Mar 11, 2015 at 15:39 | comment | added | Lucas Kauffman | I'm outspoken in saying: if you think memory safe languages don't have security caveats, you should have a look at the above. | |
| Mar 11, 2015 at 15:35 | comment | added | boggart | I'm outspoken in saying: skip the C programming and use a memory safe language. | |
| Mar 11, 2015 at 15:19 | history | asked | BrainSCAN | CC BY-SA 3.0 |