Hi all.<br><br>Sorry for the lack of replies... I've been... umm... distracted by Wesnoth (<a href="http://www.wesnoth.org">http://www.wesnoth.org</a>) :-).<br><br><div><span class="gmail_quote">On 3/2/07, <b class="gmail_sendername">
Ron Teitelbaum</b> <<a href="mailto:Ron@usmedrec.com">Ron@usmedrec.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
+1<br><br>Michael,<br><br>I've been meaning to review your work, have you made any progress on it.<br>Have you considered putting together a protection profile? Could we use<br>your work as a starting point for FIPS? How far away from a working model
<br>are you? Revolutionary is good, as long as the target is realistic.</blockquote><div><br>What's a protection profile? I wouldn't use my work as a starting point for the FIPS stuff until it works at least as well as the
3.9 image.<br><br>Progress so far has been slow. Basic classes like Namespace have been tentatively made; I'm now modifying the Browser to be able to look at them.<br><br>After that, I've got several other tasks:<br>
<br>- Find a way of storing source code so that Namespaces are preserved. I might let the squeak.changes file format bit-rot (eventually deprecating it completely) and instead modify Monticello to preserve Namespace structure.
<br> <br>- Make sure other tools in PlusTools work with Namespaces.<br><br>- Then I start the massive task of converting core Squeak classes to use Namespaces: Kernel, Collections and Networking.<br><br>- Then I take a very serious look at Islands and Squeak-E, salvaging what I can for a secure Squeak.
<br><br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I can't realistically offer to help for at least another 6 months, I'm
<br>swamped. But maybe we can have a more in depth conversation on the<br>Cryptography Team List.<br></blockquote></div><br>Sure.<br><br>Michael.<br>