On Wed, Jan 22, 2020 at 04:32:42PM -0500, Paul Wouters wrote:
> On Wed, 22 Jan 2020, Antony Antony wrote:
>
> > > As no other people are weighing in, I'll stop objecting provided the
> > > parser crashers are resolved.
> >
> > thanks! lets give the new idea a shot.
>
> That's not how API's
On Wed, Jan 22, 2020 at 03:08:45PM -0500, Paul Wouters wrote:
> On Wed, 22 Jan 2020, Antony Antony wrote:
>
> > > I still believe yes/no is not appropriate here. As for using numbers or
> > > %unique, we already have that being used for the mark keyword(s) in the
> > > parser. So that
On Sat, 11 Jan 2020, Paul Wouters wrote:
I'm confused why I am seeing:
002 "ikev2-westnet-eastnet-x509-cr" #1: NSS Password file
"/etc/ipsec.d/nsspassword" for token "OpenDNSSEC" could not be opened for
reading
It turns out this is caused by /usr/lib64/p11-kit-proxy.so from p11-kit.
This
On Wed, 22 Jan 2020, Antony Antony wrote:
I still believe yes/no is not appropriate here. As for using numbers or
%unique, we already have that being used for the mark keyword(s) in the
parser. So that functionality is already there.
I disagree. I think no|yes| is cleaner for this kind of
On Wed, Jan 22, 2020 at 08:47:47AM -0500, Paul Wouters wrote:
> On Wed, 22 Jan 2020, Antony Antony wrote:
>
> > > > Note 0x is necessary.
> > >
> > > That is not how our parser works normally.
> >
> > I am not sure what your are implying here.
>
> That we have numbers and set interpretations.
On Wed, Jan 22, 2020 at 05:50:27AM -0500, Paul Wouters wrote:
> On Wed, 22 Jan 2020, Antony Antony wrote:
>
> > this morning in a testrun I noticed a bunch of coredump from addcon
> > https://swantest.libreswan.fi/s2/v3.28-1487-g3d33747478-testrun-xfrmi/
> > I will investigate addcon crash today.
On Wed, 22 Jan 2020, Antony Antony wrote:
this morning in a testrun I noticed a bunch of coredump from addcon
https://swantest.libreswan.fi/s2/v3.28-1487-g3d33747478-testrun-xfrmi/
I will investigate addcon crash today.
current configuration option is
ipsec-interface=no|yes| where n =
