IETF Logo Mail Archive

Re: [Syslog] Some revised text for syslog TLS

"Rainer Gerhards" <rgerhards@hq.adiscon.com> Mon, 26 May 2008 09:35 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 36D073A68ED; Mon, 26 May 2008 02:35:02 -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 4CA9D3A68ED for <syslog@core3.amsl.com>; Mon, 26 May 2008 02:35:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.444
X-Spam-Level:
X-Spam-Status: No, score=-2.444 tagged_above=-999 required=5 tests=[AWL=0.155, 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 oASjaqj6pCaS for <syslog@core3.amsl.com>; Mon, 26 May 2008 02:35:00 -0700 (PDT)
Received: from mailin.adiscon.com (hetzner.adiscon.com [85.10.198.18]) by core3.amsl.com (Postfix) with ESMTP id 3DD683A68C8 for <syslog@ietf.org>; Mon, 26 May 2008 02:34:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailin.adiscon.com (Postfix) with ESMTP id 672537AD8BB; Mon, 26 May 2008 11:34:50 +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 7sEAxLlRYW+z; Mon, 26 May 2008 11:34:50 +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 2BADB7AD6BB; Mon, 26 May 2008 11:34:50 +0200 (CEST)
MIME-Version: 1.0
x-cr-puzzleid: {CA17C618-493A-4698-9046-CC4530F9BD65}
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
x-cr-hashedpuzzle: BMxa BWud CPMA DyRr EIfm E/+s GNnu Hoia IbFm KWgY L39P MghS PPz5 Qp01 T6WN W7i+; 2; agBzAGEAbABvAHcAZQB5AEAAYwBpAHMAYwBvAC4AYwBvAG0AOwBzAHkAcwBsAG8AZwBAAGkAZQB0AGYALgBvAHIAZwA=; Sosha1_v1; 7; {CA17C618-493A-4698-9046-CC4530F9BD65}; cgBnAGUAcgBoAGEAcgBkAHMAQABoAHEALgBhAGQAaQBzAGMAbwBuAC4AYwBvAG0A; Mon, 26 May 2008 09:34:53 GMT; UgBFADoAIABbAFMAeQBzAGwAbwBnAF0AIABTAG8AbQBlACAAcgBlAHYAaQBzAGUAZAAgAHQAZQB4AHQAIABmAG8AcgAgAHMAeQBzAGwAbwBnACAAVABMAFMA
Date: Mon, 26 May 2008 11:34:53 +0200
Message-ID: <577465F99B41C842AAFBE9ED71E70ABA30909A@grfint2.intern.adiscon.com>
In-Reply-To: <AC1CFD94F59A264488DC2BEC3E890DE505DFD90C@xmb-sjc-225.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Syslog] Some revised text for syslog TLS
Thread-Index: Aci9BIbqo/w6J1eNRCCueVc7JY86VgCDuzKQ
References: <AC1CFD94F59A264488DC2BEC3E890DE505DFD90C@xmb-sjc-225.amer.cisco.com>
From: Rainer Gerhards <rgerhards@hq.adiscon.com>
To: "Joseph Salowey (jsalowey)" <jsalowey@cisco.com>, syslog@ietf.org
Subject: Re: [Syslog] Some revised text for syslog TLS
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

One more comment while implementing it:

> 4.2.2  Certificate Fingerprints
> 
> Both client and server implementations MUST make the certificate
> fingerprint for their certificates available through a management
> interface.
> 
> The mechanism to generate a fingerprint is to take the hash of the
> certificate using a cryptographically strong algorithm and convert the
> result into colon separated, hexadecimal bytes, each represented by 2
> uppercase ASCII characters.  When a fingerprint value is displayed or
> configured the fingerprint is prepended with an ASCII label
identifying
> the hash function followed by a colon.  Implementations MUST support
> SHA-1 as the hash algorithm and use the ASCII label "SHA1" to identify
> the SHA-1 algorithm.  The length of a SHA-1 hash is 20 bytes and the
> length of the corresponding fingerprint string is 64 characters. An
> example certificate fingerprint is:
> 
> 	SHA1:E1:2D:53:2B:7C:6B:8A:29:A2:76:C8:64:36:0B:08:4B:7A:F1:9E:9D
> 
> 
> During validation the hash is extracted from the fingerprint and
> compared against the hash calculated over the received certificate.

The text above makes it really easy to implement, as there is no longer
a doubt about what the actual format should look like. Also, adding the
hash algo as first field of the fingerprint cleans up a lot of code.

Rainer
_______________________________________________
Syslog mailing list
Syslog@ietf.org
https://www.ietf.org/mailman/listinfo/syslog

v2.23.0 | Report a Bug | By Email