{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2025,6,19]],"date-time":"2025-06-19T04:43:29Z","timestamp":1750308209055,"version":"3.41.0"},"reference-count":2,"publisher":"Association for Computing Machinery (ACM)","issue":"4","license":[{"start":{"date-parts":[[2004,6,1]],"date-time":"2004-06-01T00:00:00Z","timestamp":1086048000000},"content-version":"vor","delay-in-days":0,"URL":"https:\/\/www.acm.org\/publications\/policies\/copyright_policy#Background"}],"content-domain":{"domain":["dl.acm.org"],"crossmark-restriction":true},"short-container-title":["Queue"],"published-print":{"date-parts":[[2004,6]]},"abstract":"<jats:p>Security bug? My programming language made me do it! It doesn\u2019t seem that a day goes by without someone announcing a critical flaw in some crucial piece of software or other. Is software that bad? Are programmers so inept? What the heck is going on, and why is the problem getting worse instead of better? One distressing aspect of software security is that we fundamentally don\u2019t seem to \u201cget it.\u201d In the 15 years I\u2019ve been working the security beat, I have lost track of the number of times I\u2019ve seen (and taught) tutorials on \u201chow to write secure code\u201d or read books on that topic.<\/jats:p>","DOI":"10.1145\/1016978.1016981","type":"journal-article","created":{"date-parts":[[2005,1,26]],"date-time":"2005-01-26T16:33:14Z","timestamp":1106757194000},"page":"44-49","update-policy":"https:\/\/doi.org\/10.1145\/crossmark-policy","source":"Crossref","is-referenced-by-count":0,"title":["Security: The Root of the Problem"],"prefix":"10.1145","volume":"2","author":[{"given":"Marcus J","family":"Ranum","sequence":"first","affiliation":[{"name":"TruSecure"}],"role":[{"role":"author","vocabulary":"crossref"}]}],"member":"320","published-online":{"date-parts":[[2004,6]]},"reference":[{"key":"e_1_2_1_1_1","unstructured":"1\n  .  For information on programmers who started posting patches to remove the warning message visit the Grass GIS (Geographic Resources Analysis Support System) Web site: http:\/\/grass.itc.it\/pipermail\/grassuser\/2000- May\/003586.html.  1. For information on programmers who started posting patches to remove the warning message visit the Grass GIS (Geographic Resources Analysis Support System) Web site: http:\/\/grass.itc.it\/pipermail\/grassuser\/2000- May\/003586.html."},{"key":"e_1_2_1_2_1","unstructured":"2\n  .  Digital Equipment Corporation's version of Unix.  2. Digital Equipment Corporation's version of Unix."}],"container-title":["Queue"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/1016978.1016981","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/dl.acm.org\/doi\/pdf\/10.1145\/1016978.1016981","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,6,18]],"date-time":"2025-06-18T16:31:00Z","timestamp":1750264260000},"score":1,"resource":{"primary":{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/1016978.1016981"}},"subtitle":["Why is it we can\u2019t seem to produce secure, high-quality code?"],"short-title":[],"issued":{"date-parts":[[2004,6]]},"references-count":2,"journal-issue":{"issue":"4","published-print":{"date-parts":[[2004,6]]}},"alternative-id":["10.1145\/1016978.1016981"],"URL":"https:\/\/doi.org\/10.1145\/1016978.1016981","relation":{},"ISSN":["1542-7730","1542-7749"],"issn-type":[{"type":"print","value":"1542-7730"},{"type":"electronic","value":"1542-7749"}],"subject":[],"published":{"date-parts":[[2004,6]]},"assertion":[{"value":"2004-06-01","order":2,"name":"published","label":"Published","group":{"name":"publication_history","label":"Publication History"}}]}}