Intel + Windows 10 AES cipher fails on supported provider

[blademan]

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]

which usenet server?

[blademan]

newshosting

[sanderj]

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

[blademan]

news-us.newshosting.com

[sanderj]

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]

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]

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]

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]

Recommended next steps?

Well ... yes ... remove cipher. Does that work? If so ... why do you want to specify a cipher?