On Fri, Jan 13, 2012 at 1:41 AM, Viktor Tarasov
wrote:
> Le 12/01/2012 15:00, LinuxChuck a écrit :
>> Are there any event logs or debug logs I should try to gather to determine
>> the cause of this error?
>
> Look for the file c:\tmp\md.log . This path is hard encoded into
On Tue, Jan 10, 2012 at 2:55 AM, Viktor Tarasov
wrote:
> Fine,
> if possible, keep us informed about your successes (or else) with your
> application.
> It's interesting to get know more about usage cases.
>
>
Here's an update:
I can successfully read certificates from these CardOS 4.4 cards no
ional tests since I have access to Windows
7 X64 with CardOS 4.4 cards, I'll be happy to help.
Thanks again!!!
On Wed, Jan 4, 2012 at 1:44 PM, LinuxChuck wrote:
> On Fri, Dec 30, 2011 at 11:51 AM, Viktor Tarasov
> wrote:
>> 'It-works-for-me' on Windows 7(64bits) with
On Fri, Dec 30, 2011 at 11:51 AM, Viktor Tarasov
wrote:
> 'It-works-for-me' on Windows 7(64bits) with the OpenSC.msi(64bits) built on
> the same platform with VS-2010.
>
> I've had the seg.fault problems with the opensc tools from the
> 'nightly-built' that was built, apparently, on the same sou
Hello all,
Be warned, I am learning all of this as I go, so there may be some
obvious mistakes below that could easily solve my problems. Feel free
to point those out. :-)
I've recently finalized the lengthy NDA process that allows me access
to the keys for unlocking and initializing my CardOS
Edited a bit for brevity...
On Mon, Aug 29, 2011 at 11:59 PM, Martin Paljak wrote:
>> I'm in the process of preparing a migration from Aladdin USB eToken
>> (CardOS 4.2) PKI tokens to credit-card contact chip PKI ID cards with
>> built-in OTP functionality. The vendor has provided me with the
>>
Hello,
Allow me to start by announcing that I am new to PKI smart-card
management with OpenSC, and have only had experience working with
Aladdin eToken devices and their proprietary middleware. However, I
am fairly well versed in the concepts and fundamentals of PKI in
general.
I've been reading
