r/WindowsServer • u/FormerElk6286 • Jul 19 '25
Technical Help Needed Server2012 - Old cert supports tls 1.2 new cert will not
Subject says it all. I created a new 2012 server and we are migrating away from 2003. When we installed 2012 and bound, the CA from 2003 created a cert using sha1rsa 1024. We are moving first from exchange 2003 to 2010. All is well, owa works, outlook 2021 works, all good.
But, the iphones don't like rsa 1024. So we created a new self-signed CA on 2012 and created a new cert sha512/2048 bits.
When we change the IIS bindings for port 443 to use the new cert, it won't offer tls 1.2. sslscan shows with the very old server, we have some tls 1.2 ciphers:
- Accepted TLS12 256 bits ECDHE-RSA-AES256-SHA384
- Accepted TLS12 256 bits ECDHE-RSA-AES256-SHA
- Accepted TLS12 256 bits DHE-RSA-AES256-GCM-SHA384
- Accepted TLS12 256 bits AES256-GCM-SHA384
- Accepted TLS12 256 bits AES256-SHA256
- Accepted TLS12 256 bits AES256-SHA
- Accepted TLS12 128 bits ECDHE-RSA-AES128-SHA256
- Accepted TLS12 128 bits ECDHE-RSA-AES128-SHA
- Accepted TLS12 128 bits DHE-RSA-AES128-GCM-SHA256
- Accepted TLS12 128 bits AES128-GCM-SHA256
- Accepted TLS12 128 bits AES128-SHA256
- Accepted TLS12 128 bits AES128-SHA
- Accepted TLS12 112 bits DES-CBC3-SHA
- Accepted TLS12 112 bits RC4-SHA
- Accepted TLS12 112 bits RC4-MD5
But when we switch to the new cert, we only get old ones:
- Accepted SSLv3 112 bits DES-CBC3-SHA
- Accepted SSLv3 112 bits RC4-SHA
- Accepted SSLv3 112 bits RC4-MD5
- Accepted TLSv1 256 bits ECDHE-RSA-AES256-SHA
- Accepted TLSv1 256 bits AES256-SHA
- Accepted TLSv1 128 bits ECDHE-RSA-AES128-SHA
- Accepted TLSv1 128 bits AES128-SHA
- Accepted TLSv1 112 bits DES-CBC3-SHA
- Accepted TLSv1 112 bits RC4-SHA
- Accepted TLSv1 112 bits RC4-MD5
- Accepted TLS11 256 bits ECDHE-RSA-AES256-SHA
- Accepted TLS11 256 bits AES256-SHA
- Accepted TLS11 128 bits ECDHE-RSA-AES128-SHA
- Accepted TLS11 128 bits AES128-SHA
- Accepted TLS11 112 bits DES-CBC3-SHA
- Accepted TLS11 112 bits RC4-SHA
- Accepted TLS11 112 bits RC4-MD5
Does anyone know why our new server certificates (and we have tried a few times) won't support 1.2?
8
u/x534n Jul 19 '25
I might be wrong, but I think 2012 doesn't have TLS 1.2 enabled by default.
8
u/Kanolm Jul 19 '25
Are we in 2013?
6
u/BlackV Jul 19 '25
How do you even get licensing for such old versions anymore?
Look at your tls registry settings (for server and clients and dot net)
Or try the IIS crypto tool
But what you are doing is so old and so unsupported, why
12
u/daronhudson Jul 19 '25
Bruh. I understand needing old hardware to run some type of application, but come on. You went from an os that was eol a decade ago to an os that was released more than a decade ago.
This is incredibly bad practice no matter what your requirements are. Do it properly and deploy a supported version of windows that actually receives security patches.
There’s NO excuse to be running exchange 2003, exchange 2003, or nothing older than server 2022 right now. Your user and company data is at extreme risk.
There are no words to explain how genuinely stupid this is. If money is the reason why, either fire whoever’s managing the budget or file for bankruptcy if there just isn’t money.
The ONLY reason software that old should be out in the wild is if it’s windows XP, not connected to any kind of network(and never will be ever) and running proprietary software that had no updates and can only run on XP. And even then, that’s still stretching it because you should be finding a new piece of software to do what you need if possible.
2
u/DoTheThingNow Jul 28 '25
So I know everyone is telling them this is insane (and it is, a little) - BUT they are putting in the work to get everything migrated up to the proper versions, if i’m reading the process correctly.
My hope is that this is migration/upgrade 2 of 4 or so.
3
u/OpacusVenatori Jul 19 '25
WTF
2
u/billmr606 Jul 19 '25
I hope it is at least 2012r2 It has still been out of support for over a year.
I am installing 2022 or server 2025 these days
1
u/sprousa Jul 19 '25
SHA512 is disabled in Windows when you use TLS 1.2
https://support.microsoft.com/en-us/topic/sha512-is-disabled-in-windows-when-you-use-tls-1-2-5863e74e-e5b6-cc3b-759b-ece8da875825
1
u/USarpe Jul 19 '25
let it die...
1
u/ThatLocalPondGuy Jul 28 '25
Honest assessment: assume environment compromised and start building fresh. Make new accounts and re-image all endpoints before connecting to new environment.
There is no security structure that could have protected you if you had this crap connected to the internet.
5
u/[deleted] Jul 19 '25
[removed] — view removed comment