RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2039877 - drop IKEv1 packets by default
Summary: drop IKEv1 packets by default
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: libreswan
Version: 9.0
Hardware: All
OS: Linux
medium
unspecified
Target Milestone: rc
: ---
Assignee: Daiki Ueno
QA Contact: Ondrej Moriš
Jan Fiala
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-12 16:12 UTC by Ondrej Moriš
Modified: 2022-05-27 12:25 UTC (History)
4 users (show)

Fixed In Version: libreswan-4.6-3.el9
Doc Type: Enhancement
Doc Text:
.Libreswan does not accept IKEv1 packages by default Because the Internet Key Exchange v2 (IKEv2) protocol is now widely deployed, Libreswan no longer supports IKEv1 packets by default. IKEv2 provides a more secure environment and more resilience against attacks. If your scenario requires the use of IKEv1, you can enable it by adding the `ikev1-policy=accept` option to the `/etc/ipsec.conf` configuration file.
Clone Of:
Environment:
Last Closed: 2022-05-17 13:44:16 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CRYPTO-6057 0 None None None 2022-01-18 14:35:44 UTC
Red Hat Issue Tracker RHELPLAN-107600 0 None None None 2022-01-12 16:19:30 UTC
Red Hat Product Errata RHBA-2022:2575 0 None None None 2022-05-17 13:44:19 UTC

Description Ondrej Moriš 2022-01-12 16:12:08 UTC
Description of problem:

Libreswan now (4.3) supports policy for IKEv1 packets. By default they are allowed. In RHEL-9 it would be good to put a barrier to using old IKEv1 by setting 'drop' ikev1-policy in default ipsec.conf. Please notice that this wouldn't change the default (which is 'accept') but rather explicitly configure default libreswan installation not to use the default.

Version-Release number of selected component (if applicable):

libreswan-4.3

Additional info:

This setting causes that no IKEv1 connection will be loaded. We need to document this changes properly. It is also quite clear that upstream is planning to get rid of IKEv1 (strongswan too) and we won't be able to guarantee full support for IKEv1 during RHEL-9 lifecycle.

Comment 13 errata-xmlrpc 2022-05-17 13:44:16 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 (new packages: libreswan), 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-2022:2575


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