Hello Ludovic,

1. The new version prompt some annoying messages in X... This is
related to the new pam_prompt addition when HAVE_SECURITY_PAM_EXT_H is
defined.

2. I've look at the code. It seems like you added the whole nss into
the source... I don't understand why... You can use the external
library files.

3. Regarding the pkcs11-helper...

The problem is that NSS addition is somewhat strange... I expected
that it will replace OpenSSL entirely... So that you can run current
PKCS#11 implementation with NSS... This requires the abstraction
library for certificate and digest will be implemented as standalone,
and use this throughout the whole package.

If it had been so, it would been easy to offer alternative that uses
NSS or OpenSSL as a crypto engine and NSS PKCS#11 implementation or
pkcs11-helper implementation.

I have one more problem regarding the slot number... For a strange
reason the pam_pkcs11 bothers the user with numeric slot/string
number... What happens if there are several providers? Readers? etc...
For this reason I abstract it in pkcs11-helper... I wished to removed
this one from pam_pkcs11 so that all available certificate objects are
validated against the mappers.

But the current state requires too much work...

I regret to say, I don't have the time right now. I think that before
the NSS additions, I could have cleaned up the code faster...

Sorry,
Alon Bar-Lev.

On 6/12/07, Ludovic Rousseau <[EMAIL PROTECTED]> wrote:
> On 11/06/07, Alon Bar-Lev <[EMAIL PROTECTED]> wrote:
> > BTW: We can shrink up the code if next version will use pkcs11-helper :)
>
> Please, send a patch.
> I just hope it will not collide with the NSS support. I imagine NSS
> and pkcs11-helper are orthogonal features, aren't they?
>
> bye
>
> --
>   Dr. Ludovic Rousseau
> _______________________________________________
> opensc-devel mailing list
> [email protected]
> http://www.opensc-project.org/mailman/listinfo/opensc-devel
>
_______________________________________________
opensc-devel mailing list
[email protected]
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Reply via email to