Bug 1367121

Summary:	when receiving a Delete request in IKEv2 for an auto=start tunnel, the tunnel is not re-initiated
Product:	Red Hat Enterprise Linux 7	Reporter:	Paul Wouters <pwouters>
Component:	libreswan	Assignee:	Paul Wouters <pwouters>
Status:	CLOSED ERRATA	QA Contact:	Ondrej Moriš <omoris>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3	CC:	omoris, pwouters
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	3.20-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 12:31:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Paul Wouters 2016-08-15 15:22:43 UTC

When a tunnel is configured with auto=start, the tunnel is supposed to remain up.
When the remote end sends a delete, the tunnel is torn down, but no new tunnel is initiated. Also, the tunnel is placed in "auto=add" mode, not "auto=route", causing a potential plaintext packet leak.

note that a DPD/liveness failure at the remote can cause it to send a delete request.

See also the discussion at:


https://lists.libreswan.org/pipermail/swan-dev/2016-July/001537.html

Comment 4 Ondrej Moriš 2017-06-23 18:55:33 UTC

Successfully verified on all architectures that connection with auto=start is re-initiated after:

 * ipsec auto --down <conn>
 * ipsec whack --deletestate <newest_ipsec_sa_id>

from remote end. Please notice that connection is NOT re-initiated after:

 * ipsec whack --name <conn> --delete 

For more details, please see TJ#1921798.

Comment 5 errata-xmlrpc 2017-08-01 12:31:06 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2101