On Mon, 12 Mar 2018 22:40:12 +0200
Yauheni Kaliuta [off-list ref] wrote:

Hi, Michal!
=20

quoted

quoted

quoted

quoted

quoted

On Mon, 12 Mar 2018 16:42:57 +0100, Michal Such=C3=A1nek  wrote: =20

=20
 > On Thu,  8 Mar 2018 15:58:08 +0200
 > Yauheni Kaliuta [off-list ref] wrote: =20
=20
 >> What bothers me is that asn1c files are generated under BSD
 >> license. =20
=20
 > What bothers me more license-wise is the pkcs7.asn1 coming from
 > kernel which is licensed under GPL. =20
=20
Better to ask lawers, but it is not code, but data based on the RFCs
and it is not part of the library to link with (VS the BSD code,
generated by asn1c).

Based on RFCs does not have any meaning - work based on RFCs can be
distributed under any license.

It is part of the library because the generated parser is based on the
data - without the data it cannot be generated.

Finally the asn1c compiler does not cleanly separate asn1c itself and
parsers generated by asn1c - at least some of the parser files
indeed carry the asn1c license. So to fulfill the license requirements
you should probably add a notice about the asn1c used and copy the
asn1c license information somewhere. Unfortunately, asn1c does not by
itself print a license banner. The best information it provides is
asn1c -h |& head -n 2 for version but the license text has to be stored
separately.

It is useful to store the version of asn1c used for generating the
files anyway because it gives the user some idea about the asn1c issues
that might affect the code.

Thanks

Michal