Bug 814859 - openssl FIPS: speed command segfaults with forbidden alogrithms in FIPS mode
openssl FIPS: speed command segfaults with forbidden alogrithms in FIPS mode
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: openssl (Show other bugs)
6.3
All Linux
unspecified Severity medium
: rc
: ---
Assigned To: Tomas Mraz
BaseOS QE Security Team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-04-20 17:06 EDT by Miroslav Vadkerti
Modified: 2012-04-23 02:26 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-04-23 02:26:10 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Miroslav Vadkerti 2012-04-20 17:06:23 EDT
Description of problem:
[root@x86-64-v10 ~]# openssl speed blowfish
bf_skey.c(70): OpenSSL internal error, assertion failed: BF Algorithm forbidden in FIPS mode
Aborted (core dumped)
[root@x86-64-v10 ~]# openssl speed rc2
rc2_skey.c(107): OpenSSL internal error, assertion failed: RC2 Algorithm forbidden in FIPS mode
Aborted (core dumped)
[root@x86-64-v10 ~]# openssl speed seed
seed.c(203): OpenSSL internal error, assertion failed: SEED Algorithm forbidden in FIPS mode
Aborted (core dumped)
[root@x86-64-v10 ~]# openssl speed rc4
rc4_fblk.c(71): OpenSSL internal error, assertion failed: RC4 Algorithm forbidden in FIPS mode
Aborted (core dumped)

Version-Release number of selected component (if applicable):
openssl-1.0.0-20.el6_2.4

How reproducible:
100%

Steps to Reproduce:
1. Switch machine to FIPS mode
1. openssl speed [unsupported cipher]
  
Actual results:
segfault

Expected results:
no segfault

Additional info:
Tested only on i686 architecture. Setting medium priority as openssl speed command is not really used anywhere.
Comment 2 Tomas Mraz 2012-04-23 02:26:10 EDT
This is not a _segfault_! This is abort. There is no need to fix it.

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