Hi.
On Feb 2, 2008, at 12:26 AM, Alon Bar-Lev wrote:
> Ludovic, I need some help in reader-pcsc:
> 1. How can I detect if SCardControl is old or new? I am sure I can do
> this by detecting some other fact.
Do you mean the number of parameters passed to SCardControl? I believe
you just have to k
On Feb 2, 2008, at 12:11 AM, Alon Bar-Lev wrote:
> Using Manifests requires to be more dependent on Microsoft
> technologies. Also it has nothing to do with security. A simpler
> solution would be to create a new DLL name for each release.
Windows is Windows is owned by Microsoft and this is a sad
Hi!
On Feb 2, 2008, at 12:06 AM, Douglas E. Engert wrote:
> Alon Bar-Lev wrote:
>> Requiring Microsoft compile for free software is somewhat
>> strange... :)
>
> Why? Using the vendor's compiler is common on many platforms,
> especially if your code is in the kernel, or is security
> related, lik
On Feb 2, 2008, at 12:26 AM, Alon Bar-Lev wrote:
> 2. Download latest libtool for win32 [3].
>
> [[[Does someone know why is this used for Windows, I believe a simple
> LoadLibrary(), GetProcAddress() should do.]]]
There used to be scdl
(http://www.opensc-project.org/opensc/browser/releases/ope
Hey Alon, this sounds like a good deal! So I'm afraid I can't help with
Winedoze and can't voice an opinion on that part...I didn't even knew
that it requires MS compilers ;-)
Alon Bar-Lev wrote:
Hello All,
It all started as result of OpenSSL incompatibility between an
application and OpenSC
Alon Bar-Lev wrote:
> Hello All,
>
> It all started as result of OpenSSL incompatibility between an
> application and OpenSC PKCS#11 provider.
>
> I quickly learned that OpenSC is built for Windows only using
> Microsoft compiler.
>
> Requiring Microsoft compile for free software is somewhat s
On 2/1/08, Alon Bar-Lev <[EMAIL PROTECTED]> wrote:
> It took some effort, but at the end I have a test release that uses a
> single autoconf/automake/libtool build system for all operating
> systems.
Forgot to describe how to build for Windows...
I build using cross compile on Linux to mingw32 ta
On 2/2/08, Douglas E. Engert <[EMAIL PROTECTED]> wrote:
> Why? Using the vendor's compiler is common on many platforms,
> especially if your code is in the kernel, or is security
> related, like OpenSC and runs with operating system privileges.
I disagree completely, and believe the other way arou
On 2/1/08, Eddy Nigg (StartCom Ltd.) <[EMAIL PROTECTED]> wrote:
>
> Hey Alon, this sounds like a good deal! So I'm afraid I can't help with
> Winedoze and can't voice an opinion on that part...I didn't even knew that
> it requires MS compilers ;-)
Thanks!
You can check if the new tarball compiles
Hello All,
It all started as result of OpenSSL incompatibility between an
application and OpenSC PKCS#11 provider.
I quickly learned that OpenSC is built for Windows only using
Microsoft compiler.
Requiring Microsoft compile for free software is somewhat strange... :)
Also, it required OpenSC d
On Feb 1, 2008 1:42 PM, Franz Brandl <[EMAIL PROTECTED]> wrote:
> Dear OpenSC Admins,
Hello,
> i have created a patch for the Austrian A-Trust ACOS card, since an updated
> card generation is under way (with 2 more possible ATRs), and i have also
> fixed a minor bug. Please apply it to the next m
I wrote the driver from scratch. For the moment it recognizes only one
certificate and key pairs of 2048 bit.
The mapping of memory is proprietary, so i search for certificate with
pattern 30 82 etc...
The driver is under testing (Linux, windows xp/vista and Mac work fine
with Thunderbird and Fire
On Feb 1, 2008 1:48 PM, Franz Brandl <[EMAIL PROTECTED]> wrote:
> Hi all,
Hello,
> when testing a new generation of A-Trust ACOS based cards, i came across the
> fact that the cards do not work with OpenSC when the lock_login parameter is
> set to False.
What is the problem exactly with lock_log
On Feb 1, 2008 11:50 AM, Antonio Nastasi <[EMAIL PROTECTED]> wrote:
> Hi, i wrote a driver for gemsafe V1 ( Xpresso 16k/32k )
Have you wrote the driver from scratch or you reused the code already
in OpenSC in src/libopensc/card-gemsafeV1.c
Can you post your patch for integrartion inside OpenSC?
Dear OpenSC Admins,
i have created a patch for the Austrian A-Trust ACOS card, since an updated
card generation is under way (with 2 more possible ATRs), and i have also fixed
a minor bug. Please apply it to the next major release.
Best regards
Franz Brandl
Hi all,
when testing a new generation of A-Trust ACOS based cards, i came across the
fact that the cards do not work with OpenSC when the lock_login parameter is
set to False. The parameters default value has been changed some time ago, as i
learned, so that the cards now do not work with a def
Hi, i wrote a driver for gemsafe V1 ( Xpresso 16k/32k ) and now i am
testing it on Windows. Thunderbird and Firefox recognized fine the smart
card with opensc-pkcs11.dll . I tested it also in linux.
Now i would use it with Internet Explorer and Outlook and so i read
http://www.opensc-project.org/sc
17 matches
Mail list logo
