Re: [Syslog] syslog/tls policies and use cases
robert.horn@agfa.com Wed, 14 May 2008 18:31 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 352343A6940; Wed, 14 May 2008 11:31:53 -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 00D273A6940; Wed, 14 May 2008 11:31:49 -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 jY9t7un3rAon; Wed, 14 May 2008 11:31:49 -0700 (PDT)
Received: from mornm01-out.agfa.com (mornm01-out.agfa.com [134.54.1.75]) by core3.amsl.com (Postfix) with ESMTP id 971C63A6781; Wed, 14 May 2008 11:31:47 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,487,1204498800"; d="scan'208";a="45529690"
Received: from morswa037.agfa.be (HELO morswa037.be.local) ([10.232.220.21]) by mornm01-out.agfa.com with ESMTP; 14 May 2008 20:30:54 +0200
In-Reply-To: <577465F99B41C842AAFBE9ED71E70ABA308FE7@grfint2.intern.adiscon.com>
To: rgerhards@hq.adiscon.com
MIME-Version: 1.0
Message-ID: <OF7C9111FB.819044A8-ON85257449.00658DFB-85257449.0065B3FA@agfa.com>
From: robert.horn@agfa.com
Date: Wed, 14 May 2008 14:30:52 -0400
Cc: syslog@ietf.org, syslog-bounces@ietf.org
Subject: Re: [Syslog] syslog/tls policies and use cases
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
syslog-bounces@ietf.org wrote on 05/14/2008 12:29:44 PM: > > -----Original Message----- > > From: syslog-bounces@ietf.org [mailto:syslog-bounces@ietf.org] On > > Behalf Of David Harrington > > Sent: Wednesday, May 14, 2008 2:07 PM > > To: Pasi.Eronen@nokia.com; clonvick@cisco.com > > Cc: syslog@ietf.org > > Subject: Re: [Syslog] syslog/tls policies and use cases > > > > Hi, > > > > So I go buy a Linksys or Netgear router or other consumer gear. > > I slip the CD into the drive and run software to install the > > management GUI on my PC. > > That software is used to perform an initial configuration of the > > device, such as enabling DHCP, setting WEP keys, and so on. > > This same software can presumably generate a key and "copy the > > fingerprint" to the device, right? > > Clueless operator needs not be involved. The Internet is secure. > > > > right? > > Mostly ;) What the clueless user still needs to do is > > 1) copy the server's fingerprint to the client > 2) configure the server to accept the client's fingerprint > Another minor correction. The dumb gear sends its certificate to the server, and gets its certificate from the server. (I would suggest by a reasonably secure means, such as https.) You then use the fingerprints to make sure that the right certificates were copied. R Horn > Rainer > > > > David Harrington > > dbharrington@comcast.net > > ietfdbh@comcast.net > > dharrington@huawei.com > > > > > > > > _______________________________________________ > > 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 _______________________________________________ Syslog mailing list Syslog@ietf.org https://www.ietf.org/mailman/listinfo/syslog
- Re: [Syslog] syslog/tls policies and use cases David Harrington
- Re: [Syslog] syslog/tls policies and use cases Rainer Gerhards
- Re: [Syslog] syslog/tls policies and use cases robert.horn
- Re: [Syslog] syslog/tls policies and use cases Rainer Gerhards
- Re: [Syslog] syslog/tls policies and use cases robert.horn
- Re: [Syslog] syslog/tls policies and use cases tom.petch