PiRSquared17 / ttrss-reader-fork

Automatically exported from code.google.com/p/ttrss-reader-fork
0 stars 1 forks source link

Https TLS only strange behaviour #233

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Try to connect with https
2. Server-side allow only TLS because of SNI
3. use non-self-signed certicate

What is the expected output? What do you see instead?
Normal usage like with http. Instead every connect to server i get the message 
that the connection failed with javax.net.ssl.SSLProtocolException: Handshake 
failed. But in the serverlogs i see the connection established on https.

What version of the product are you using? On what operating system? And
what server-version is your TTRSS-server running?
App: 1.73
Ttrss: 1.10

Please provide any additional information below.
If you want, i will try to upload a screenshot, but at the moment Chrome says 
it can't open it.

Original issue reported on code.google.com by pinc...@googlemail.com on 4 Feb 2014 at 1:07

GoogleCodeExporter commented 9 years ago
It seems tt-rss doesn't play well with tlsv1.1 or tlsv1.2 yet. Does your server 
have tlsv1 disabled for some reason?

Original comment by MathStuf@gmail.com on 21 Oct 2014 at 4:01

GoogleCodeExporter commented 9 years ago
Can you please try the attached build and report back if it works (and also if 
it doesn't of course)? And please check if you have the "old connector" method 
enabled in the preferences since this deprecated method is not affected by the 
new changes.

I changed several aspects of the SSL connections like disabling SSLv3 for 
security reasons and trying to add support for TLSv1.2 and 1.3...

It works with my own server but I can't create several testing servers with 
different SSL configurations easily.

Original comment by nils.braden on 21 Oct 2014 at 8:52

Attachments:

GoogleCodeExporter commented 9 years ago
Doesnt work for me. Using a nginx server. If you need the config, contact me.

Original comment by ott.micha@gmail.com on 29 Oct 2014 at 3:51

GoogleCodeExporter commented 9 years ago
Could not answer your mail, but here it is: https://rss.xfragger.de

E-Mail was mine problem, have to fix it first 

Original comment by ott.micha@gmail.com on 30 Oct 2014 at 10:50

GoogleCodeExporter commented 9 years ago
I see a similar situation here wjth my server,an Apache 2 with only TLS v1.1 
and TLS 1.2 enabled. The app is not able to connect. 

Original comment by reiner.b...@gmail.com on 6 Nov 2014 at 3:46