Intel + Windows 10 AES cipher fails on supported provider

Get help, report and discuss bugs.
blademan
Posts: 8
Joined: 29 Jan 2018, 20:40

Intel + Windows 10 AES cipher fails on supported provider

Post by blademan » 29 Nov 2020, 23:18

Reading this article: https://nzbget.net/choosing-cipher, my Intel cpu supports AES and this old post shows my provider supports AES: https://www.reddit.com/r/usenet/comment ... er_suites/. When I use

Code: Select all

Server1.Cipher=AES256-SHA
Testing the connection, I get:

Code: Select all

Could not select cipher for TLS: error:1410F0B9:SSL routines:SSL_set_cipher_list:no cipher match
I didn't verify directly on Windows, so maybe they don't use AES anymore.

sanderj
Posts: 178
Joined: 10 Feb 2014, 21:46

Re: Intel + Windows 10 AES cipher fails on supported provider

Post by sanderj » 30 Nov 2020, 08:34

which usenet server?

blademan
Posts: 8
Joined: 29 Jan 2018, 20:40

Re: Intel + Windows 10 AES cipher fails on supported provider

Post by blademan » 30 Nov 2020, 19:27

newshosting

sanderj
Posts: 178
Joined: 10 Feb 2014, 21:46

Re: Intel + Windows 10 AES cipher fails on supported provider

Post by sanderj » 30 Nov 2020, 20:27

which usenet server exaclty? So: full name ("FQDN") you use?

blademan
Posts: 8
Joined: 29 Jan 2018, 20:40

Re: Intel + Windows 10 AES cipher fails on supported provider

Post by blademan » 30 Nov 2020, 22:05

;) news-us.newshosting.com

sanderj
Posts: 178
Joined: 10 Feb 2014, 21:46

Re: Intel + Windows 10 AES cipher fails on supported provider

Post by sanderj » 01 Dec 2020, 14:00

I tested news-us.newshosting.com with nzbget on my Win10 without and with cipher ... no problem.

I tested news-us.newshosting.com with testssl.sh ... no problem

So ... I can't reproduce

blademan
Posts: 8
Joined: 29 Jan 2018, 20:40

Re: Intel + Windows 10 AES cipher fails on supported provider

Post by blademan » 01 Dec 2020, 20:52

Code: Select all

Server1.Cipher=AES256-SHA
worked for news-us.newshosting.com with NZBGet on Windows for you?
Maybe my string is incorrect, according to the note in the setttings config: "NOTE: You may get a TLS handshake error if the news server does not support the chosen cipher. You can also get an error "Could not select cipher for TLS" if the cipher string is not valid."

sanderj
Posts: 178
Joined: 10 Feb 2014, 21:46

Re: Intel + Windows 10 AES cipher fails on supported provider

Post by sanderj » 01 Dec 2020, 20:58

blademan wrote:
01 Dec 2020, 20:52

Code: Select all

Server1.Cipher=AES256-SHA
worked for news-us.newshosting.com with NZBGet on Windows for you?
Maybe my string is incorrect, according to the note in the setttings config: "NOTE: You may get a TLS handshake error if the news server does not support the chosen cipher. You can also get an error "Could not select cipher for TLS" if the cipher string is not valid."
Yes. By filling it out in the GUI (FWIW)

blademan
Posts: 8
Joined: 29 Jan 2018, 20:40

Re: Intel + Windows 10 AES cipher fails on supported provider

Post by blademan » 01 Dec 2020, 21:13

Curious. I'm running v 21.0. Just tried reinstalling from a fresh download, same error. I don't see a LogFile. Recommended next steps?

sanderj
Posts: 178
Joined: 10 Feb 2014, 21:46

Re: Intel + Windows 10 AES cipher fails on supported provider

Post by sanderj » 01 Dec 2020, 21:39

blademan wrote:
01 Dec 2020, 21:13
Recommended next steps?
Well ... yes ... remove cipher. Does that work? If so ... why do you want to specify a cipher?

Post Reply

Who is online

Users browsing this forum: No registered users and 4 guests