Re:How to Write Software with Zero bugs – 25 years after qma...
by daneel_w on Tuesday August 22, 2023 @06:30PM
(#37229436)
Does anyone know how qmail has fared since this PDF was written in 2007? Did it make it to 2023 without any bugs surfacing?
[ Parent
| on HN ]
Re:How to Write Software with Zero bugs – 25 years after qma...
by troutwine on Tuesday August 22, 2023 @06:33PM
(#37229464)
It didn't make the transition to 64 bits worth of memory with the record intact. https://lwn.net/Articles/820969/ Although the CVE _is_ from 2005 so perhaps it doesn't count.
Re:How to Write Software with Zero bugs – 25 years after qma...
by literalAardvark on Tuesday August 22, 2023 @08:16PM
(#37230318)
I mean... I'd say expecting a program written for a 32 bit OS to just work on 64 is excessive. And the fix is just to add mildly sane memory limits to the processes, which is an OS level task, thus, not necessarily a bug.
Not that the whole thing was very well handled.
Re:How to Write Software with Zero bugs – 25 years after qma...
by troutwine on Tuesday August 22, 2023 @08:56PM
(#37230588)
I would argue that the fix is for the software to refuse to function if it can detect that it's in an environment where it won't function safely, to fail-closed rather than fail-open.
Re:How to Write Software with Zero bugs – 25 years after qma...
by literalAardvark on Sunday August 27, 2023 @06:20AM
(#37281229)
Fair enough, that's a good idea.
Re:How to Write Software with Zero bugs – 25 years after qma...
by commandersaki on Tuesday August 22, 2023 @06:34PM
(#37229478)
Re:How to Write Software with Zero bugs – 25 years after qma...
by emailsysadmin on Wednesday August 23, 2023 @01:15AM
(#37232130)
no one in their right mind keeps qmail-verify active for many reasons.