IETF Logo Mail Archive

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

Chris Lonvick <clonvick@cisco.com> Fri, 09 May 2008 18:08 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 543BF28C170; Fri, 9 May 2008 11:08:25 -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 5DE2528C125 for <syslog@core3.amsl.com>; Fri, 9 May 2008 11:08:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.524
X-Spam-Level:
X-Spam-Status: No, score=-6.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 281G8QzmIFOK for <syslog@core3.amsl.com>; Fri, 9 May 2008 11:08:18 -0700 (PDT)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by core3.amsl.com (Postfix) with ESMTP id BD3A03A683D for <syslog@ietf.org>; Fri, 9 May 2008 11:08:14 -0700 (PDT)
Received: from sj-dkim-1.cisco.com ([171.71.179.21]) by sj-iport-6.cisco.com with ESMTP; 09 May 2008 11:07:17 -0700
Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id m49I7He4016200; Fri, 9 May 2008 11:07:17 -0700
Received: from sjc-cde-011.cisco.com (sjc-cde-011.cisco.com [171.69.20.39]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m49I7Hut000031; Fri, 9 May 2008 18:07:17 GMT
Date: Fri, 09 May 2008 11:07:17 -0700
From: Chris Lonvick <clonvick@cisco.com>
To: Rainer Gerhards <rgerhards@hq.adiscon.com>
In-Reply-To: <577465F99B41C842AAFBE9ED71E70ABA308FBD@grfint2.intern.adiscon.com>
Message-ID: <Pine.GSO.4.63.0805091103200.10011@sjc-cde-011.cisco.com>
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>
MIME-Version: 1.0
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2169; t=1210356437; x=1211220437; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=clonvick@cisco.com; z=From:=20Chris=20Lonvick=20<clonvick@cisco.com> |Subject:=20Missing=20email?=20was=3A=20Re=3A=20[Syslog]=20 -transport-tls-12,=20section=204.2.3=0A=20(fingerprints) |Sender:=20; bh=oOkp5x0db2HExj4il9AbVsaOPG8VuLTkuoB0xp9R2kM=; b=tXh79h7bTrH+h3MhM1wUhqXutW+pv/Y6NCHQK6JOSO+na3v3lnBcMRK3Uq ATJZbkFXEZ1E3PEi48JHjVQqu06/1GgORLMY2nWLB36MC/1jRVdmSxHFmUji +3MLv8NzL6NAOrlVsYMG+q2iMzSQY/WcDRh27tBO9NbjGeB9noR0I=;
Authentication-Results: sj-dkim-1; header.From=clonvick@cisco.com; dkim=pass ( sig from cisco.com/sjdkim1004 verified; );
Cc: syslog@ietf.org
Subject: [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 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

v2.23.0 | Report a Bug | By Email