In some email I received from Balazs Scheidler, sie wrote: > > > I don't think we need two md5 hash for each log line (chain= and md5=) We > > > could simply include the chain value implicitly in the value of md5. Here's > > > the formula to use: > > [...] > > > > It is necessary otherwise it is possible to end up with a resulting log > > file that cannot be put back together. As far as the sending host is > > concerned, everything is in sequence, but who knows what order they are > > in on the receiving host ? > > You are right if using UDP transport. Using a TCP channel may help this > problem though. This only guarantees ordered delivery to the host, not storage, processing or even relaying onto others. Darren
- Simple authentication of syslog messages for embedded net... Alex Brown
- Re: Simple authentication of syslog messages for emb... Balazs Scheidler
- Re: Simple authentication of syslog messages for emb... Darren Reed
- Re: Simple authentication of syslog messages for emb... Balazs Scheidler
- Re: Simple authentication of syslog messages for emb... Alex Brown
- Re: Simple authentication of syslog messages for... Chris Lonvick
- Simple authentication of syslog messages for embedde... Alex Brown
- Re: Simple authentication of syslog messages for emb... Chris Lonvick
- Re: Simple authentication of syslog messages for emb... John Kelsey
- Simple authentication of syslog messages for embedde... Alex Brown
- Re: Simple authentication of syslog messages for... Chris Lonvick
