Re: slot attributes & last call

Darren J Moffat <Darren.Moffat@Oracle.COM> Thu, 18 December 2014 11:22 UTC

Return-Path: <Darren.Moffat@Oracle.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 733BE1A6F2E; Thu, 18 Dec 2014 03:22:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 EtmiRik6cUiS; Thu, 18 Dec 2014 03:22:19 -0800 (PST)
Received: from aserp1040.oracle.com (aserp1040.oracle.com [141.146.126.69]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 23C4A1A07BE; Thu, 18 Dec 2014 03:22:19 -0800 (PST)
Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id sBIBMDqo021501 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 18 Dec 2014 11:22:13 GMT
Received: from aserz7021.oracle.com (aserz7021.oracle.com [141.146.126.230]) by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id sBIBMC1w024115 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 18 Dec 2014 11:22:12 GMT
Received: from abhmp0009.oracle.com (abhmp0009.oracle.com [141.146.116.15]) by aserz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id sBIBMCTH024102; Thu, 18 Dec 2014 11:22:12 GMT
Received: from [10.163.198.80] (/10.163.198.80) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 18 Dec 2014 03:22:11 -0800
Message-ID: <5492B8E1.6010709@Oracle.COM>
Date: Thu, 18 Dec 2014 11:22:09 +0000
From: Darren J Moffat <Darren.Moffat@Oracle.COM>
Organization: Oracle Solaris Security
User-Agent: Mozilla/5.0 (X11; SunOS i86pc; rv:17.0) Gecko/20140924 Thunderbird/17.0.11
MIME-Version: 1.0
To: Jan Pechanec <jan.pechanec@Oracle.COM>
Subject: Re: slot attributes & last call
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>
In-Reply-To: <alpine.GSO.2.00.1412171614240.4549@keflavik>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Source-IP: acsinet21.oracle.com [141.146.126.237]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/NsRTtb1aWbvhH0EzZkWoycnpgFc
X-Mailman-Approved-At: Thu, 18 Dec 2014 08:23:39 -0800
Cc: Stef Walter <stef@thewalter.net>, Jaroslav Imrich <jaroslav.imrich@gmail.com>, ietf@ietf.org, saag@ietf.org, Nikos Mavrogiannopoulos <n.mavrogiannopoulos@gmail.com>
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: Thu, 18 Dec 2014 11:22:20 -0000


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.

-- 
Darren J Moffat