Bug 435308 - koji.fedoraproject.org has SSL issues
koji.fedoraproject.org has SSL issues
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: koji (Show other bugs)
rawhide
All Linux
low Severity high
: ---
: ---
Assigned To: David Cantrell
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-02-28 11:44 EST by Horst H. von Brand
Modified: 2013-01-09 20:48 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-02-28 11:54:14 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)

  None (edit)
Description Horst H. von Brand 2008-02-28 11:44:26 EST
Description of problem:
When trying to log in to koji (no, I don't know if I have an account there),
firefox complains that the site's certificate isn't trusted. After applying an
exception for the site, and clicking again on "Log in" I get an error
(copy&paste from Firefox):

  Secure Connection Failed

  An error occurred during a connection to koji.fedoraproject.org.

  SSL peer was unable to negotiate an acceptable set of security parameters.

  (Error code: ssl_error_handshake_failure_alert)
       

  The page you are trying to view can not be shown because the authenticity of 
the received data could not be verified.

      * Please contact the web site owners to inform them of this problem.

Version-Release number of selected component (if applicable):
No idea on koji
firefox-3.0-0.beta3.29.nightly20080227.fc9.i386
openssl-0.9.8g-5.fc9.i686

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Jesse Keating 2008-02-28 11:54:14 EST
That's because it's expecting you to have a cert (yours) imported, which if you
don't have an account, you won't.
Comment 2 Mike McLean 2008-02-28 14:05:06 EST
Since this is happening at the httpd level, I'm not sure if we can trap the
error and provide something more useful.  Might be worth looking into, but I
don't see it as a priority right now.

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