Last week I posted an announcement of SDSC's secure syslog project to the Loganalysis mailing list. The announcement was fully buzzword-compliant, as required by tradition :-) It was also /.'ed
Christopher Lonvick <[EMAIL PROTECTED]> has asked that I post the same announcement here (see below). We are *really* looking for other RFC 3195 compliant syslog systems to test with. Are there any, especially non-proprietary? ---------------------------------------- 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 [EMAIL PROTECTED], 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 <[EMAIL PROTECTED]> | San Diego Supercomputer Center http://www.sdsc.edu/~tep/ |
