Le 01/05/2011 06:33, Peter Stuge a écrit :
> Viktor TARASOV wrote:
>> when creating new object with protected usage (using
>> 'pkcs15-init'), the 'auth-id' argument is mandatory.
>> 'Auth-id' argument can have only one possible value
> This I think is the crux, and it always seemed stupid to me tha
Viktor TARASOV wrote:
> when creating new object with protected usage (using
> 'pkcs15-init'), the 'auth-id' argument is mandatory.
> 'Auth-id' argument can have only one possible value
This I think is the crux, and it always seemed stupid to me that I
need to provide an argument which can only ev
Le 29/04/2011 20:49, NdK a écrit :
> On 29/04/2011 15:35, Viktor TARASOV wrote
>> ID '02' will silently go into the authId of a new PKCS#15 object. Nothing
>> more.
> So creating a mismatch between what PKCS#15 knows aout that object and
> what card mandates... And we end up having to look at (pos
On 29/04/2011 15:35, Viktor TARASOV wrote:
>>> From your point of view, where the UPDATE access to 4402 and friends
>>> should be defined ?
>> Since UPDATE refers to an existing object, it belongs to that object.
> 4402 is not an object that can be described by PKCS#15, it's the PKCS#15
> i
Hello,
On Fri, Apr 29, 2011 at 16:30, NdK wrote:
> Il 29/04/2011 14:38, Martin Paljak ha scritto:
>
>> Hello NdK (Diego?)
> Yup. It's me.
I was just trying to figure out if you have a real life name which can
be used to refer you :)
>> A side note: PKCS#15 profiles related parts of OpenSC are q
Le 29/04/2011 14:20, NdK a écrit :
> Il 29/04/2011 13:49, Viktor TARASOV ha scritto
>> Please, precise what standards are you talking about?
> PKCS#15, ISO7816 and every applicable one.
>>From your point of view, where the UPDATE access to 4402 and friends
>> should be defined ?
> Since UPDATE
Il 29/04/2011 14:38, Martin Paljak ha scritto:
> Hello NdK (Diego?)
Yup. It's me.
> A side note: PKCS#15 profiles related parts of OpenSC are quite undocumented
> and difficult to understand/follow (as you probably have experienced yourself)
I know. But since they're there and have to be followe
Hello NdK (Diego?)
A side note: PKCS#15 profiles related parts of OpenSC are quite undocumented
and difficult to understand/follow (as you probably have experienced yourself)
If you feel like improving what you read, as you go on, what about updating
- pkcs15-profile (should it be renamed to p
Il 29/04/2011 13:49, Viktor TARASOV ha scritto:
> Please, precise what standards are you talking about?
PKCS#15, ISO7816 and every applicable one.
> From your point of view, where the UPDATE access to 4402 and friends should
> be defined ?
Since UPDATE refers to an existing object, it belongs to
Il 29/04/2011 12:23, Toni Sjoblom - Aventra ha scritto:
>>> Agree, but not every card always returns all necessary information.
>>> The missing part can be looked for in the card profiles.
>> Uhm... Doesn't standards mandate that, for example, 3F00 must always be
>> readable, 4402 contains auth in
Le 29/04/2011 10:38, NdK a écrit :
> Il 29/04/2011 09:20, Viktor TARASOV ha scritto:
>
We cannot replace $PIN macro with the one that can be modified by
'--auth-id'.
$PIN macro can be used to protect, for ex. the xxDF files itself,
>>> Well, I don't see why it shouldn't work :)
>> W
Hi,
> -Original Message-
> From: opensc-devel-boun...@lists.opensc-project.org
[mailto:opensc-devel-boun...@lists.opensc-project.org] On Behalf Of NdK
>
> Il 29/04/2011 09:20, Viktor TARASOV ha scritto:
>
> >>> We cannot replace $PIN macro with the one that can be modified by
'--auth-
>
Il 29/04/2011 09:20, Viktor TARASOV ha scritto:
>>> We cannot replace $PIN macro with the one that can be modified by
>>> '--auth-id'.
>>> $PIN macro can be used to protect, for ex. the xxDF files itself,
>> Well, I don't see why it shouldn't work :)
> When $PIN translation can change from one in
13 matches
Mail list logo
