Bug 1935339 - virtual_private setting is missing in the default config [rhel-8.5.0]
Summary: virtual_private setting is missing in the default config [rhel-8.5.0]
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: libreswan
Version: 8.4
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Daiki Ueno
QA Contact: Ondrej Moriš
Depends On: 1934186 1936492 1958968
TreeView+ depends on / blocked
Reported: 2021-03-04 16:29 UTC by RHEL Program Management Team
Modified: 2021-11-10 01:34 UTC (History)
2 users (show)

Fixed In Version: libreswan-4.4-1.el8
Doc Type: No Doc Update
Doc Text:
Clone Of: 1934186
Last Closed: 2021-11-09 18:49:51 UTC
Type: ---
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CRYPTO-5253 0 None None None 2021-11-09 18:55:58 UTC
Red Hat Product Errata RHBA-2021:4299 0 None None None 2021-11-09 18:50:02 UTC

Comment 3 Ondrej Moriš 2021-03-16 15:24:37 UTC
See parent bug for AC. 

Successfully verified with libreswan-4.3-3.el8 on RHEL-8.5.0-20210313.n.0:

# cat /etc/redhat-release 
Red Hat Enterprise Linux release 8.5 Beta (Ootpa)

# rpm -q libreswan

# cat /etc/ipsec.conf 
# /etc/ipsec.conf - Libreswan 4.0 configuration file
# see 'man ipsec.conf' and 'man pluto' for more information
# For example configurations and documentation, see https://libreswan.org/wiki/

config setup
	# If logfile= is unset, syslog is used to send log messages too.
	# Note that on busy VPN servers, the amount of logging can trigger
	# syslogd (or journald) to rate limit messages.
	# Debugging should only be used to find bugs, not configuration issues!
	# "base" regular debug, "tmi" is excessive (!) and "private" will log
	# sensitive key material (not available in FIPS mode). The "cpu-usage"
	# value logs timing information and should not be used with other
	# debug options as it will defeat getting accurate timing information.
	# Default is "none"
	# plutodebug="base"
	# plutodebug="tmi"
	# Some machines use a DNS resolver on localhost with broken DNSSEC
	# support. This can be tested using the command:
	# dig +dnssec DNSnameOfRemoveServer
	# If that fails but omitting '+dnssec' works, the system's resolver is
	# broken and you might need to disable DNSSEC.
	# dnssec-enable=no
	# To enable IKE and IPsec over TCP for VPN server. Requires at least
	# Linux 5.7 kernel or a kernel with TCP backport (like RHEL8 4.18.0-291)
	# listen-tcp=yes
	# To enable IKE and IPsec over TCP for VPN client, also specify
	# tcp-remote-port=4500 in the client's conn section.

# if it exists, include system wide crypto-policy defaults
include /etc/crypto-policies/back-ends/libreswan.config

# It is best to add your IPsec connections as separate files
# in /etc/ipsec.d/
include /etc/ipsec.d/*.conf

Comment 7 errata-xmlrpc 2021-11-09 18:49:51 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.


Note You need to log in before you can comment on or make changes to this bug.