Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
From: bugzilla@apache.org
To: dev@tomcat.apache.org
Subject: [Bug 56027] Unable to use TCN on RHEL6 boxes if box is booted in
 fips mode
Date: Fri, 17 Jan 2014 16:33:10 +0000
Message-ID: <bug-56027-78-nTqINOYRlz@https.issues.apache.org/bugzilla/>
In-Reply-To: <bug-56027-78@https.issues.apache.org/bugzilla/>
References: <bug-56027-78@https.issues.apache.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Auto-Submitted: auto-generated
MIME-Version: 1.0

https://issues.apache.org/bugzilla/show_bug.cgi?id=56027

--- Comment #3 from Christopher Schultz <chris@christopherschultz.net> ---
This bug will likely require (at least) two separate patches: one for avoiding
double-entry into FIPS mode, one for changing the key sizes used, and possibly
one for creating a native-wrapper around the FIPS_mode function call so Java
can inspect the current status and take appropriate action.

I think the best situation would be to allow the user to specify more than
simply "on" versus "off" for the FIPSmode configuration attribute: it would be
nice to use something like "on" to enable FIPS mode by calling FIPS_mode_set if
necessary, "require" to require that FIPS mode already be enabled (or throw an
exception and refuse to start the connector), or maybe a third option like
"enter" which would attempt to enter FIPS mode and fail if FIPS mode were
already enabled (this is the current behavior).

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org