Jboss 6 server is configured to support these ciphers:


But the Chrome browser reports:

The connection to this site uses a strong protocol (TLS 1.2), a strong key exchange (ECDHE_RSA), and an obsolete cipher (AES_256_CBC with HMAC-SHA1)

Should we remove all _SHA ones from the server configuration?

However, the nmap ssl scan shows, they are all A grade ciphers:

$ nmap -p 443 --script ssl-enum-ciphers.nse host-name

TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (secp160k1) - A
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (secp160k1) - A
TLS_RSA_WITH_AES_256_CBC_SHA256 (rsa 2048) - A
TLS_RSA_WITH_AES_256_CBC_SHA (rsa 2048) - A
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (secp160k1) - A
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (secp160k1) - A
TLS_RSA_WITH_AES_128_CBC_SHA256 (rsa 2048) - A
TLS_RSA_WITH_AES_128_CBC_SHA (rsa 2048) - A
  • 1
    Your question looks a little bit crappy, maybe you should invest more effort to into these formatting things, making it more attractive to the answerers. – peterh Dec 13 '16 at 10:57
  • 1
    Using capitals, punctuations, marks... formatting a text, you can learn it in hours. Understanding encryption on your current level requires months. I never understood, why you should play a... well, not very smart people. I formatted your text. Furthermore, it would be nice if it would be needed to have an actual question, currently it is unclear ("Why is it so?" "What to do?" "How to fix the problem?" "What are the possible security consequences?" - you could ask probably one of them, but the answerers don't know, what you really want to ask. You only show a problem, but not a question.) – peterh Dec 13 '16 at 11:15
  • Run qualys' ssllabs until you hit a+ – John Keates Dec 13 '16 at 11:41
  • The details I have given is enough to understand about the concern. – user133283 Dec 13 '16 at 12:09
  • It could also be about CBC mode. Since SSL/TLS uses MAC-then-encrypt, they're all not optimal. Labeling HMAC-SHA1 used as MAC as "obsolete" would be idiotic (but still believable). – CodesInChaos Dec 13 '16 at 12:23

The problem is not the SHA1 but the CBC. You need to offer an AEAD cipher like the GCM ciphers or CHACHA20-POLY1305. From the Chromium (base for Chrome) projects documentation about cipher suites:

To avoid this message, use TLS 1.2 and prioritize an ECDHE cipher suite with AES_128_GCM or CHACHA20_POLY1305. Most servers will wish to negotiate TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256.

You don't offer any of these ciphers so you get this warning. See also this answer for more details. See also the source code of Chromium, notable the function ObsoleteSSLStatusForCipherSuite in net/ssl/ssl_cipher_suite_names.c where this check is implemented.


I think your problem is in the certificate you are using. Your certificate must be done using a good cypher. That's the Chrome message you are seeing. You need to issue the certificate again using sha2 and a good cypher this time.

I recommend to you to use the online tool ssllabs to test your site. It will test your certificate, your configuration, etc. And it provide you a grade. A+ is the best. And also it recommends to you how to proceed to solve your problems. A very nice tool!

EDIT: maybe this post can help you

  • it does not look like , I did a sslscan using Kali Linux and here is info about certificate: SSL Certificate: Signature Algorithm: sha256WithRSAEncryption RSA Key Strength: 2048 – user133283 Dec 13 '16 at 11:24
  • Ok I edited my answer, take a look. – OscarAkaElvis Dec 13 '16 at 11:26

Fixed it by re-configuring the Jboss ciphers without SHA ones. Now the Chrome does not shows any security warnings.


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.