🚀 go-pugleaf

Because IHUG's constantly crashing newsserver, I am reposting this

Quoting http://www.theregister.co.uk/content/1/14592.html
>The system doesn't just deal with incoming files - it applies to "every
>piece of code executing on the machine." There's a list of 40 different
>kinds of executables, and policies can be set to define which of them 
>can be run, the most secure policy being to run only signed applications.

With a pro-active digital signature system, a larger organization 
( or small remotely managed site ) can ditch the third party resident 
anti-virus programs *alltogether*.

Someone from Microsoft must have been reading my posts!!!
See
  http://x61.deja.com/[ST_rn=ps]/viewthread.xp?AN=628264384
  http://x61.deja.com/[ST_rn=ps]/viewthread.xp?AN=672311516

http://www.deja.com/[ST_rn=ps]/threadmsg_ct.xp?AN=673714160&fmt=text
Quoteing myself in the latter from "Re: Linux ( and Unix ) virus :Overview"
thread, on what you can do to secure an opensource linux/BSD system

+>Hardwiring configuration, allowing administrators to hard lock options
+>for users and applications on a case by case basis, constraining scripting 
+>engines, digital signatures, constrained user shells and file selection
+>widgits , preventing user applications from creating/modifing 
+>executables/scripts,  etc etc etc, all now possible. 
+>( Even down to digital signature checking for every executable, 
+>  dynamic library and script before execution - cached checksum
+>  with refetch from trusted servers on failure )
        
David Mohring - Vindicated