Re: [Opensc-devel] Adding libp11 (or its equivalent) to OpenSSL

[Andreas J. <an...@io...>]

found it, commit b2455b097f8bd9b0a075df3820ce21c6bf33357a in engine_pkcs11
has the same content as opensc in
commit bae2b51e01e16c126613289dd68e75545d3dd333 at least for these files:

aj@seiryu:~/opensc-git/src/sslengines$ md5sum ~/xx/xx/engine_pkcs11/src/*
f16abeabca8f30197b94f5cbbed56132
 /home/aj/xx/xx/engine_pkcs11/src/engine_pkcs11.c
e693a2a09ee07964722d71f1afbf1882
 /home/aj/xx/xx/engine_pkcs11/src/engine_pkcs11.def
9936c4fc0357e7c24ddc12abe66fcd06
 /home/aj/xx/xx/engine_pkcs11/src/engine_pkcs11.h
e4d4f039411f964636b11973d5617ffc
 /home/aj/xx/xx/engine_pkcs11/src/hw_opensc.c
8f7565d60db0ad6246c50b3282676bbf
 /home/aj/xx/xx/engine_pkcs11/src/hw_pkcs11.c
f4911e7a7cd3b44a4251ca8529f685bc
 /home/aj/xx/xx/engine_pkcs11/src/Makefile.am
003221d31d444bb8cd3ca09b7a305158
 /home/aj/xx/xx/engine_pkcs11/src/Makefile.mak
aj@seiryu:~/opensc-git/src/sslengines$ md5sum *
1a29991197312afe0b8d055e5912ce2f  engine_opensc.c
e4219829d19f13cc6c59f7a49d1d830c  engine_opensc.h
f16abeabca8f30197b94f5cbbed56132  engine_pkcs11.c
e693a2a09ee07964722d71f1afbf1882  engine_pkcs11.def
9936c4fc0357e7c24ddc12abe66fcd06  engine_pkcs11.h
e4d4f039411f964636b11973d5617ffc  hw_opensc.c
8f7565d60db0ad6246c50b3282676bbf  hw_pkcs11.c
cae21328df67ce552a790779bf3e4015  Makefile.am
003221d31d444bb8cd3ca09b7a305158  Makefile.mak
0afa2a574a5f83c7fa52cfe35fbd9098  test_engine.sh

thus the code can be tracked back to opensc that way. Also the code at that
age is already BSD-2 or OpenSSL licensed.

engine_pkcs11.def is trivial and I guess you have no need to reuse old
Makefiles. Thus you should be all good?

Regards, Andreas

2016-03-01 17:43 GMT+01:00 David Woodhouse <dw...@in...>:

> On Tue, 2016-03-01 at 16:12 +0100, Andreas Jellinghaus wrote:
>
> > Yes, all code from me for libp11 may be re-used under the BSD-3 clause.
> > Same applies to engine_pkcs11 or pam_p11 (the two users of libp11
> > that I'm aware off), in case that is helpful.
>
> Thank you.
>
> > Please note that I created libp11 mostly by splitting
> > engine_pkcs11/opensc code into a new project, so that I can use it
> > for a pam module I was adding. At least that is how I remember it.
> > Thus most code under my name might come from Olaf Kirch instead, but
> > he has given the same approval already for all I know.
>
> Actually, the interesting part starts before that. You moved the code
> out from OpenSC to separate engine_pkcs11 and libp11 repositories in
> August/September 2005.
>
> But they all appeared, in a big lump, in OpenSC in May 2003:
> https://github.com/OpenSC/OpenSC/commit/496232d9b
>
> Where did they come from before that?
>
> There are commits earlier in the OpenSC history which strongly imply
> that the engine code was already there — Olaf's commit f169b5c891
> tweaks some autoconf code and is titled "only build sslengine if
> OpenSSL supports it". But according to the git history there *is* no
> code at that point; only the autoconf test...
>
> --
> dwmw2
>
>