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 1290907 - ipsec initnss/checknss custom directory not recognized
Summary: ipsec initnss/checknss custom directory not recognized
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libreswan
Version: 7.2
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Paul Wouters
QA Contact: Jaroslav Aster
Mirek Jahoda
URL:
Whiteboard:
: 1288257 (view as bug list)
Depends On:
Blocks: 1077162 1266519 1274548 1335896
TreeView+ depends on / blocked
 
Reported: 2015-12-11 21:09 UTC by Brent Eagles
Modified: 2016-11-03 21:22 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Feature: support for custom location of nss database for the ipsec nss related commands Reason: some cloud frameworks do not use the default location of /etc/ipsec.d. Result: better support for cloud frameworks.
Clone Of:
: 1335896 (view as bug list)
Environment:
Last Closed: 2016-11-03 21:22:10 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2603 0 normal SHIPPED_LIVE Moderate: libreswan security and bug fix update 2016-11-03 12:13:02 UTC

Description Brent Eagles 2015-12-11 21:09:15 UTC
Copied from u/s: https://github.com/libreswan/libreswan/issues/44

"I set up Openstack with VPNaaS.

During creation process of the VPN this command is executed:
ip netns exec qrouter-664940e8-6139-4c36-8fcc-ee9e06bd5212 ipsec checknss /var/lib/neutron/ipsec/664940e8-6139-4c36-8fcc-ee9e06bd5212/etc

The db files are always added to the directory /etc/ipsec.d
Looking at the bash script "ipsec" i saw that the variable IPSEC_NSSDIR_SQL is set only at the beginning of the script.
If a custom directory is specified, the variable IPSEC_NSSDIR_SQL is not changed.

Adding IPSEC_NSSDIR_SQL="sql:${IPSEC_NSSDIR}" resolved the issue."

We are experiencing this issue in our neutron CI system. Our current version of libreswan is 3.15. 

The patch has been already been merged u/s in: 

https://github.com/libreswan/libreswan/commit/709e2a92d768afc6c78e5a243f0076ddec744c8a

Comment 6 Paul Wouters 2016-02-16 21:56:02 UTC
Since we need a respin for 7.1.x for FIPS, we should pull this in.

Comment 14 Brent Eagles 2016-06-06 20:21:58 UTC
*** Bug 1288257 has been marked as a duplicate of this bug. ***

Comment 18 errata-xmlrpc 2016-11-03 21:22:10 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://rhn.redhat.com/errata/RHSA-2016-2603.html


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