On Fri, Mar 06, 2020 at 02:01:39PM -0500, Andrew Cagney wrote:
> Yea,
>
> On Fri, 6 Mar 2020 at 11:47, Antony Antony wrote:
> >
> > while fixing the bug, left=%eth1, reported in
> > https://lists.libreswan.org/pipermail/swan/2020/003458.html. I ran into a
> > !happy() and core dump. If I remove
On Sat, 29 Feb 2020, nupur agarwal wrote:
I am Nupur Agrawal, currently an undergraduate at IIT Roorkee. I am interested
in participating in GSoC 2020 with Libreswan this year. I am interested in BSD
Networking
hence different ideas listed on the website like "Re-port the libreswan code for
Yea,
On Fri, 6 Mar 2020 at 11:47, Antony Antony wrote:
>
> while fixing the bug, left=%eth1, reported in
> https://lists.libreswan.org/pipermail/swan/2020/003458.html. I ran into a
> !happy() and core dump. If I remove the following check the fix would work;
> test case addconn-05
>
>
while fixing the bug, left=%eth1, reported in
https://lists.libreswan.org/pipermail/swan/2020/003458.html. I ran into a
!happy() and core dump. If I remove the following check the fix would work;
test case addconn-05
sockaddr_to_endpoint
- /* XXX: to strict? */
- if
The certs could be in either of the two aggressive initiator messages.
However, the code is throwing away away the verified cert list every
time it tries to parse a CERT payload (present or not). As an aside,
this explains the log message:
-002 "westnet-eastnet-x509" #1: No Certificate Authority
