Re: PKCS#11 URI slot attributes & last call

Nico Williams <nico@cryptonector.com> Wed, 17 December 2014 23:56 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC3B51A006F; Wed, 17 Dec 2014 15:56:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.666
X-Spam-Level:
X-Spam-Status: No, score=-1.666 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qVTL6SsDw1RA; Wed, 17 Dec 2014 15:56:18 -0800 (PST)
Received: from homiemail-a89.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 40BA21A0067; Wed, 17 Dec 2014 15:56:18 -0800 (PST)
Received: from homiemail-a89.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a89.g.dreamhost.com (Postfix) with ESMTP id 1D58331805C; Wed, 17 Dec 2014 15:56:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=8B7HYv2nBjTlXw c6OPYpO0RXiow=; b=TBcnBV9ggWdTUiHOzWTIf2SeAOyn2u+XJr//gqmIddfw6e QuaYT/Ln2sugU1uSc/ww+ugRRBuOoCXSYA+u+aDKg5cdd0ZJa4Mz1sKZFtocS3sv PHtk5insKSTwpmAIRJxRQjs7p3YaICmIg7uAV9ONe0FPiPBxLI0ga4CgxQcxU=
Received: from localhost (108-207-244-174.lightspeed.austtx.sbcglobal.net [108.207.244.174]) (Authenticated sender: nico@cryptonector.com) by homiemail-a89.g.dreamhost.com (Postfix) with ESMTPA id 74B6D318059; Wed, 17 Dec 2014 15:56:17 -0800 (PST)
Date: Wed, 17 Dec 2014 17:56:17 -0600
From: Nico Williams <nico@cryptonector.com>
To: Jan Pechanec <jan.pechanec@oracle.com>
Subject: Re: PKCS#11 URI slot attributes & last call
Message-ID: <20141217235612.GK9443@localhost>
References: <alpine.GSO.2.00.1412161359100.4549@keflavik> <1418771511.2106.7.camel@gnutls.org> <20141216234252.GN3241@localhost> <1418809054.2100.9.camel@gnutls.org> <alpine.GSO.2.00.1412171537500.4549@keflavik>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.GSO.2.00.1412171537500.4549@keflavik>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/8y_WQv7ACHdnOl4u2ul6g1skWDY
Cc: Darren.Moffat@oracle.com, Stef Walter <stef@thewalter.net>, Jaroslav Imrich <jaroslav.imrich@gmail.com>, ietf@ietf.org, saag@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Dec 2014 23:56:19 -0000

On Wed, Dec 17, 2014 at 03:52:50PM -0800, Jan Pechanec wrote:
> On Wed, 17 Dec 2014, Nikos Mavrogiannopoulos wrote:
> >I don't follow how the above require the slots to be known in order to
> >figure where the object is. In gnutls we handle all of these use cases,
> >and we don't need to know the slot at all. First you iterate all slots
> >searching for the object, and then you login and search again. How would
> >knowing the slot would have helped that?
> 
> 	hi Nikos, if I expect a token to be inserted with some key 
> (rather then identifying the key to use) then specifying the slot 
> where such token is to be found seems useful to me.  If I understand 
> it correctly, that's how pam_pkcs11 works.  It has two configuration 
> options for this - slot description and slot ID.

That only works with a PKCS#11 implementation like Solaris' libpkcs11.

In general PKCS#11 slot IDs are unreliable, and that's why Nikos
objects.

> 	I know that the slot ID is cryptoki module specific.  It would 
> have been nice if the specification supported token serial number as 
> it does for tokens.

It needn't be stable even for one module.

> 	the updated text would have to provide information about 
> general unreliability using the slot ID, for example.

Please post proposed new text.  Time is running out.

Nico
--