Patch applied in revision 121
http://www.opensc-project.org/sca/changeset/121
Please check it is still correct for you.
2009/6/4 Thomas "fake" Jakobi :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> hi,
>
> i'm not too sure wether mailman will be able to attach this message to
> the thread
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
i'm not too sure wether mailman will be able to attach this message to
the thread i am referring to, so i'll add a link to it:
http://www.opensc-project.org/pipermail/opensc-devel/2009-April/012052.html
i just wanted to add a thumbs up for thi
On Mar 22, 2009, at 11:36 AM, Henry B. Hotz wrote:
>
> On Mar 21, 2009, at 2:26 AM, Martin Paljak wrote:
>
>> On 21.03.2009, at 2:34, Henry B. Hotz wrote:
>>
>>
>>> I'm willing to do some debugging, if someone will tell me what to
>>> look at. Maybe where to put syslog calls in a custom build?
>
Hello Hugh,
> I have attached a patch to add support for different size keys in the
> tokend,
> which should work for RSA 2048-bit keys. I removed the hardcoded 1024
> values and
> added an attribute coder for key attributes, which examines the key
> object
> to determine the key size. I've test
On Apr 13, 2009, at 1:50 AM, Martin Paljak wrote:
On 13.04.2009, at 2:27, Hugh Cole-Baker wrote:
I had the same error, but got around it by choosing the Deployment
(instead
of Development) build config. in XCode. I think the build process
may not be
building the debug version of tokend.fram
On 13.04.2009, at 2:27, Hugh Cole-Baker wrote:
> I had the same error, but got around it by choosing the Deployment
> (instead
> of Development) build config. in XCode. I think the build process
> may not be
> building the debug version of tokend.framework correctly.
That's right.
> Anyway, I
Henry B. Hotz wrote:
>
>
> On Mar 24, 2009, at 12:49 PM, Martin Paljak wrote:
>
>>
>> On 24.03.2009, at 21:42, Henry B. Hotz wrote:
>>>
>>> If you give me a hint, I'll try building under Leopard and look at
>>> the source. The WIKI (down last night) only describes building
>>> under Tiger. I
On Mar 24, 2009, at 12:49 PM, Martin Paljak wrote:
>
> On 24.03.2009, at 21:42, Henry B. Hotz wrote:
>>
>> If you give me a hint, I'll try building under Leopard and look at
>> the source. The WIKI (down last night) only describes building
>> under Tiger. I have darwinbuild and friends installe
On Mar 25, 2009, at 1:54 AM, Thomas Engelmeier wrote:
>
> Am Mar 24, 2009 um 8:09 PM schrieb Henry B. Hotz:
>
>> On Mar 24, 2009, at 6:27 AM, Miller, Timothy J. wrote:
>>
>>> FYI, Apple's SmartCardServices stuff is now out on MacForge:
>>>
>>> http://smartcardservices.macosforge.org/
>>>
>>> Not
Am Mar 24, 2009 um 8:09 PM schrieb Henry B. Hotz:
> On Mar 24, 2009, at 6:27 AM, Miller, Timothy J. wrote:
>
>> FYI, Apple's SmartCardServices stuff is now out on MacForge:
>>
>> http://smartcardservices.macosforge.org/
>>
>> Not sure if this includes tokend code, but there you go.
>>
>> -- Tim
>
>The hash value, BTW, is just the subject key identifier extension
>field in the cert. It's computed by the CA, you don't compute it
>yourself. (Only guaranteed to be unique for a single CA.) sc_auth is
>just a script layered on top of "dscl" and "security" if you feel like
>looking at such thin
On 24.03.2009, at 21:42, Henry B. Hotz wrote:
>
> If you give me a hint, I'll try building under Leopard and look at
> the source. The WIKI (down last night) only describes building
> under Tiger. I have darwinbuild and friends installed.
>
Don't bother with darwinbuild for now.
http://wi
On Mar 24, 2009, at 8:25 AM, Martin Paljak wrote:
1. According to the log and my testing, the cosmetic "show locked
icon" code is never called on 10.5.6. The lock icon has no practical
meaning (except for authenticating the first PIN once when clicked).
So it remains "locked" for now.
I can b
On Mar 24, 2009, at 6:27 AM, Miller, Timothy J. wrote:
> FYI, Apple's SmartCardServices stuff is now out on MacForge:
>
> http://smartcardservices.macosforge.org/
>
> Not sure if this includes tokend code, but there you go.
>
> -- Tim
It does. It doesn't build because it depends on 2-3 CDSA fra
.@lists.opensc-project.org] On Behalf Of Henry B. Hotz
>Sent: Sunday, March 22, 2009 1:37 PM
>To: Martin Paljak
>Cc: opensc-de...@opensc-project.org
>Subject: Re: [opensc-devel] Mac Tokend PIN Rejection
>
>
>On Mar 21, 2009, at 2:26 AM, Martin Paljak wrote:
>
>> On 21.03.20
1. According to the log and my testing, the cosmetic "show locked
icon" code is never called on 10.5.6. The lock icon has no practical
meaning (except for authenticating the first PIN once when clicked).
So it remains "locked" for now.
2. What happens with login is something I don't know and
On Mar 22, 2009, at 11:36 AM, Henry B. Hotz wrote:
>
> On Mar 21, 2009, at 2:26 AM, Martin Paljak wrote:
>
>> On 21.03.2009, at 2:34, Henry B. Hotz wrote:
>>
>>
>>> I'm willing to do some debugging, if someone will tell me what to
>>> look at. Maybe where to put syslog calls in a custom build?
>
On Mar 21, 2009, at 2:26 AM, Martin Paljak wrote:
> On 21.03.2009, at 2:34, Henry B. Hotz wrote:
>
>>> If it is a PIV card, you probably don't use OpenSC tokend, but the
>>> CAC
>>> one? I might be wrong. Anyway, you don't need to "unlock" the
>>> keychain, you need to provide the PIN when you us
On 21.03.2009, at 2:34, Henry B. Hotz wrote:
>> If it is a PIV card, you probably don't use OpenSC tokend, but the
>> CAC
>> one? I might be wrong. Anyway, you don't need to "unlock" the
>> keychain, you need to provide the PIN when you use a key/certificate
>> on the card.
>
>
> CAC uses the CA
On Mar 20, 2009, at 3:47 AM, Martin Paljak wrote:
> On 20.03.2009, at 7:36, Henry B. Hotz wrote:
>
>> I don't think I'm having any trouble with the PIN in normal OpenSC
>> operations, but I can't unlock the card in Apple's Keychain Access
>> app.
>>
>> NASA PIV card, SCM 331 reader, Leopard.
>>
>
On 20.03.2009, at 7:36, Henry B. Hotz wrote:
> I don't think I'm having any trouble with the PIN in normal OpenSC
> operations, but I can't unlock the card in Apple's Keychain Access
> app.
>
> NASA PIV card, SCM 331 reader, Leopard.
>
> Any pointers? How would I debug this?
AFAIK the lock in
I don't think I'm having any trouble with the PIN in normal OpenSC
operations, but I can't unlock the card in Apple's Keychain Access app.
NASA PIV card, SCM 331 reader, Leopard.
Any pointers? How would I debug this?
--
The opinions expressed
22 matches
Mail list logo
