RE: [logs] SDSC Secure Syslog

nwhiteat_private

Slashdot has picked this up w/the usual peanut gallery comments :-)

http://slashdot.org/articles/02/12/05/1554209.shtml?tid=172

-Noah


> -----Original Message-----
> From: Tom Perrine [mailto:tepat_private]
> Sent: Thursday, December 05, 2002 1:32 AM
> To: Log Analysis Mailing List
> Subject: [logs] SDSC Secure Syslog
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> 
> Announcing SDSC Secure Syslog (Release Candidate)
> 
> The Security Technologies group at the San Diego Supercomputer Center
> (SDSC) is pleased to announce the early availability of "SDSC secure
> syslog", a replacement for the standard Linux/UNIX syslog daemon that
> adds security and performance features, while retaining backwards
> compatibility.
> 
> We believe it is the first syslog implementation to target
> "syslog-reliable" (RFC 3195) functionality and it is the first syslog
> targeted at very high performance and forensically-sound auditing.
> 
> The project home page is at:
> http://security.sdsc.edu/software/sdsc-syslog
> 
> Authors of other RFC3195-compliant software, please contact us at
> sdscsyslogat_private, so we can explore inter-operability testing with
> you.
> 
> This is a release candidate for version 1.0.
> 
> SDSC syslog is intended as a high-performance and high-security
> replacement for "syslog classic".  It is intended for sites with high
> volumes of syslog transactions that also want security and integrity
> features and compatibility with new audit standards.
> 
> SDSC syslog is a complete new design incorporating new features and
> capabilities, including:
>     *modular
> 	*input modules for socket, UDP network connections,
> 	    TCP/BEEP, etc.
> 	* a message switch to perform log message routing
> 	* multiple output modules for UDP, TCP/BEEP, "syslog
>         classic" files, structured files
> 
>     *multi-processing - handles more input syslog steams, provides
>         better scalability
>     *support for draft standards such as "syslog-reliable" (RFC
>         3195, syslog messages over BEEP)
> 
> 
> This Release Candidate does not yet have complete support for
> RFC 3195, but is fully backwards compatible with "syslog classic"
> using 514/UDP.
> 
> Note that this software ***currently*** carries the standard
> University of California copyright statement, permitting free use for
> educational and non-profit activities.  We are exploring a transition
> to an Open Source license, such as the "BSD license".  This requires
> completion of the pending approval of the University of California.
> 
> - --
> Tom E. Perrine <tepat_private> | San Diego Supercomputer Center
> http://www.sdsc.edu/~tep/     |
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.6 (GNU/Linux)
> Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/>
> 
> iQCVAwUBPe7yxhTSxpWcaAFRAQF3QwP/VHEvjQLhyNCb3mWmTHsu/OW7AMmltDmt
> t8gqRSMokjOMJti03/4/1Oji3u6YBiyZ+oKP/YsaqGjeFKjhV1qZcqagjZi48pvD
> OthgG+J9BHAaexILVNb0+rLQeWseeJDJyyYHIui8po5Fnexfh8jp4Am8HG2lbVIv
> IoekSFrExIc=
> =lO5H
> -----END PGP SIGNATURE-----
> _______________________________________________
> LogAnalysis mailing list
> LogAnalysisat_private
> http://lists.shmoo.com/mailman/listinfo/loganalysis
_______________________________________________
LogAnalysis mailing list
LogAnalysisat_private
http://lists.shmoo.com/mailman/listinfo/loganalysis