This bug is showing ssl issues for multiple urls, it appears like some are working (for me at least) and one does not.
It looks like this is a issue with our usage of the webkit/glib-http component that has a less robust ssl implementation
than e.g. firefox.
I get:
$ gnutls-cli --x509cafile /etc/ssl/certs/ca-certificates.crt -p 443 verifiedbyvisa.barclays.co.uk
...
- Peer's certificate is trusted
But also:
$ gnutls-cli --verbose --x509cafile /etc/ssl/certs/ca-certificates.crt -p 443 secure2.arcot.com
Processed 160 CA certificate(s).
Resolving 'secure2.arcot.com'...
Connecting to '216.136.151.43:443'...
*** Fatal error: A TLS fatal alert has been received.
*** Received alert [47]: Illegal parameter
*** Handshake has failed
GnuTLS error: A TLS fatal alert has been received.
Thanks for your bugreport.
This bug is showing ssl issues for multiple urls, it appears like some are working (for me at least) and one does not.
It looks like this is a issue with our usage of the webkit/glib-http component that has a less robust ssl implementation
than e.g. firefox.
I get: certs/ca- certificates. crt -p 443 verifiedbyvisa. barclays. co.uk
$ gnutls-cli --x509cafile /etc/ssl/
...
- Peer's certificate is trusted
$ gnutls-cli --x509cafile /etc/ssl/ certs/ca- certificates. crt -p 443 www.securesuite.net
..
- Peer's certificate is trusted
But also: certs/ca- certificates. crt -p 443 secure2.arcot.com arcot.com' ... 151.43: 443'...
$ gnutls-cli --verbose --x509cafile /etc/ssl/
Processed 160 CA certificate(s).
Resolving 'secure2.
Connecting to '216.136.
*** Fatal error: A TLS fatal alert has been received.
*** Received alert [47]: Illegal parameter
*** Handshake has failed
GnuTLS error: A TLS fatal alert has been received.