=================================================================== RCS file: /cvsrepo/anoncvs/cvs/www/Attic/press.html,v retrieving revision 1.607 retrieving revision 1.608 diff -u -r1.607 -r1.608 --- www/Attic/press.html 2016/04/24 20:08:50 1.607 +++ www/Attic/press.html 2016/08/15 02:22:11 1.608 @@ -6,7 +6,7 @@ - + @@ -464,7 +464,7 @@ Code written under NDA will make it difficult to improve it in the future because somebody signed an agreement to keep the required hardware documentation secret. For the OpenBSD project -NDAs are never acceptable. +NDAs are never acceptable.

@@ -807,7 +807,7 @@ support for UltraSPARC III on sparc64, improvements to ipsecctl, a new RCS implementation, and much more. Includes a reminder to "show your support for the project by -placing your pre-orders today!" +placing your pre-orders today!"
@@ -1464,7 +1464,7 @@ fully dedicated to OpenBSD..." Great coverage of the OpenBSD Porting Hackathon: people, ports, beer, ... Contains a link to - + pval's summary slides.
@@ -3712,7 +3712,7 @@ making software vendors liable for bug-ridden products? Or rooting out insecure Microsoft products like the troubled SQL server in favor of more secure open-source solutions like -OpenBSD?" +OpenBSD?" I can scarcely believe that Slate's owner Microsoft is paying them to write this stuff (nor that Koerner thinks OpenBSD is a database :-)). Finally: "Nothing so bold is forthcoming in the Strategy. Which is @@ -3753,7 +3753,7 @@ Support, Software Development, Security, and Research. One unexpected result was the degree to which Security depends on FOSS. Banning FOSS would remove certain types of infrastructure components (e.g., -OpenBSD) that currently help +OpenBSD) that currently help support network security. It would also limit DoD access to, and overall expertise in, the use of powerful FOSS analysis and detection applications that hostile groups could