Closed Bug 581147 Opened 15 years ago Closed 12 years ago

e-fibank.bg - "Secure Connection Failed: Renegotiation is not allowed on this SSL socket"

Categories

(Tech Evangelism Graveyard :: Bulgarian, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: jruderman, Unassigned)

References

()

Details

(Whiteboard: [input])

[From Firefox Input] https://e-fibank.bg/ fails to load. Firefox says "Secure Connection Failed: Renegotiation is not allowed on this SSL socket". Am I correct to assume this is a problem with the web site?
Whiteboard: [input]
That error message means the SSL handshake failed with the NSS error code SSL_ERROR_RENEGOTIATION_NOT_ALLOWED. The user may have changed some Firefox preferences that disabled SSL renegotiation, or the user may be using a computer whose system NSS library is version 3.12.5, in which SSL renegotiation is disabled by default.
wtc, I get this message when I load https://e-fibank.bg/ using a Firefox trunk build, even with a new profile.
I found that the default value of the preference security.ssl.allow_unrestricted_renego_everywhere__temporarily_available_pref changed from "true" to "false" in Firefox 4.0 pre-release. Until the site is upgraded to support the TLS renegotiation_info extension, please tell the user to add the host name e-fibank.bg to the whitelist in the preference security.ssl.renego_unrestricted_hosts.
I confirm this bug also for the french tax site. I added the host cfspart.impots.gouv.fr in the preference security.ssl.renego_unrestricted_hosts, and everything works. Nevertheless, I think a popup should be displayed to inform the user.
(In reply to comment #4) > I confirm this bug also for the french tax site. I added the host > cfspart.impots.gouv.fr in the preference > security.ssl.renego_unrestricted_hosts, and everything works. You'll need to file a new bug report for that site. This bug report is a tech evangelism bug for e-fibank.bg, where we've determined that the problem is with the web site. > Nevertheless, I think a popup should be displayed to inform the user. There's a content-area error message; I don't see a reason to show a popup.
Assignee: other → bulgarian
Component: Other → Bulgarian
QA Contact: other → bulgarian
Problem not found Mozilla/5.0 (X11; Linux i686; rv:23.0) Gecko/20100101 Firefox/23.0
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.