On 4/7/2011 12:10 PM, Viktor TARASOV wrote:
> Hello Douglas,
>
> Le 05/04/2011 15:36, Douglas E. Engert a écrit :
>> I would the serialized, so some cards do not have to follow the GUID format.
>> This could eliminate
>> the need to have a hash function for OpenSSL.
>
> I've committed the common
Hello Douglas,
Le 05/04/2011 15:36, Douglas E. Engert a écrit :
I would the serialized, so some cards do not have to follow the GUID format.
This could eliminate
the need to have a hash function for OpenSSL.
I've committed the common routines to get the 'classic' serialized form of GUID.
In
On 4/5/2011 2:55 AM, Viktor TARASOV wrote:
> Le 04/04/2011 20:35, Douglas E. Engert a écrit :
>> Yes. The PIV-Compatible defines a GUID in the CHUID. These would be
>> non-US-gov
>> issued cards. The test cards I generate used the Solaris 10 /usr/bin/makeuuid
>> to generate a GUID. The FASCN the
Le lundi 28 mars 2011 à 14:06 +0200, Viktor TARASOV a écrit :
> I'm get used to this GUID format in the Windows world.
> and so it seemed to me quite natural to use it for the Windows
> containers.
>
> > If other cards have longer serial numbers or IDs for the certs,
> > that could still be an iss
Le 04/04/2011 20:35, Douglas E. Engert a écrit :
> Yes. The PIV-Compatible defines a GUID in the CHUID. These would be non-US-gov
> issued cards. The test cards I generate used the Solaris 10 /usr/bin/makeuuid
> to generate a GUID. The FASCN then starts with .
>
> But the real US-gov issued car
On 4/4/2011 11:58 AM, Viktor TARASOV wrote:
> Le 04/04/2011 17:39, Douglas E. Engert a écrit :
>> On 4/4/2011 4:09 AM, Viktor TARASOV wrote:
>>> Le 30/03/2011 18:38, Viktor TARASOV a écrit :
What would you say if we accept the 'classic' GUID form as a default one,
and give the possibili
Le 04/04/2011 17:39, Douglas E. Engert a écrit :
> On 4/4/2011 4:09 AM, Viktor TARASOV wrote:
>> Le 30/03/2011 18:38, Viktor TARASOV a écrit :
>>> What would you say if we accept the 'classic' GUID form as a default one,
>>> and give the possibility to define its own format to the pkcs15 card drive
On 4/4/2011 4:09 AM, Viktor TARASOV wrote:
> Le 30/03/2011 18:38, Viktor TARASOV a écrit :
>> What would you say if we accept the 'classic' GUID form as a default one,
>> and give the possibility to define its own format to the pkcs15 card driver ?
>> A new sc_pkcs15_operations callback will be u
Le 30/03/2011 18:38, Viktor TARASOV a écrit :
> What would you say if we accept the 'classic' GUID form as a default one,
> and give the possibility to define its own format to the pkcs15 card driver ?
> A new sc_pkcs15_operations callback will be used:
> http://www.opensc-project.org/opensc/browse
Le 01/04/2011 17:23, Douglas E. Engert a écrit :
>
> On 4/1/2011 2:08 AM, Viktor TARASOV wrote:
>> Le 31/03/2011 21:28, Martin Paljak a écrit :
>>> Hello,
>>>
>>> On Mar 31, 2011, at 20:36 , Viktor TARASOV wrote:
Cardmod is promoted by Microsoft and is used (afaik) exclusively by
Microso
On 4/1/2011 2:08 AM, Viktor TARASOV wrote:
> Le 31/03/2011 21:28, Martin Paljak a écrit :
>> Hello,
>>
>> On Mar 31, 2011, at 20:36 , Viktor TARASOV wrote:
>>> Cardmod is promoted by Microsoft and is used (afaik) exclusively by
>>> Microsoft .
>> For the sake of terminology - the concept is call
Le 31/03/2011 21:28, Martin Paljak a écrit :
> Hello,
>
> On Mar 31, 2011, at 20:36 , Viktor TARASOV wrote:
>> Cardmod is promoted by Microsoft and is used (afaik) exclusively by
>> Microsoft .
> For the sake of terminology - the concept is called a mini(-)driver and most
> Miicrosoft originating
Hello,
On Mar 31, 2011, at 20:36 , Viktor TARASOV wrote:
> Cardmod is promoted by Microsoft and is used (afaik) exclusively by Microsoft
> .
For the sake of terminology - the concept is called a mini(-)driver and most
Miicrosoft originating documentation talks about "a minidriver", not a cardmod
Le lundi 28 mars 2011 à 14:06 +0200, Viktor TARASOV a écrit :
> I'm get used to this GUID format in the Windows world.
> and so it seemed to me quite natural to use it for the Windows
> containers.
+1.
--
Jean-Michel Pouré - Gooze - http://www.gooze.eu
___
Le 30/03/2011 20:16, Douglas E. Engert a écrit :
> On 3/30/2011 11:38 AM, Viktor TARASOV wrote:
>> Le 28/03/2011 18:29, Douglas E. Engert a écrit :
>>> On 3/28/2011 7:06 AM, Viktor TARASOV wrote:
Le 25/03/2011 20:51, Douglas E. Engert a écrit :
>> ...
> Do we really need the GUID format? "
On 3/30/2011 11:38 AM, Viktor TARASOV wrote:
> Le 28/03/2011 18:29, Douglas E. Engert a écrit :
>> On 3/28/2011 7:06 AM, Viktor TARASOV wrote:
>>> Le 25/03/2011 20:51, Douglas E. Engert a écrit :
> ...
Do we really need the GUID format? "{" and "}" and 4 "-" take up 6
characters that co
Le 28/03/2011 18:29, Douglas E. Engert a écrit :
> On 3/28/2011 7:06 AM, Viktor TARASOV wrote:
>> Le 25/03/2011 20:51, Douglas E. Engert a écrit :
...
>>> Do we really need the GUID format? "{" and "}" and 4 "-" take up 6
>>> characters that could be used for more serial number and ID.
>> Not reall
On 3/28/2011 7:06 AM, Viktor TARASOV wrote:
> Le 25/03/2011 20:51, Douglas E. Engert a écrit :
>>
>>
>> On 3/25/2011 1:25 PM, Viktor TARASOV wrote:
>>> Le 25/03/2011 17:23, Douglas E. Engert a écrit :
Testing opensc-cardmod.dll r5270 on Vista, login to AD works with
two different cards
Le 25/03/2011 20:51, Douglas E. Engert a écrit :
>
>
> On 3/25/2011 1:25 PM, Viktor TARASOV wrote:
>> Le 25/03/2011 17:23, Douglas E. Engert a écrit :
>>> Testing opensc-cardmod.dll r5270 on Vista, login to AD works with
>>> two different cards to the same account. But certutil has a problem.
>>> I
On 3/25/2011 1:25 PM, Viktor TARASOV wrote:
> Le 25/03/2011 17:23, Douglas E. Engert a écrit :
>> Testing opensc-cardmod.dll r5270 on Vista, login to AD works with
>> two different cards to the same account. But certutil has a problem.
>> I see from:
>> certutil -store -user My
>>
>> Key Cont
Le 25/03/2011 17:23, Douglas E. Engert a écrit :
> Testing opensc-cardmod.dll r5270 on Vista, login to AD works with
> two different cards to the same account. But certutil has a problem.
> I see from:
> certutil -store -user My
>
>Key Container = {0100----}
>
> So i
Testing opensc-cardmod.dll r5270 on Vista, login to AD works with
two different cards to the same account. But certutil has a problem.
I see from:
certutil -store -user My
Key Container = {0100----}
So it looks like the serial number of the card is not being used,
On 3/14/2011 2:02 PM, Viktor TARASOV wrote:
> On 14.03.2011 13:56, Douglas E. Engert wrote:
>>
>> On 3/12/2011 1:40 PM, Viktor TARASOV wrote:
>>> Hi,
>>>
>>> For container's GUID I propose to adopt the classic serialized form
>>> (ex.{3F2504E0-4F89-11D3-9A0C-0305E82C3301})
>>> used by Windows co
On 14.03.2011 13:56, Douglas E. Engert wrote:
>
> On 3/12/2011 1:40 PM, Viktor TARASOV wrote:
>> Hi,
>>
>> For container's GUID I propose to adopt the classic serialized form
>> (ex.{3F2504E0-4F89-11D3-9A0C-0305E82C3301})
>> used by Windows containers.
>>
>> In this patch there is also little simp
On 14.03.2011 14:00, Douglas E. Engert wrote:
On 3/13/2011 1:03 PM, Viktor TARASOV wrote:
On 12.03.2011 20:40, Viktor TARASOV wrote:
Hi,
For container's GUID I propose to adopt the classic serialized form
(ex.{3F2504E0-4F89-11D3-9A0C-0305E82C3301})
used by Windows containers.
In this patch
On 3/13/2011 1:03 PM, Viktor TARASOV wrote:
> On 12.03.2011 20:40, Viktor TARASOV wrote:
>> Hi,
>>
>> For container's GUID I propose to adopt the classic serialized form
>> (ex.{3F2504E0-4F89-11D3-9A0C-0305E82C3301})
>> used by Windows containers.
>>
>> In this patch there is also little simplif
On 3/12/2011 1:40 PM, Viktor TARASOV wrote:
> Hi,
>
> For container's GUID I propose to adopt the classic serialized form
> (ex.{3F2504E0-4F89-11D3-9A0C-0305E82C3301})
> used by Windows containers.
>
> In this patch there is also little simplification of the key research, and
> some minor remar
On 12.03.2011 20:40, Viktor TARASOV wrote:
Hi,
For container's GUID I propose to adopt the classic serialized form
(ex.{3F2504E0-4F89-11D3-9A0C-0305E82C3301})
used by Windows containers.
In this patch there is also little simplification of the key research, and some
minor remarks.
Another i
Hi,
For container's GUID I propose to adopt the classic serialized form
(ex.{3F2504E0-4F89-11D3-9A0C-0305E82C3301})
used by Windows containers.
In this patch there is also little simplification of the key research, and some
minor remarks.
Kind wishes,
Viktor.
--
Viktor Tarasov
Index: src
29 matches
Mail list logo
