<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 10/27/2013 10:00 AM, Pete Hardie
wrote:<br>
</div>
<blockquote
cite="mid:CAMdBqcOhpPKBr1pYLXTTAuL2WSdsH3Uqf5=7Rfs9UasaWAZ_=w@mail.gmail.com"
type="cite">
<div class="gmail_default"
style="font-family:arial,helvetica,sans-serif;font-size:small">
Out of curiosity, what sort of things are you referring to in
the Python stdlib?</div>
</blockquote>
<br>
It's not "what sort" but "how much".<br>
<br>
It's extremely time-consuming and thus therefore very improbable to
be able to audit the entire Python stdlib, plus the entire python
VM, plus the entire interpreter, plus the generator, and be able to
say "Yes, this 12-line Python program is proved secure."<br>
<br>
Those twelve lines on their own might be secure, <i>assuming that
all invariants are held that the programmer assumes</i>. Of
course, that depends on far more than the 12 lines of code! That
audit then has a domino effect.<br>
<br>
However, if you are working in C, you don't even really need to
worry about the compiler itself, just the compiler's output. If you
can easily map a line of C to one or more assembler statements (and
you can do that quite easily), then you can prove the program's
security far more easily. After all, then you KNOW where the chains
of logic go—they're static, not dynamic.<br>
<br>
— Mike<br>
<br>
<div class="moz-signature">-- <br>
<table border="0">
<tbody>
<tr>
<td> <img src="cid:part1.01050304.05090706@naunetcorp.com"
alt="Naunet Corporation Logo"> </td>
<td> Michael B. Trausch<br>
<br>
President, <strong>Naunet Corporation</strong><br>
☎ (678) 287-0693 x130 or (855) NAUNET-1 x130<br>
FAX: (678) 783-7843<br>
</td>
</tr>
</tbody>
</table>
</div>
</body>
</html>