Updated tar.gz for the 0.9.2-P1 crash fix ("Improved handling of incoming
packets with invalid client-id and DUID.") I also added an XXX comment
to remind us to update the license marker for 1.0 because ISC are moving
to the Apache license :'(I'm still looking for OKs to import if anyone has time to look it over... On 2015/12/10 09:57, Stuart Henderson wrote: > On 2015/12/09 20:33, Patrik Lundin wrote: > > On Tue, Dec 08, 2015 at 11:15:04PM +0000, Stuart Henderson wrote: > > > On 2015/12/08 23:59, Patrik Lundin wrote: > > > > I have posted a question to kea-dev regarding this: > > > > https://lists.isc.org/pipermail/kea-dev/2015-December/000588.html > > > > > > > > Let's see how that goes. > > > > > > Good idea. > > > > > > > I have recieved a response now. As I do not think there is an > > overwhelming reason for using Botan I feel it is nicer to skip > > additional port dependencies and explicitly use our LibreSSL instead. > > > > The question remaining is if the configure flag should be --with-openssl > > or --with-openssl=/usr. While it seems the configure script will look > > for the library in an order that starts with /usr, I wonder if it is > > nicer to be explicit that we want to use the base version (rather than > > the openssl port for instance). > > > > Attached is a port with the explicit flag set and a shortened > > LIB_DEPENDS/WANTLIB list. I have tested that it ignores the use of Botan > > when it is installed. Let me know what you think. > > Either way is OK, I deliberately put the ports version of OpenSSL in a > directory that is unlikely to be searched by configure. (Unless it uses > something like the bonkers locate(1) check that freeradius3 uses, but > I digress...) > > Any OKs to import this version? >
kea,4.tgz
Description: application/tar-gz
