Re: slot attributes & last call

Nikos Mavrogiannopoulos <nmav@gnutls.org> Fri, 19 December 2014 06:52 UTC

Return-Path: <n.mavrogiannopoulos@gmail.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 4F1C21A914B; Thu, 18 Dec 2014 22:52:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 s_VVbelnTk9v; Thu, 18 Dec 2014 22:52:17 -0800 (PST)
Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AB141A9132; Thu, 18 Dec 2014 22:52:17 -0800 (PST)
Received: by mail-wi0-f172.google.com with SMTP id n3so900634wiv.5; Thu, 18 Dec 2014 22:52:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:subject:from:to:cc:date:in-reply-to:references :content-type:mime-version:content-transfer-encoding; bh=a7RJlp5jLyZT7/go9Acawv5BL1uS9ChmCfUt68nKdzk=; b=QAV2sp6ywyZVqdO/NK8zEbkGgZg3LUgNoX4coRu3vZw5yMg47m2I229HlEdHh4ZJ2O Fz54nFdIG5Yrl7ahITNt4DgZxc42jfENC5Lgb1NpYXpE4v9naQHY3eqNQauKPjreiLM/ CJPEqDOdnPdLLgKWpB/dWMbdSL60gJDGTV7e59Fc5gdFFS4vleanDUyoD5wZLaliILl5 mXEAkE/wsu5YHjUDtmzpVpP9+d9+Hnmt66eqspurbDe9lUsZIkTxmbYzhMZ5RRwvkUa7 1+k9O1vGjyb59NttCOM4Sa29iZqe+tcFkDVx2zOqxVUM32Se7jV1Fqyq/iU1Zn1YYmRx Lszw==
X-Received: by 10.194.6.164 with SMTP id c4mr11008379wja.77.1418971936260; Thu, 18 Dec 2014 22:52:16 -0800 (PST)
Received: from aspire.lan (178.128.236.150.dsl.dyn.forthnet.gr. [178.128.236.150]) by mx.google.com with ESMTPSA id ud1sm11589724wjc.7.2014.12.18.22.52.13 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 18 Dec 2014 22:52:14 -0800 (PST)
Sender: Nikos Mavrogiannopoulos <n.mavrogiannopoulos@gmail.com>
Message-ID: <1418971932.28712.2.camel@gnutls.org>
Subject: Re: slot attributes & last call
From: Nikos Mavrogiannopoulos <nmav@gnutls.org>
To: Darren J Moffat <Darren.Moffat@Oracle.COM>
Date: Fri, 19 Dec 2014 08:52:12 +0200
In-Reply-To: <5492B8E1.6010709@Oracle.COM>
References: <alpine.GSO.2.00.1412161359100.4549@keflavik> <CAB6OCMvGxT99cGGBSBbz=XU2+F1xRzBa97z6dY-qPSJk1GWXyQ@mail.gmail.com> <20141217230150.GB9443@localhost> <CAB6OCMvkPSfNYqftAgbcN5KrG7kxb5ooico205O6EffcsU8SwQ@mail.gmail.com> <20141218000736.GL9443@localhost> <alpine.GSO.2.00.1412171614240.4549@keflavik> <5492B8E1.6010709@Oracle.COM>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.12.8 (3.12.8-1.fc21)
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/R5k6a9nr9g2GFwZaKD6i4QtD32Y
Cc: Stef Walter <stef@thewalter.net>, Jaroslav Imrich <jaroslav.imrich@gmail.com>, Nikos Mavrogiannopoulos <n.mavrogiannopoulos@gmail.com>, saag@ietf.org, Jan Pechanec <jan.pechanec@Oracle.COM>, ietf@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: Fri, 19 Dec 2014 06:52:19 -0000

On Thu, 2014-12-18 at 11:22 +0000, Darren J Moffat wrote:
> 
> On 12/18/14 00:15, Jan Pechanec wrote:
> > On Wed, 17 Dec 2014, Nico Williams wrote:
> >
> >>> removable token and you cannot use slot-description, slot-manufacturer and
> >>> neither of token attributes? So the only option left is: pkcs11:slot-id=2
> >>> ???
> >>
> >> I think so.  This is really for Jan to answer.  Maybe the Solaris
> >> libpkcs11 should just ensure a meaningful (stable and distinct) slot
> >> label.  If that could be done then slot-id could be excluded here.
> >>
> >> Jan?
> >
> > 	for example, metaslot on Solaris is always 0 so slot-id=0
> > would be reliable there to use to access the soft token.  Jan.
> 
> It is the zeroth slot in the list of slots not a slotid with a value of 
> 0 - the distinction is subtle.
> I don't think we should have slot-id, it isn't stable and I know that 
> some vendors use random values.

Jan,
 Given that this was the main argument for adding slot-id, is there any
other reason for adding it? Aren't the description and manufacturer
sufficient for the applications which want to restrict to a specific
slot?

regards,
Nikos