Skip to main content

Apache SNI config to send handshake alert: unrecognized_name

itemprop="text">

I am trying to achieve what some years
ago was a problem due to miss configured servers that caused




"handshake alert:
unrecognized_name"




when a SNI
enabled client ( for Java 1.7 or bigger clients) would send during the handshake the






Extension server_name, server_name: [type=host_name (0),

value=hostname]




for
example this question was how to avoid this
:



href="https://stackoverflow.com/questions/7615645/ssl-handshake-alert-unrecognized-name-error-since-upgrade-to-java-1-7-0">https://stackoverflow.com/questions/7615645/ssl-handshake-alert-unrecognized-name-error-since-upgrade-to-java-1-7-0.



My
apache version is 2.4.33, on Ubuntu 16.04.

and the config file that
I use looks like this :



            ssl_module>
Listen
8095


mod_gnutls.c>
Listen
8095



ServerName
localhost


_default_:8095>
ServerName
value.that.does.not.match.the.cn.in.certificate
ServerAlias
value.that.does.not.match.the.cn.in.certificate
DocumentRoot
/var/www/html

SSLEngine on
SSLCertificateFile
/path_to_certificates/selfsigned.cert

SSLCertificateKeyFile
/path_to_certificates/selfsigned.key
SSLVerifyClient none

SSLVerifyDepth 10





I
have done some research and I used the following command to check that SNI is enabled
for the hostname that I expose through apache
:



openssl s_client -servername
hostanametocheck -tlsextdebug -connect hostanametocheck:8095 2>/dev/null | grep
"server
name"



for
which the result is :



TLS server
extension "server name" (id=0),
len=0


which from what
I've read it is an indicator that apache sends this extension during the handshake which
in case of Java clients > 1.7 would end up as an exception during the
handshake.



I would expect that my Java client
(1.8) would receive that alert and the handshake will fail, but as I landed here it does
not. I already spend a quite good amount of time trying to figure out this but looks
like it is beyond my networking and linux knowledge.




Btw, I am running the apache on my
dev machine, therefore the 8095 port instead of 443. I mapped the hostname to
localhost.
SNI is enabled on the client side as I can see in the handshake
logs that the extension is sent



Extension server_name,
server_name: [type=host_name (0),
value=hostname.that.does.not.match.cn.in.certificate.com]


Your
help would be really appreciated!


class="post-text" itemprop="text">
class="normal">Answer



I had
successfully caused the error , with Apache 2.2.22 ( but some old version, unpatched )
as it looks like they started removing that alert from being sent starting with 2.4.1
and some versions back. More on the following
link.




href="https://bz.apache.org/bugzilla/show_bug.cgi?id=56241" rel="nofollow
noreferrer">https://bz.apache.org/bugzilla/show_bug.cgi?id=56241



Comments

Popular posts from this blog

iLO 3 Firmware Update (HP Proliant DL380 G7)

The iLO web interface allows me to upload a .bin file ( Obtain the firmware image (.bin) file from the Online ROM Flash Component for HP Integrated Lights-Out. ) The iLO web interface redirects me to a page in the HP support website ( http://www.hp.com/go/iLO ) where I am supposed to find this .bin firmware, but no luck for me. The support website is a mess and very slow, badly categorized and generally unusable. Where can I find this .bin file? The only related link I am able to find asks me about my server operating system (what does this have to do with the iLO?!) and lets me download an .iso with no .bin file And also a related question: what is the latest iLO 3 version? (for Proliant DL380 G7, not sure if the iLO is tied to the server model)

linux - How can I get my mediawiki to stop thinking I have cookies disabled?

I've searched half a day for how to resolve this issue, and can't figure it out. Shortly after I made my wiki a simple private wiki according to the instructions at Mediawiki's website, it started giving me this weird login error message: Wiki uses cookies to log in users. You have cookies disabled. Please enable them and try again. If I remove those private wiki settings, the error disappears, even if I try logging in. But I need it to be a private wiki for only my team. So what do I do? Here's what I've done so far. Just to be safe, after ever change, I try rebooting Apache using: sudo /etc/init.d/apache2 restart In my php.ini file, I have the following set: session.save_path = "/var/lib/php5" session.cookie_secure = secure session.cookie_path = /tmp session.cookie_domain = my server's internal URL (should I even set this? this field was blank before, but not commented out) session.referer_check = Off I ran the following to ensure that the fold...

linux - Awstats - outputting stats for merged Access_logs only producing stats for one server's log

I've been attempting this for two weeks and I've accessed countless number of sites on this issue and it seems there is something I'm not getting here and I'm at a lost. I manged to figure out how to merge logs from two servers together. (Taking care to only merge the matching domains together) The logs from the first server span from 15 Dec 2012 to 8 April 2014 The logs from the second server span from 2 Mar 2014 to 9 April 2014 I was able to successfully merge them using the logresolvemerge.pl script simply enermerating each log and > out_putting_it_to_file Looking at the two logs from each server the format seems exactly the same. The problem I'm having is producing the stats page for the logs. The command I've boiled it down to is /usr/share/awstats/tools/awstats_buildstaticpages.pl -configdir=/home/User/Documents/conf/ -config=example.com awstatsprog=/usr/share/awstats/wwwroot/cgi-bin/awstats.pl dir=/home/User/Documents/parced -month=all -year=all...