Closed Bug 1146281 Opened 5 years ago Closed 4 years ago

ebank.db-pbc.pl is RC4 only

Categories

(Web Compatibility :: Desktop, defect)

defect
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mlegof, Unassigned)

References

()

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101 Firefox/35.0
Build ID: 20141229214612

Steps to reproduce:

the latest version of Firefox, the certificate page (https://ebank.db-pbc.pl/auth/login.jsp) does not appear. Grey warning triangle warns of Preferably page. With other browsers and earlier versions everything works ok


Actual results:

2015-03-12 Bank exchanged for a new certificate but the problem is still present in the latest versions of Firefox browser. I checked all the possible settings for certificates. I contacted the bank.


Expected results:

Firefox fix needed to accept certified bank as in previous versions. The site should to be verifiable. Fraudsters can use a certificate that does not act on firefox> 36
The server is RC4 only:
https://www.ssllabs.com/ssltest/analyze.html?d=ebank.db-pbc.pl

Cipher Suites (sorted by strength; the server has no preference)
TLS_RSA_WITH_RC4_128_SHA (0x5) 

In FF39, you'll see:
An error occurred during a connection to ebank.db-pbc.pl. Cannot communicate securely with peer: no common encryption algorithm(s). (Error code: ssl_error_no_cypher_overlap)
Status: UNCONFIRMED → NEW
Component: Untriaged → Desktop
Ever confirmed: true
OS: Windows 7 → All
Product: Firefox → Tech Evangelism
Hardware: x86_64 → All
Summary: the problem with the display of a bank certificate Deutche Bank → ebank.db-pbc.pl is RC4 only
Version: 36 Branch → Trunk
Thanks Loic!
If you want, you can contact their support by e-mail and redirect them to this bug report. Devs can answer them if they have some questions.
Yesterday I gave your answer to the bank. We'll see what they have to answer to me : -)
I'll let you know.
Fixed.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Product: Tech Evangelism → Web Compatibility
You need to log in before you can comment on or make changes to this bug.