Bug 1333521

Summary: Provide ability to set the expected server name in gnutls-serv utility [rhel-6]
Product: Red Hat Enterprise Linux 6 Reporter: Alicja Kario <hkario>
Component: gnutlsAssignee: Nikos Mavrogiannopoulos <nmavrogi>
Status: CLOSED ERRATA QA Contact: Alicja Kario <hkario>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.8CC: nmavrogi, szidek
Target Milestone: rcKeywords: Patch
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gnutls-2.12.23-15.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1444792 (view as bug list) Environment:
Last Closed: 2017-03-21 09:03:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1339222, 1343211, 1444792    
Attachments:
Description Flags
add support for setting hostname on server side
none
[V2] add support for setting hostname on server side nmavrogi: review+

Description Alicja Kario 2016-05-05 17:55:08 UTC 
Created attachment 1154331 [details]
add support for setting hostname on server side

Description of problem:
gnutls-serv utility can't indicate on protocol level whether the name provided by client matched the value expected by server.

Version-Release number of selected component (if applicable):
gnutls-2.8.5-19.el6_7.x86_64

How reproducible:
always

Steps to Reproduce:
1. gnutls-serv --sni-hostname localhost

Actual results:
unrecognised option: --sni-hostname

Expected results:
server started, sending TLS alerts when hostname did not match

Additional info:
https://gitlab.com/gnutls/gnutls/merge_requests/10

Needed to perform tests related to server name indication extension.
Comment 1 Alicja Kario 2016-05-11 13:02:15 UTC 
Created attachment 1156135 [details]
[V2] add support for setting hostname on server side

update the code to current upstream version, remove debugging aids
Comment 12 errata-xmlrpc 2017-03-21 09:03:54 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2017-0574.html