Bug 1760633

Summary:	if pluto daemon is manually started with non-default config file, addconn fork should use same config file
Product:	Red Hat Enterprise Linux 8	Reporter:	Paul Wouters <pwouters>
Component:	libreswan	Assignee:	Paul Wouters <pwouters>
Status:	CLOSED ERRATA	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	low	Docs Contact:
Priority:	medium
Version:	8.1	CC:	dapospis, omoris, pvrabec
Target Milestone:	rc	Keywords:	Patch, Triaged
Target Release:	8.0	Flags:	pwouters: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	3.30-1	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-04 03:18:00 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:
Bug Depends On:	1820206
Bug Blocks:

Description Paul Wouters 2019-10-11 00:59:28 UTC

When starting pluto using:

ipsec pluto --config /non/standard/test.conf

it starts up using this configuration file. But at the end of the startup it launches "addconn" that is responsible for all auto=add|route|start connections to actually startup. This addconn process was not passed the non-standard config file location and would use the default /etc/ipsec.conf. This results in connections not working on startup.

ipsec status also does not show the actual configuration file used for startup

Comment 1 Paul Wouters 2019-10-11 01:07:42 UTC

upstream patch: https://github.com/libreswan/libreswan/commit/8d4acad27bc98db8361fe285135c60c45b647158
upstream test case: https://github.com/libreswan/libreswan/tree/master/testing/pluto/addconn-04

Comment 12 errata-xmlrpc 2020-11-04 03:18:00 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 (libreswan bug fix and enhancement update), 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/RHEA-2020:4722