Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 549811 - Openswan (pluto) logs NSS password which should not happen
Openswan (pluto) logs NSS password which should not happen
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: openswan (Show other bugs)
5.5
All Linux
urgent Severity high
: rc
: 5.5
Assigned To: Avesh Agarwal
Aleš Mareček
: Security, ZStream
Depends On:
Blocks: 557688
  Show dependency treegraph
 
Reported: 2009-12-22 13:10 EST by Avesh Agarwal
Modified: 2012-11-19 08:54 EST (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-02-21 00:58:37 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0211 normal SHIPPED_LIVE openswan bug fix and enhancement update 2012-02-20 10:08:08 EST

  None (edit)
Description Avesh Agarwal 2009-12-22 13:10:29 EST
Description of problem:

Openswan (pluto) logs NSS password at the run time

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

How reproducible:
Alwys

Steps to Reproduce:
1. While establishing a connection, put the NSS database in FIPS mode.
2.
3.
  
Actual results:
NSS password is logged

Expected results:
NSS password should not be logged.

Additional info:
Comment 23 errata-xmlrpc 2012-02-21 00:58:37 EST
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.

http://rhn.redhat.com/errata/RHBA-2012-0211.html

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