mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] libmd: specification of license tags
Date: Tue, 4 Oct 2016 16:19:47 +0200	[thread overview]
Message-ID: <20161004141947.gfohtw7l5hiywopz@pengutronix.de> (raw)
In-Reply-To: <1475525936.15532.48.camel@ws-apr.office.loc>

On Mon, Oct 03, 2016 at 10:18:56PM +0200, Andreas Pretzsch wrote:
> While updating the license stuff in a customer BSP, libmd hit me.
> 
> libmd provides MD2, MD4, MD5, SHA-1 and RIPEMD-160 message digest
> algorithms.
> Each of the respective implementations includes different license
> statements, with wrappers under beer-ware license.
> Copied them in below, for reference.
> 
> The ptxdist rule file does not specify a license. Well, no surprise.
> Question would be how to handle this.
> 
> One option is of course to simply ignore it, i.e. not use it ;-)
> As of now, in ptxdist I see ntp pulling it in, for MD5. But it has its
> own implementation, so...
> Also, libarchive would be willing to take it, but prefers
> OpenSSL/libcrypto, as being more complete. Also no dependency in ptxdist
> here.
> Maybe other packages would take it, too, didn't check.
> 
> Now, as I have this can of worms open anyway, what would be the best way
> to specify a license tag ?
> I only see providing ptxdist patches to copy out the license headers to
> files, and referring to them in LIBMD_LICENSE_FILES.
> In addition to a list in LIBMD_LICENSE. Like "RSA (MD2, MD4) ;
> public-domain (MD5) ; unknown (RIPEMD160) ; public-domain (SHA-1) ;
> beer-ware (ALL)", or similar.
> 
> Probably one has to go even further (to avoid the RSA attribution
> clauses) and provide options for MD2 and MD4.
> 
> But before investing the time: Does anybody care ?

In this case, I'd say, let's just move the package to staging and not use
it at all. As I noted in my other mail, even ntp is not using it any more,
so it is no longer needed.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  parent reply	other threads:[~2016-10-04 14:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-03 20:18 Andreas Pretzsch
2016-10-03 23:25 ` Roland Hieber
2016-10-04 14:26   ` Michael Olbrich
2016-10-04 16:19     ` Andreas Pretzsch
2016-10-04 14:19 ` Michael Olbrich [this message]
2016-10-04 16:12   ` Andreas Pretzsch

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161004141947.gfohtw7l5hiywopz@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox