Folks:
Since someone start a "let's introduce ourselves" thread I'll jump
in to it. I have been advocating an effort like this for quite a while as
the current protocol and implementations are lacking several features that
I consider critical (i.e., assured delivery, security/authentication,
preservation of a cascading host trail, etc.). I have hacked to death
Eric Allman's (oh great god of sendmail) implementation with the regular
expression parser and still find it limiting.
If the final composition of the WG has not been settled I would
be more than happy to lend my efforts to this endeavour...otherwise I
will just hang out on this list and offer what I can...
Let's all put in a great effort and get it right this time!!!!!
TRAVEL: At Scient SF as of 27th of Sept. -- Traveling often, no sched. yet
Regards,
b c++'ing u,
%-) sjs
-------------------------------------------------------------------------------
Weebles wobble, but they don't fall down!!!
-------------------------------------------------------------------------------
Stefan Jon Silverman SJS Associates, N.A., Inc.
698 West End Avenue - Suite 15-B
New York, NY 10025
E-mail: [EMAIL PROTECTED] Phone: 212 662 9450
Website: http://www.sjsinc.com Fax: 212 662 9461
Text-Page: [EMAIL PROTECTED] Cell: 917 929 1668
-------------------------------------------------------------------------------
In San Francisco
Scient: 415 591 3973 [EMAIL PROTECTED] (MD - Infrastructure Arch.)
Home: 415 929 0406 [EMAIL PROTECTED] (1155 Jones, Apt. 303 - 94133)
-------------------------------------------------------------------------------
On Tue, 19 Oct 1999, Balazs Scheidler wrote:
> Hi,
>
> I was happy to see that the IETF finally found out that the current syslog
> protocol is hmm... a bit limited. I would like to offer my help to the
> working group, although I am sure most of you are more clever than
> me.
>
> I'm the author of a syslog implementation, named syslog-ng, which is
> originally inspired by Darren's nsyslog. (Since then it has been rewritten
> from scratch) I was about to begin designing a new inter-syslog protocol,
> which would allow authentication and encryption, and would make it easier to
> parse messages.
>
> My suggestion is to try to summarize the earlier proposals (found in the
> project charter of this WG). I've quite closely seen Darren's nsyslog, and have
> just read Schneier's Secure logging paper. So while it's fresh, I would like
> make some comments on the latter paper.
>
> Schneier's suggestion is more a log file format, than a protocol, but his
> ideas would be worth considering. The best idea is the log message type
> field, which would allow finegrained access to log messages. I think the
> worst in it is that starting a log file would require two-way communication
> with a central log server.
>
> Darren's nsyslog is a syslog implementation using MAC to protect messages
> while in transit, and to protect messages stored in logfiles.
>
> My syslog-ng's basic idea comes from Darren's nsyslog, but it's completely
> reimplemented from scratch. It still has no cryptographic capabilities, I
> was just beginning to implement that.
>
> I don't know the last one, ssyslog.
>
> --
> Bazsi
> PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
> url: http://www.balabit.hu/pgpkey.txt
>
