Changes between Initial Version and Version 1 of Ticket #38055
- Timestamp:
- Feb 14, 2013, 12:03:37 AM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #38055
- Property Cc mww@… cal@… egall@… larryv@… added
- Property Keywords gmail alpine openssl removed
- Property Port openssl added
-
Ticket #38055 – Description
initial v1 3 3 After a recent update of alpine and of openssl, alpine now comes 4 4 back with the following on launch going to my inbox: 5 6 {{{ 5 7 There was an SSL/TLS failure for the server 6 8 imap.gmail.com … … 17 19 imap.gmail.com/notls 18 20 Type RETURN to continue. 21 }}} 19 22 20 23 A co-worker suggested trying the following command: 24 25 {{{ 21 26 $ openssl s_client -connect imap.gmail.com:993 22 27 CONNECTED(00000003) … … 65 70 Verify return code: 20 (unable to get local issuer certificate) 66 71 --- 72 }}} 73 67 74 After seeing this ouput, he remarked: 68 I think alpine uses the same cert store as openssl. But the point69 not on curve error is more interesting. More likely, the new openssl70 supports ECC ciphers out of the box, and there's some incompatibility71 with Google's support for it. You might want to see if Alpine supports72 configuration of the acceptable ciphers (like the Apache SSLCiphers73 or SSH's Cipher option). Then set it to remove the ECC ciphers and74 see if it's happier.75 -- 75 I think alpine uses the same cert store as openssl. But the point 76 not on curve error is more interesting. More likely, the new openssl 77 supports ECC ciphers out of the box, and there's some incompatibility 78 with Google's support for it. You might want to see if Alpine supports 79 configuration of the acceptable ciphers (like the Apache SSLCiphers 80 or SSH's Cipher option). Then set it to remove the ECC ciphers and 81 see if it's happier. 82 76 83 I didn't see where to configure acceptable ciphers in alpine and not 77 84 sure if that needs to be configured in openssl.