[20180] in Kerberos_V5_Development
Re: Building the PKINIT plugin on Windows
daemon@ATHENA.MIT.EDU (Greg Hudson)
Fri Oct 9 18:54:43 2020
To: Ken Hornstein <kenh@cmf.nrl.navy.mil>, <krbdev@mit.edu>
From: Greg Hudson <ghudson@mit.edu>
Message-ID: <c7949123-c267-5bd1-804e-7f4928353236@mit.edu>
Date: Fri, 9 Oct 2020 18:54:24 -0400
MIME-Version: 1.0
In-Reply-To: <202010091940.099JeXHY030172@hedwig.cmf.nrl.navy.mil>
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
On 10/9/20 3:40 PM, Ken Hornstein wrote:> BTW, would the license on the
Henry Spencer regex library be acceptable?
>
> https://github.com/garyhouston/regex/blob/master/COPYRIGHT
It's not ideal; it looks similar to 3-clause BSD but is written in an
informal style, with the liability disclaimer phrased as a fourth
licensing restriction. That might create doubts as to whether it meets
the usual criteria that people find important (DFSG-free, non-copyleft,
GPL-compatible). We already get complaints about the wording
differences between many similar licenses in the tree (I got one just
this week about the license in the old version of the Gladman AES code
we have in lib/crypto, for instance).
I didn't see a response to the idea of wrapping std::regex, which I
believe ships with Visual Studio and wouldn't require us to add code to
the tree or instructions for the dev environment setup.
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
