Re: License clarification

Ludovic Rousseau <[email protected]>
Newsgroups gmane.comp.encryption.opensc.devel
Message-ID <CAGstE8AiiOjVYmsWUB4AMhJ+HWJLL2BL-96JhCgphA8QkYLf+g@mail.gmail.com>
Hello,

2017-03-06 12:11 GMT+01:00 Andreas Jellinghaus <[email protected]>:
>
> 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.

>From a file comment:
/* Mostly copied from pcsc-lite, this is the minimum required */

So the license should be the same as for pcsc-lite i.e. 3-clause BSD
license as in, the original,
https://github.com/LudovicRousseau/PCSC/blob/master/src/PCSC/winscard.h

> 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.

I wrote this file because the corresponding strlcpy.c has no .h file.
I added a license in the strlcpycat.h file for pcsc-lite. See
https://github.com/LudovicRousseau/PCSC/blob/master/src/strlcpycat.h

Bye

--
 Dr. Ludovic Rousseau

------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensc-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.