You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Stunnel supplies an ARM openssl binary, could this work/be added?
I am aware this may very well be a Google/Android issue with boringssl, but we all know if we waited for a fix we'd be at android v291... It looks to me Stunnel had this issue and supplies an openssl ARM binary (https://www.stunnel.org/downloads/stunnel-latest-android.zip)
Tests done from windows/openssl:
POP (does not work in k9, error:10000410)
Windows-test: openssl s_client -connect mail.anon.nl:995
SSL-Session:
Protocol : TLSv1.2
Cipher : DHE-RSA-AES128-SHA
Verify return code: 19 (self signed certificate in certificate chain)
+OK Dovecot ready.
IMAP (does not work in k9, error:10000410)
Windows-test: openssl s_client -connect mail.anon.nl:993
SSL-Session:
Protocol : TLSv1.2
Cipher : DHE-RSA-AES128-SHA
Verify return code: 19 (self signed certificate in certificate chain)
OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
SMTP (StartTLS in k9 for smtp works!)
Windows-test: openssl s_client -starttls smtp -connect mail.anon.nl:587
SSL-Session:
Protocol : TLSv1.2
Cipher : ECDHE-RSA-AES256-GCM-SHA384
Verify return code: 19 (self signed certificate in certificate chain)
250 DSN
quit
221 2.0.0 Bye
The text was updated successfully, but these errors were encountered:
When I run K-9 6.804 on Android 14 on my Samsung Tab S8 however, it works fine. Same IMAP server with same configuration options. Samsung may not have updated Boringssl on that device to the impacted version.
Checklist
App version
Latest 6804 from git (here)
Where did you get the app from?
Other
Android version
14 (security update 1-sep-2024)
Device model
s24 samsung
Steps to reproduce
Any account with pop3/imap.
Connect to Dovecot with ssl/tls.
Expected behavior
Success connect.
Actual behavior
See screen shot about boringssl error. (Steps to reproduce)
Logs
error:10000410:ssl routines:openssl_internal:sslv3_alert_handshake_failure
(boringssl android 14) see Steps to reproduce.
Dovecot blamed but looks like android problem.
https://www.aqua-mail.com/forum/index.php?PHPSESSID=b54gea24qmsouh1qleccqgp9m4&topic=6824.msg41212#msg41212
Stunnel supplies an ARM openssl binary, could this work/be added?
I am aware this may very well be a Google/Android issue with boringssl, but we all know if we waited for a fix we'd be at android v291... It looks to me Stunnel had this issue and supplies an openssl ARM binary (https://www.stunnel.org/downloads/stunnel-latest-android.zip)
Tests done from windows/openssl:
POP (does not work in k9, error:10000410)
Windows-test: openssl s_client -connect mail.anon.nl:995
SSL-Session:
Protocol : TLSv1.2
Cipher : DHE-RSA-AES128-SHA
Verify return code: 19 (self signed certificate in certificate chain)
+OK Dovecot ready.
IMAP (does not work in k9, error:10000410)
Windows-test: openssl s_client -connect mail.anon.nl:993
SSL-Session:
Protocol : TLSv1.2
Cipher : DHE-RSA-AES128-SHA
Verify return code: 19 (self signed certificate in certificate chain)
SMTP (StartTLS in k9 for smtp works!)
Windows-test: openssl s_client -starttls smtp -connect mail.anon.nl:587
SSL-Session:
Protocol : TLSv1.2
Cipher : ECDHE-RSA-AES256-GCM-SHA384
Verify return code: 19 (self signed certificate in certificate chain)
250 DSN
quit
221 2.0.0 Bye
The text was updated successfully, but these errors were encountered: