IETF Logo Mail Archive

[Syslog] why fingerprints? (Re: I-D Action:draft-ietf-syslog-transport-tls-12.txt)

Martin Schütte <lists@mschuette.name> Sat, 10 May 2008 18:25 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 E0DA73A6970; Sat, 10 May 2008 11:25:09 -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 2C5AB3A6970 for <syslog@core3.amsl.com>; Sat, 10 May 2008 11:25:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.949
X-Spam-Level:
X-Spam-Status: No, score=-1.949 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, MIME_8BIT_HEADER=0.3]
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 IQKvTL0KKgtv for <syslog@core3.amsl.com>; Sat, 10 May 2008 11:25:07 -0700 (PDT)
Received: from mail.asta.uni-potsdam.de (mail.asta.uni-potsdam.de [141.89.58.198]) by core3.amsl.com (Postfix) with ESMTP id 6826F3A68D4 for <syslog@ietf.org>; Sat, 10 May 2008 11:25:07 -0700 (PDT)
Received: from localhost (mail.asta.uni-potsdam.de [141.89.58.198]) by mail.asta.uni-potsdam.de (Postfix) with ESMTP id 55A497D89F for <syslog@ietf.org>; Sat, 10 May 2008 17:33:33 +0200 (CEST)
X-Virus-Scanned: on mail at asta.uni-potsdam.de
Received: from mail.asta.uni-potsdam.de ([141.89.58.198]) by localhost (mail.asta.uni-potsdam.de [141.89.58.198]) (amavisd-new, port 10024) with ESMTP id X+7yR7RVpYrT for <syslog@ietf.org>; Sat, 10 May 2008 17:33:21 +0200 (CEST)
Received: from [192.168.178.21] (BAEbf33.bae.pppool.de [77.132.191.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "Martin Schuette", Issuer "AStA-CA" (verified OK)) by mail.asta.uni-potsdam.de (Postfix) with ESMTP id B110079341 for <syslog@ietf.org>; Sat, 10 May 2008 17:33:20 +0200 (CEST)
Message-ID: <4825DC61.9000000@mschuette.name>
Date: Sat, 10 May 2008 17:33:21 +0000
From: Martin Schütte <lists@mschuette.name>
User-Agent: Thunderbird 2.0.0.12 (X11/20080427)
MIME-Version: 1.0
To: syslog@ietf.org
References: <20080507150001.D3CB428C65B@core3.amsl.com>
In-Reply-To: <20080507150001.D3CB428C65B@core3.amsl.com>
Subject: [Syslog] why fingerprints? (Re: I-D Action:draft-ietf-syslog-transport-tls-12.txt)
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

>    o  Certificate fingerprints: For each transport receiver, the client
>       is configured with a fingerprint of the server's certificate
>       (which can be self-signed).  This option MUST be supported.

Am I the only one who finds this whole fingerprint option completely
unnecessary?
Is this practice actually used somewhere? I have not heard about this
before and get the impression it is only a bad substitute for copying 
the peer's certificate.

-- 
Martin

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

v2.23.0 | Report a Bug | By Email