>> It is questionable whether we should "roll our own" crypto...mandate the use >> of SSL or IPsec. Not using existing crypto means you have to get the crypto >> right and then you've got X.509 issues, etc. Time is better spent elsewhere >> - other people have already "solved this", lets stop reinenting the wheel. > Please don't reinvent the crypto-stuff that has already been invented in for > example the SSL and the SSH protocols. Just make sure the standard available > stuff fits in. > Jan I agree there is already significant amount of work completed in the crypto world. It is not necessary to reinvent the wheel. Jim Cupps Network Engineer Sappi Fine Paper North America Telephone (207)854-7065 Fax (207)874-6638
- secured syslog protocol... Balazs Scheidler
- Re: secured syslog protocol... Chris Lonvick
- Re: secured syslog protocol... Jon Knight
- Re: secured syslog protocol... Kurt D. Starsinic
- Re: secured syslog protocol... Darren Reed
- Re: secured syslog protocol... Jan Meijer
- Re: secured syslog protocol... Enrique A. Chaparro
- Re: secured syslog protocol... Chris Lonvick
- Re: secured syslog protocol... Jan Meijer
- Re: secured syslog protocol... Alex Brown
- Re: secured syslog protocol... james . cupps
- Re: secured syslog protocol... Magosanyi Arpad
- Re: secured syslog protocol... Darren Reed
- Re: secured syslog protocol... Magosanyi Arpad
- Re: secured syslog protocol... Jan Meijer
- Re: secured syslog protocol... Darren Reed
- Re: secured syslog protocol... Alex Brown
- Re: secured syslog protocol... Balazs Scheidler
- Re: secured syslog protocol... Tero Kivinen