which I do not want to take.
Tom Petch
___
Syslog mailing list
Syslog@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/syslog
network devices. If you limit yourself
to network operations of network devices, then it appears to be
SSH a significant number
TLS so small as to be invisible
Tom Petch
- Original Message -
From: Anton Okmianski (aokmians) [EMAIL PROTECTED]
To: Chris Lonvick (clonvick) [EMAIL PROTECTED
accept that SSL dominates).
Tom Petch
- Original Message -
From: Rodney Thayer [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, October 25, 2005 11:46 PM
Subject: Re: Why not TLS was Re: [Syslog] Secure substrate - need your input
Tom Petch wrote:
In the context of isms, ie
, not saying that we have at present.
Tom Petch
- Original Message -
From: Rainer Gerhards [EMAIL PROTECTED]
To: Chris Lonvick [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Wednesday, November 30, 2005 2:48 PM
Subject: RE: [Syslog] #5 - character encoding (was: Consensus
I was thinking that PRI is also not optional.
Tom Petch
- Original Message -
From: Rainer Gerhards [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, November 30, 2005 10:06 AM
Subject: RE: [Syslog] #7 field order
I just got private mail if a missing field is denoted
.
My instinct is we should be doing more in this area, in particular having
greater consistency between MSG and PARAM-VALUE, in their transfer syntax and
termination..
Anyone else agree or disagree?
Tom Petch
- Original Message -
From: Chris Lonvick [EMAIL PROTECTED]
To: [EMAIL PROTECTED
I don't think this quite nails it down - see inline
Tom Petch
- Original Message -
From: Chris Lonvick [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday, December 12, 2005 2:38 AM
Subject: [Syslog] Newly revised proposed charter
Sam has asked that we nail down
...
Rainer
-Original Message-
From: Tom Petch [mailto:[EMAIL PROTECTED]
Sent: Saturday, December 17, 2005 4:59 PM
To: Rainer Gerhards
Cc: [EMAIL PROTECTED]; Chris Lonvick
Subject: nailing down characters in syslog-protocol
I would like to see a stricter definition of characters in
syslog
prohibits
-
but allows
--
i
-id-
etc
(but not:-)
Tom Petch
- Original Message -
From: Rainer Gerhards [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, December 21, 2005 6:16 PM
Subject: RE: [Syslog] #7, field order
David, Darren,
even though no responses indicated we actually need
think I am
lost here and that the introduction should be recast in the language of
RFC3164/syslog-protocol (even if it is intending to convey the above).
Tom Petch
___
Syslog mailing list
Syslog@lists.ietf.org
https://www1.ietf.org/mailman/listinfo
Sam
I struggle to think what a security system would look like when the protocol is
purely simplex, apart from a MAC to give integrity with some shared secret
transmitted totally out of band.
Are there any examples of simplex security elsewhere in the IETF?
Tom Petch
- Original Message
- Original Message -
From: Sam Hartman [EMAIL PROTECTED]
To: Tom Petch [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Friday, January 06, 2006 10:27 PM
Subject: Re: [Syslog] Charter comments from IESG Review
Tom == Tom Petch [EMAIL PROTECTED] writes:
Tom Sam I struggle to think
The goal of this working group is to identify the security problems, perform
a threat analysis and document a solution to the perceived threats,
without committing us to either a -sign or a secure transport approach (and yes,
we did start the transport wars, some time ago, with SSH v TLS:-(
Tom
.
The only realistic alternative would be to incorporate signature blocks in the
style of syslog-sign in the structured data of the message being authenticated.
Tom Petch
___
Syslog mailing list
Syslog@lists.ietf.org
https://www1.ietf.org/mailman/listinfo
the meaning of
previous or later coded characters, it is not possible to determine where one
'symbol' ends. So truncation at a UTF-8 boundary could subtlety change the
meaning of a message, even breach security. Not something we can guard against
but should mention.
Tom Petch
- Original Message
- Original Message -
From: Darren Reed [EMAIL PROTECTED]
To: Tom Petch [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday, January 16, 2006 10:51 PM
Subject: Re: [Syslog] Sec 6.1: Truncation
[ Charset ISO-8859-1 unsupported, converting... ]
Truncation of UTF-8 is actually slightly
- Original Message -
From: Anton Okmianski (aokmians) [EMAIL PROTECTED]
To: Sam Hartman [EMAIL PROTECTED]
Cc: Chris Lonvick (clonvick) [EMAIL PROTECTED]; Tom Petch
[EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Tuesday, January 17, 2006 10:54 PM
Subject: RE: [Syslog] Re: Threat model
- Original Message -
From: Rainer Gerhards [EMAIL PROTECTED]
To: Tom Petch [EMAIL PROTECTED]; Darren Reed
[EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, January 18, 2006 9:32 AM
Subject: RE: [Syslog] Sec 6.1: Truncation
Tom,
I agree there are some issues with truncation
.
Tom Petch
- Original Message -
From: Anton Okmianski (aokmians) [EMAIL PROTECTED]
To: Darren Reed [EMAIL PROTECTED]; Tom Petch
[EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Friday, January 20, 2006 4:39 PM
Subject: RE: [Syslog] Sec 6.1: Truncation
I think the suggestion from me and Tom
, will not happen.
Tom Petch
snip
___
Syslog mailing list
Syslog@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/syslog
this is resolved.
Tom Petch
- Original Message -
From: Glenn Mansfield Keeni [EMAIL PROTECTED]
To: Tom Petch [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday, January 26, 2006 6:43 AM
Subject: Re: [Syslog] draft-ietf-syslog-device-mib-07.txt
Tom,
Getting there; recall that my
it.
Tom Petch
- Original Message -
From: Chris Lonvick [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, February 07, 2006 3:09 PM
Subject: [Syslog] Coming to consensus on syslog threats
Hi,
In reviewing the messages around the threats to the syslog protocol, it
appears
has failed.
Tom Petch
- Original Message -
From: David B Harrington [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, May 09, 2006 4:26 PM
Subject: [Syslog] draft-ietf-syslog-transport-tls-01.txt
Hi,
A new revision of the syslog/TLS draft is available.
http://www.ietf.org/internet
on TLS
and then we would not be having this discussion :-)
But, in all seriousness, changing from TLS to anything is a charter change that
I think needs the approval of the IESG, and should require commitment, similar
to that given at the turn of the year, to produce conformant products.
Tom Petch
inline
- Original Message -
From: Anton Okmianski (aokmians) [EMAIL PROTECTED]
To: Tom Petch [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Tuesday, June 20, 2006 8:18 PM
Subject: RE: [Syslog] delineated datagrams
Tom:
I think these are valid concerns. They span different layers:
1. If we
as embedded in the charter (as well as, more obscurely,
in the discussions that led up to the charter change).
Tom Petch
- Original Message -
From: Rainer Gerhards [EMAIL PROTECTED]
To: Tom Petch [EMAIL PROTECTED]; David Harrington
[EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Thursday, June 22
26 matches
Mail list logo
