Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[renluop]

[Chrysalis]

why havent you named the bank?

[broadstairs]

Well I would not try to get round that error, I'd call them first. If a bank cannot negotiate a secure connection then dont trust them until they do.

Stuart

[renluop]

@ Chrysalis because my financial affairs like yours are confidential.
@ broadstairs I did say that

Of course I shall contact by phone,

to make thread not just about the specifics.

[Chrysalis]

Well I Cant diagnose if you not even willing to name the bank.

[broadstairs]

I realise you were going to phone them but making the point that it's their problem not one which you should be trying to circumvent. I trust the site you were trying was not one contained in an email.

Stuart

[renluop]

Twas not, sire!

[niemand]

Try without Avast proxying your SSL session. It may not support the TLS handshake going on. Either parameters or extensions could break it.

[renluop]

Do you mean, turn off Avast?

[niemand]

Yes. That or try via something that doesn't have Avast.

If I recall correctly Avast behaves as a proxy - it connects to the site on your behalf then re-encrypts for delivery to you, providing its own certificate to your browser and completing cryptographic exchange with it. If the Avast proxy can't complete the connection to the remote site properly it may end up causing this error.

I've seen things like this on SSL/TLS proxies where there's a problem with the initial handshake and it's too late to bail from proxying the session so it just passes the alert to your browser.

[renluop]

Interesting! Thanks.
TBH I'm getting fed up with Avast's pestering me with pop ups telling things like your location is showing, trying to get me to upgrade. May be I'll ditch for another free AV.

[Chrysalis]

Ignition's idea is excellent, a/v like avast and nod32 proxy SSL/TLS which breaks the standards for SSL/TLS (non interception) and can break stuff when they get things wrong, a big problem they have is they often cannot keep up with the rapid development of web TLS technologies.

[niemand]

Ignition's idea is excellent, a/v like avast and nod32 proxy SSL/TLS.....

Thanks! I should do that kind of thing for a living. Oh wait... 

[Chrysalis]

Well I asked for the bank so I could check if their website is broken for TLS, then that would have determined if a local PC/LAN problem or a website problem.

[Ronski]

I use Avast, both on my phone and PC and have not noticed any banking issues.