IETF Logo Mail Archive

Re: PKCS#11 URI slot attributes & last call

Jan Pechanec <jan.pechanec@oracle.com> Thu, 18 December 2014 00:31 UTC

Return-Path: <jan.pechanec@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 9FCF31A0092; Wed, 17 Dec 2014 16:31:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 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, UNPARSEABLE_RELAY=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 YOfA3wLWhYlf; Wed, 17 Dec 2014 16:31:25 -0800 (PST)
Received: from userp1040.oracle.com (userp1040.oracle.com [156.151.31.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A3F91A007A; Wed, 17 Dec 2014 16:31:25 -0800 (PST)
Received: from ucsinet21.oracle.com (ucsinet21.oracle.com [156.151.31.93]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id sBI0VHkZ016291 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 18 Dec 2014 00:31:18 GMT
Received: from userz7022.oracle.com (userz7022.oracle.com [156.151.31.86]) by ucsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id sBI0VGGC001650 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 18 Dec 2014 00:31:17 GMT
Received: from abhmp0020.oracle.com (abhmp0020.oracle.com [141.146.116.26]) by userz7022.oracle.com (8.14.5+Sun/8.14.4) with ESMTP id sBI0VFc1021848; Thu, 18 Dec 2014 00:31:16 GMT
Received: from keflavik.us.oracle.com (/10.132.148.214) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 17 Dec 2014 16:31:15 -0800
Date: Wed, 17 Dec 2014 16:31:13 -0800
From: Jan Pechanec <jan.pechanec@oracle.com>
X-X-Sender: jpechane@keflavik
To: Jaroslav Imrich <jaroslav.imrich@gmail.com>
Subject: Re: PKCS#11 URI slot attributes & last call
In-Reply-To: <CAB6OCMsAdTarz5XBHgTnU=v9qweS5B6mk-tb7Gbf7kwkDFBDMg@mail.gmail.com>
Message-ID: <alpine.GSO.2.00.1412171627370.4549@keflavik>
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> <CAB6OCMsAdTarz5XBHgTnU=v9qweS5B6mk-tb7Gbf7kwkDFBDMg@mail.gmail.com>
User-Agent: Alpine 2.00 (GSO 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Source-IP: ucsinet21.oracle.com [156.151.31.93]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/u6W6d3Q84N4vksUE51Abfm5_NZk
X-Mailman-Approved-At: Thu, 18 Dec 2014 08:24:56 -0800
Cc: Darren J Moffat <Darren.Moffat@oracle.com>, Stef Walter <stef@thewalter.net>, 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 00:31:27 -0000

On Thu, 18 Dec 2014, Jaroslav Imrich 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.
>
>And there is no other URI that could identify that slot without the slot-id
>attribute? i.e. pkcs11:slot-description=metaslot

	hi Jaroslav, you could use the slot description to find the 
slot but that's not the case.  The thing is that you can use slot 0 
reliably there so slot-id would make sense in that context.  We have 
attributes that can be reasonable used only in certain scenarios and 
not others, like "pin-value".  Jan.

-- 
Jan Pechanec <jan.pechanec@oracle.com>

v2.23.0 | Report a Bug | By Email