[20181] in Kerberos_V5_Development
Re: Building the PKINIT plugin on Windows
daemon@ATHENA.MIT.EDU (Ken Hornstein)
Fri Oct 9 19:11:08 2020
Message-ID: <202010092309.099N9eM5031147@hedwig.cmf.nrl.navy.mil>
From: Ken Hornstein <kenh@cmf.nrl.navy.mil>
To: Greg Hudson <ghudson@mit.edu>
In-Reply-To: <c7949123-c267-5bd1-804e-7f4928353236@mit.edu>
MIME-Version: 1.0
Date: Fri, 09 Oct 2020 19:09:39 -0400
Cc: krbdev@mit.edu
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
>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'll look around then.
>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.
Personally, that sounds like such an awful nightmare to me that I didn't
even consider it. If we are already saying OpenSSL is an external
dependency, we could also say that a regex library is as well and
provide some links so people could choose their own.
--Ken
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
