Bug 1144655 - Wrong DSA_generate_parameters result
Summary: Wrong DSA_generate_parameters result
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: openssl
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomas Mraz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-20 06:54 UTC by Ivan Romanov
Modified: 2014-09-22 09:14 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-09-22 09:14:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
test-case to reproduce error (549 bytes, application/octet-stream)
2014-09-20 06:54 UTC, Ivan Romanov
no flags Details

Description Ivan Romanov 2014-09-20 06:54:46 UTC
Created attachment 939480 [details]
test-case to reproduce error

Description of problem:
There is a DSA KeyPair Generation Algorithm. If I provide seed from this 
algorithm I must get always constant result. http://docs.oracle.com/javase/7/docs/technotes/guides/security/StandardNames.html#algspec . I wrote minimal test-case. To check this. The test-case always show various wrong key. I obtained the code. Seems provided seed is not used. DSA_generate_parameters thinks seed is bad, so it uses any random seed in really.

Version-Release number of selected component (if applicable):
openssl-1.0.1e-39.fc20.x86_64

How reproducible:
Always

Steps to Reproduce:
Unpack archive and start build.sh. It compiles minimal test-case and run it.

Actual results:
Always various.

Expected results:
Constant key.

Additional info:
It works in Debian testing, also my QCA unittests passed in build.kde.org environment. In build.kde.org also is used Debian.

Comment 1 Tomas Mraz 2014-09-22 09:14:48 UTC
The DSA parameter generation in our openssl is replaced by parameter generation based on the current FIPS specification. This means the seed for the older specification cannot be used as you found out.
Parameters <2048bits are not sufficiently secure anymore anyway.


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