RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 668590 - Could not negotiate a supported cipher suite.
Summary: Could not negotiate a supported cipher suite.
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: gnutls
Version: 6.0
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: rc
: ---
Assignee: Tomas Mraz
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-10 20:46 UTC by Jóhann B. Guðmundsson
Modified: 2016-10-24 19:19 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-04-04 12:51:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
/etc/cups/cupsd.conf (4.74 KB, text/plain)
2011-01-10 20:47 UTC, Jóhann B. Guðmundsson 		no flags Details
/var/log/cups/error.log (3.08 KB, text/plain)
2011-01-10 20:47 UTC, Jóhann B. Guðmundsson 		no flags Details
openssl test (4.54 KB, text/plain)
2011-01-10 20:48 UTC, Jóhann B. Guðmundsson 		no flags Details
gnutls test (1.36 KB, text/plain)
2011-01-10 20:48 UTC, Jóhann B. Guðmundsson 		no flags Details
View All

Description Jóhann B. Guðmundsson 2011-01-10 20:46:31 UTC 
Description of problem:

When trying to add global signed wildcard cert for our domain to cups and login via https://fqdn-cname.domain.com:631 it always results in "Could not negotiate a supported cipher suite"

Using the unsigned server cert works just fine. 

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

cups-1.4.2-35.el6_0.1.x86_64
( gnutls-2.8.5-4.el6.x86_64 )

How reproducible:

Always 

Steps to Reproduce:
1. Get a wildcart cert from globalsign 
2. Configure server to use it 
3.
  
Actual results:

the above

Expected results:

That it works just fine as it does with https

Additional info:

Running gnutls-serv $foo or certtool $pem/key result in "Error: Base64 decoding error." which might be causing this as in cups never loads the cert hence it's unable to negotiate the "cipher suite" that is if it's using gnutls instead of openssl. ( Running gnutls-cli-debug results in "Error in %INITIAL_SAFE_RENEGOTIATION which is a bid odd I think )
Comment 1 Jóhann B. Guðmundsson 2011-01-10 20:47:07 UTC 
Created attachment 472684 [details]
/etc/cups/cupsd.conf
Comment 2 Jóhann B. Guðmundsson 2011-01-10 20:47:47 UTC 
Created attachment 472685 [details]
/var/log/cups/error.log
Comment 3 Jóhann B. Guðmundsson 2011-01-10 20:48:30 UTC 
Created attachment 472686 [details]
openssl test
Comment 4 Jóhann B. Guðmundsson 2011-01-10 20:48:58 UTC 
Created attachment 472687 [details]
gnutls test
Comment 6 Tim Waugh 2011-02-25 15:47:57 UTC 
CUPS uses gnutls, yes.  It seems like this is a gnutls issue with that certificate, as you say.

It looks like that message is coming from here:

  gnutls_certificate_allocate_credentials(credentials);
  gnutls_certificate_set_x509_key_file(*credentials, ServerCertificate,
                                       ServerKey, GNUTLS_X509_FMT_PEM);

  gnutls_init(&con->http.tls), GNUTLS_SERVER);
  gnutls_set_default_priority(con->http.tls);
  gnutls_credentials_set(con->http.tls, GNUTLS_CRD_CERTIFICATE, *credentials);
  gnutls_transport_set_ptr(con->http.tls, (gnutls_transport_ptr)HTTP(con));
  gnutls_transport_set_pull_function(con->http.tls, _httpReadGNUTLS);
  gnutls_transport_set_push_function(con->http.tls, _httpWriteGNUTLS);

  error = gnutls_handshake(con->http.tls);

  if (error != GNUTLS_E_SUCCESS)
  {
    cupsdLogMessage(CUPSD_LOG_ERROR,
                    "Unable to encrypt connection from %s - %s",
                   con->http.hostname, gnutls_strerror(error));
[...]

Changing component.
Comment 7 RHEL Program Management 2011-07-06 00:09:55 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 8 Jóhann B. Guðmundsson 2011-07-06 08:58:54 UTC 
What does that answer actually mean? 

Does it mean that this bug wont get fixed during the lifecycle of RHEL6?
Comment 9 Tomas Mraz 2011-07-11 10:04:00 UTC 
No, this means just that it will not be fixed in RHEL 6.2.
Comment 11 Suzanne Logcher 2012-02-14 23:05:59 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 12 Tomas Mraz 2012-06-13 08:57:43 UTC 
Can you please provide an example of such certificate?
Comment 13 Tomas Mraz 2012-08-08 12:17:15 UTC 
Also I suppose it might be duplicate of bug 745242 - is the private key encoded in the PKCS#8 format?
Can you try to convert it with the 'openssl rsa' command to the PKCS#1 format and see if that helps.
Comment 14 RHEL Program Management 2012-12-14 06:47:33 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 15 Tomas Mraz 2013-04-04 12:51:35 UTC 
Unfortunately we cannot fix the bug due to missing information.
Comment 16 hardihood07 2016-10-24 19:19:32 UTC 
As Tomas Mraz suggested above, I was able to get this working by converting the PKCS#8 private key to PKCS#1 private key using "openssl rsa". Thank you Tomas for valuable suggestion.
Note You need to log in before you can comment on or make changes to this bug.