Return-Path: <owner-ips@ece.cmu.edu>
X-Sieve: cmu-sieve 2.0
Return-Path: <owner-ips@ece.cmu.edu>
Received: (from majordom@localhost)
	by ece.cmu.edu (8.11.0/8.10.2) id gBJJ62m07173
	for ips-outgoing; Thu, 19 Dec 2002 14:06:02 -0500 (EST)
X-Authentication-Warning: ece.cmu.edu: majordom set sender to owner-ips@ece.cmu.edu using -f
Received: from lion.ninthwonder.com (lion.ninthwonder.com [151.199.66.147])
	by ece.cmu.edu (8.11.0/8.10.2) with ESMTP id gBJJ60W07167
	for <ips@ece.cmu.edu>; Thu, 19 Dec 2002 14:06:00 -0500 (EST)
Received: by lion.ninthwonder.com (Postfix, from userid 1021)
	id 7665F30706; Thu, 19 Dec 2002 14:05:59 -0500 (EST)
Date: Thu, 19 Dec 2002 11:01:49 -0800 (PST)
From: Bill Studenmund <wrstuden@wasabisystems.com>
X-X-Sender:  <wrstuden@candlekeep.home-net.internetconnect.net>
To: Ofer Biran <BIRAN@il.ibm.com>
Cc: <ips@ece.cmu.edu>
Subject: Re: iSCSI: Kerb auth issue 1 - checksum
In-Reply-To: <OFB092C06D.28B87A86-ONC2256C94.0057D0B4@telaviv.ibm.com>
Message-ID: <Pine.NEB.4.33.0212191018370.539-100000@candlekeep.home-net.internetconnect.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-ips@ece.cmu.edu
Precedence: bulk

On Thu, 19 Dec 2002, Ofer Biran wrote:

> According to RFC1510 the server Kerberos implementation should
> maintain a cache of client name/timestamp for a window of the
> the allowable clock skew, this prevents a replay usage of
> the authenticator. Telnet does not bind the connection either,
> just the negotiation result (against m-i-m).

I'm sorry, are you saying we don't need this?

> If IPsec is not used, m-i-m can hijack the connection after
> the login anyway.

The original idea was to have input from the end-to-end IPsec SAs in the
checksum too. This would be to prevent against M-I-M IPsec attacks.
Unfortunately the IPsec APIs don't support this, so we dropped it.

Take care,

Bill

