Se below.
Soru, kind of busy now, so I didn't have time to explain more
-------- Original Message --------
Subject: Re: Remarks on syslog-sign (draft 07)
Date: Tue, 28 Jan 2003 07:27:06 -0800 (PST)
From: Chris Lonvick <[EMAIL PROTECTED]>
To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
Hi Albert,
I see your point now. Please bring it back up on the mailing list. If
you can, please indicate some revisions to the syslog-sign ID that will
straighten it out. :-)
Thanks,
Chris
On Wed, 22 Jan 2003, [EMAIL PROTECTED] wrote:
>
>
> [EMAIL PROTECTED] wrote:
> > Hi All,
> >
> > Been a bit busy lately, but catching up soon, I hoop.
> > But a quick responds on a comment on a comment ..
> >
> >
> >>>> ** The TAG is defined to be ending ('MUST')with a _colon_.
> >>>> This wrong, as rfc3164 defines it can end with a _space_
> >>>> Adv Rewrite: it terminates with any not alfanum char.
> >>>
> >
> >
> >> We discussed (a long time ago) that the TAG should be included in the
> >> HEADER rather than in the MSG for people writing code.
> >
> >
> > Very true, It was I who made the suggestion ...
> >
> >> This should mean that the TAG should be able to contain things like:
> >> syslog[1234]:
> >> Since the next character may, or may not be a space, [...]
> >
> >
> >> I'll suggest that the colon stay.
> >
> >
> > The point is, syslog-sign messages should be syslog-rfc3164 "parsable".
> > And, syslog-sign-deamons should handle "old" syslog messages.
> > In other words: when a UDP message is arriving over the
syslog-port, the
> > daemon should be able to handle (so parse) it. WITHOUT knowing it is
> > syslog-rfc3164 or -sign.
> > Based on my implementation, we need the space "definition" in the
> > syslog-sign rfc, to make a 100% correct implementation.
> >
> > I have to look up the work for details, I hope you trust "my word" :-)
> >
> > NB traditional syslog can be without the colon!
> >
> >
> >> That does bring up a point, however. In "traditional" syslog
messages,
> >> there is nothing between the ":" and the message itself in many cases.
> >> Should there be a space between the ":" and the Signature Block,
and the
> >> Certifiate Block in the syslog-sign messages? If so then a Signature
> >> Block would look like:
> >> syslog[1234]: @#sigSIG 0111 ...
> >> and the Certificate Block would be:
> >> syslog[1234]: @#sigCER 0111 ...
> >
> >
> > Based on early posting(s): I suggest to allow one or more spaces
between
> > ANY 2 syslog-sign-fields. (for reading). And send 1 space between any 2
> > fields. Personally, I would like to have 2 spaces at the frond. It make
> > (manual) parsing nice. But that only a matter of style.
> >
> >
> > --ALbert Mietus
> > Sent prive mail to: [EMAIL PROTECTED]
> > Sent business mail to: [EMAIL PROTECTED]
> >
>
>
> --
> --ALbert Mietus
> Sent prive mail to: [EMAIL PROTECTED]
> Sent business mail to: [EMAIL PROTECTED]
>
>
--
--ALbert Mietus
Sent prive mail to: [EMAIL PROTECTED]
Sent business mail to: [EMAIL PROTECTED]
