Bug 1366011 - SSL_GetNegotiatedHostInfo always returns NULL
Summary: SSL_GetNegotiatedHostInfo always returns NULL
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: nss
Version: 26
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: 2016-08-10 17:59 UTC by Rob Crittenden
Modified: 2018-05-29 11:49 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-29 11:49:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Rob Crittenden 2016-08-10 17:59:51 UTC
Description of problem:

SSL_GetNegotiatedHostInfo() always returns NULL which breaks SNI support in mod_nss.

ssltap confirms that the SNI name is being sent:

            extensions[95] = {
              extension type server_name, length [21] = {
   0: 00 13 00 00  10 77 77 77  31 2e 65 78  61 6d 70 6c  | .....www1.exampl
  10: 65 2e 63 6f  6d                                     | e.com
              }

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

nss-3.25.0-1.0.fc23.x86_64
mod_nss-1.0.12-4.fc23.x86_64 (also affects 1.0.14)

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

Comment 2 Kai Engert (:kaie) (inactive account) 2016-10-18 14:31:52 UTC
Rob, is this a regression? Has it ever worked before, and if yes, what's the last version you know that's good?

Comment 3 Rob Crittenden 2016-10-18 15:00:29 UTC
I'm not sure. I'm seeing the same behavior in nss-3.26.0-1.0.fc23.x86_64 though.

It is reproducible in a test setup (though it isn't being explicitly tested). To reproduce:

- pull the mod_nss source (git://git.fedorahosted.org/mod_nss.git)
- Add to /etc/hosts
   <your_ip> www1.example.com
- run make all check (the tests pass 100% for me in F23)
- cd test/work/httpd
- ./start
- curl -kv https://www1.example.com:8000

It will fail with a 403 and the message:

Reason: The client software did not provide a hostname using Server Name Indication (SNI), which is required to access this server.

The source file is nss_engine_kernel.c. The failure happens in nss_hook_ReadReq().

If SNI is enabled in the VH hostinfo is requested. It is always NULL in this case.

Let me note that this test is a bit bogus since the VH for port 8000 will be configured for the hostname itself but this shouldn't preclude NSS from collecting the SNI hostname. I think the request should still ultimately fail but it should fail due to a bad hostname in the request, not for the NSS call returning NULL.

Comment 4 Fedora End Of Life 2016-11-25 09:30:00 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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 5 Fedora End Of Life 2017-02-28 10:05:06 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

Comment 6 Fedora End Of Life 2018-05-03 08:36:31 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 '26'.

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 26 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 7 Fedora End Of Life 2018-05-29 11:49:41 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.


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