Bug 1161808 - [RFE] method to get the SSL version info from the client regardless of the handshake result
Summary: [RFE] method to get the SSL version info from the client regardless of the ha...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: nss
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: nss-nspr-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-07 23:24 UTC by Noriko Hosoi
Modified: 2019-05-17 08:35 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-17 08:35:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Noriko Hosoi 2014-11-07 23:24:39 UTC
Description of problem:
When an SSL handshake was successful, then we could get the SSL version info from channelInfo.protocolVersion that slapd_ssl_getChannelInfo provides, e.g.:
[..] conn=2 TLS1.2 128-bit AES-GCM

We'd like to get the client's SSL version for the trouble shooting purpose, for instance, SSL_ERROR_PROTOCOL_VERSION_ALERT is returned.  Currently, the error message is not intuitive for new users.
[..] conn=1 op=-1 fd=64 closed - Cannot communicate securely with peer: no common encryption algorithm(s).

Comment 1 Fedora End Of Life 2015-05-29 13:15:03 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2015-06-29 23:12:29 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 3 Kamil Dudka 2015-06-30 06:36:30 UTC
Still an issue in Fedora rawhide.

Comment 4 Fedora Admin XMLRPC Client 2016-08-15 15:52:42 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 5 Kai Engert (:kaie) (inactive account) 2017-07-11 13:38:30 UTC
If this is still required, it needs to be requested upstream.

Comment 6 Daiki Ueno 2019-05-17 08:35:51 UTC
(In reply to Noriko Hosoi from comment #0)
> Description of problem:
> When an SSL handshake was successful, then we could get the SSL version info
> from channelInfo.protocolVersion that slapd_ssl_getChannelInfo provides,
> e.g.:
> [..] conn=2 TLS1.2 128-bit AES-GCM
> 
> We'd like to get the client's SSL version for the trouble shooting purpose,
> for instance, SSL_ERROR_PROTOCOL_VERSION_ALERT is returned.  Currently, the
> error message is not intuitive for new users.
> [..] conn=1 op=-1 fd=64 closed - Cannot communicate securely with peer: no
> common encryption algorithm(s).

How would it be possible to get the client's version, when it is not yet negotiated?
Or do you mean to know which version the client sent as ClientHello.client_version?  In that case it should be the same as the highest version returned from SSL_VersionRangeGet().


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