Re: [Syslog] Missing email? was: Re: -transport-tls-12, section 4.2.3 (fingerprints)

"Rainer Gerhards" <rgerhards@hq.adiscon.com> Fri, 09 May 2008 21:03 UTC

Return-Path: <syslog-bounces@ietf.org>
X-Original-To: syslog-archive@megatron.ietf.org
Delivered-To: ietfarch-syslog-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E6D3F3A6890; Fri, 9 May 2008 14:03:13 -0700 (PDT)
X-Original-To: syslog@core3.amsl.com
Delivered-To: syslog@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 839BE3A6890 for <syslog@core3.amsl.com>; Fri, 9 May 2008 14:03:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id typqipEbVbmH for <syslog@core3.amsl.com>; Fri, 9 May 2008 14:02:59 -0700 (PDT)
Received: from mailin.adiscon.com (hetzner.adiscon.com [85.10.198.18]) by core3.amsl.com (Postfix) with ESMTP id 2A0B63A67EC for <syslog@ietf.org>; Fri, 9 May 2008 14:02:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailin.adiscon.com (Postfix) with ESMTP id 0B6BA7AD770; Fri, 9 May 2008 22:30:48 +0200 (CEST)
Received: from mailin.adiscon.com ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 51ip1GVSaajt; Fri, 9 May 2008 22:30:47 +0200 (CEST)
Received: from grfint2.intern.adiscon.com (p50989a7c.dip0.t-ipconnect.de [80.152.154.124]) by mailin.adiscon.com (Postfix) with ESMTP id B845C7AD5BD; Fri, 9 May 2008 22:30:47 +0200 (CEST)
Content-class: urn:content-classes:message
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Fri, 09 May 2008 22:34:34 +0200
Message-ID: <577465F99B41C842AAFBE9ED71E70ABA308FBF@grfint2.intern.adiscon.com>
In-Reply-To: <Pine.GSO.4.63.0805091103200.10011@sjc-cde-011.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Missing email? was: Re: [Syslog] -transport-tls-12, section 4.2.3 (fingerprints)
Thread-Index: Acix/4Zg5a4SLD5MRB2lJM0eg9CcUQAFE07g
References: <577465F99B41C842AAFBE9ED71E70ABA308FA8@grfint2.intern.adiscon.com> <AC1CFD94F59A264488DC2BEC3E890DE505C94F0F@xmb-sjc-225.amer.cisco.com> <577465F99B41C842AAFBE9ED71E70ABA308FAA@grfint2.intern.adiscon.com> <AC1CFD94F59A264488DC2BEC3E890DE505C95488@xmb-sjc-225.amer.cisco.com> <577465F99B41C842AAFBE9ED71E70ABA308FBD@grfint2.intern.adiscon.com> <Pine.GSO.4.63.0805091103200.10011@sjc-cde-011.cisco.com>
From: Rainer Gerhards <rgerhards@hq.adiscon.com>
To: Chris Lonvick <clonvick@cisco.com>
Cc: syslog@ietf.org
Subject: Re: [Syslog] Missing email? was: Re: -transport-tls-12, section 4.2.3 (fingerprints)
X-BeenThere: syslog@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Issues in Network Event Logging <syslog.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/syslog>, <mailto:syslog-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/syslog>
List-Post: <mailto:syslog@ietf.org>
List-Help: <mailto:syslog-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/syslog>, <mailto:syslog-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: syslog-bounces@ietf.org
Errors-To: syslog-bounces@ietf.org

Hi Chris,

I just checked that archive. The message is scrambled there:

http://www.ietf.org/mail-archive/web/syslog/current/msg01861.html
http://www.ietf.org/mail-archive/web/syslog/current/msg01862.html

The complete one is containend in my blogpost at
http://rgerhards.blogspot.com/2008/05/more-on-syslog-tls-policies-and-ie
tf.html

Rainer 

> -----Original Message-----
> From: Chris Lonvick [mailto:clonvick@cisco.com] 
> Sent: Friday, May 09, 2008 8:07 PM
> To: Rainer Gerhards
> Cc: Joseph Salowey (jsalowey); syslog@ietf.org
> Subject: Missing email? was: Re: [Syslog] -transport-tls-12, 
> section 4.2.3 (fingerprints)
> 
> Hi Rainer,
> 
> I'm also seeing the list behave slowly.  I don't think that I saw any 
> message like that.  Can you check the archive and let us know 
> if it's in 
> there?
> 
> Thanks,
> Chris
> 
> On Fri, 9 May 2008, Rainer Gerhards wrote:
> 
> > Joe and Chris,
> >
> > the mailing list processor seems to be a bit slow these 
> days. I sent a
> > long note this morning telling that I see value in automatically
> > generated self-signed certs. That mail also outlines when and why.
> >
> > Please let me know if you did not receive it.
> >
> > Thanks,
> > Rainer
> >
> >> -----Original Message-----
> >> From: Joseph Salowey (jsalowey) [mailto:jsalowey@cisco.com]
> >> Sent: Friday, May 09, 2008 6:40 PM
> >> To: Rainer Gerhards
> >> Cc: syslog@ietf.org
> >> Subject: RE: -transport-tls-12, section 4.2.3 (fingerprints)
> >>
> >>
> >> <snip>
> >>>> [Joe] I don't know that we need to restrict this to a particular
> >>>> implementation.  I think it would be good to provide a management
> >>>> interface to do the generation.  It seems that it would be an
> >>>> acceptable implementation to auto-generate it as well.
> >>>
> >>> [Rainer] As long as the syslogd is not required to
> >>> auto-generate certs, I am happy enough ;)
> >>>
> >>> However, I wonder why it would be useful to auto-generate certs.
> >>> Probably I am overlooking somehting obvious. But: isn't cert
> >>> auto-generation equal to no authentication? After all, if a
> >>> *self-signed* cert is generated by the remote peer AND we
> >>> accept it, doesn't that essentially mean we accept any peer
> >>> because the peer can put whatever it likes into the cert? I
> >>> do not see why this is any better than having no cert at all...
> >>>
> >> [Joe] When I was thinking of auto-generation I was expecting the
> >> certificate to be persistent and the fingerprint would be 
> available to
> >> be communicated out of band to the verifier.  If you generate a new
> >> cert
> >> each time the process starts and the other side does not know the
> >> fingerprint then what you say is true.
> >>
> >>> Rainer
> >>>
> > _______________________________________________
> > Syslog mailing list
> > Syslog@ietf.org
> > https://www.ietf.org/mailman/listinfo/syslog
> >
> 
_______________________________________________
Syslog mailing list
Syslog@ietf.org
https://www.ietf.org/mailman/listinfo/syslog