Re: [Opensc-devel] License clarification

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

Hi Jakub,

my assumption always was: one clear license statement for the whole
software is good enough - only divergent files got marked as such.
For the core files we might have the boilerplate in each file, but I felt
that was "nice to have", and not essential.

All files are good from my perspective, as they are opensc core files, only
these two could be checked in detail:

src/libopensc/internal-winscard.h

ah, seems this was added in 2008 as part of some build system change?
ludovic would know what license this would have, if it comes from pcsc.

https://pcsclite.alioth.debian.org/api/winscard_8h_source.html

indicates BSD license, but it is better to clarify this with ludovic.

src/common/compat_strlcpy.h

either this file is too trivial to be protected by copyright, or it is
licensed under the same BSD clause as compat_strlcpy.c. Either way opensc
is fine.

Regards, Andreas

2017-03-06 10:57 GMT+01:00 Jakub Jelen <jj...@re...>:

> Hello,
> I was going through the files in the OpenSC repository and noticed
> several files with missing/unknown licenses.
>
> These files miss any open source license headers (adding Olaf Kirch if
> the email is still valid who is author):
>
> src/pkcs15init/pkcs15-init.h
> src/pkcs15init/profile.h
> src/libopensc/reader-openct.c
> src/common/libpkcs11.c
> src/pkcs11/mechanism.c
> src/pkcs11/openssl.c
>
>
> These files miss also header, but says about the source in pcsc-lite
> (adding Ludovic, who should be able to clarify the license):
>
> src/libopensc/internal-winscard.h
> src/common/compat_strlcpy.h
>
>
> Several more files without contact information:
>
> src/common/compat_report_rangecheckfailure.c
> src/common/compat_getopt_main.c
>
>
> And some more files from Juha Yrjölä (if the mail still works) without
> any open source license header:
>
> src/tests/lottery.c
> src/tests/p15dump.c
> src/tests/pintest.c
> src/tests/print.c
> src/tests/prngtest.c
>
> Can we get the clarification from the original authors, or is there
> somebody in the project who would be able to clarify the licenses and
> update the files to make sure the license is in align with the project?
>
> Thanks,
> --
> Jakub Jelen
> Software Engineer
> Security Technologies
> Red Hat
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Opensc-devel mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensc-devel
>