mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-25 17:05:59 +03:00
[GH-ISSUE #513] SSL/TLS trust all stopped working #435
Labels
No labels
AM+RCS
FAQ
awaiting response
backup
bespoke
bug
calendar
call log
cannot reproduce
cloudless
device-specific
documentation
dual- & multi-SIM
duplicate
feature-request
fixed in beta
good first issue
half-missing
help wanted
helpful
meta
misattribution
mms
other message sources
pull-request
question
rejuvenation
restore
schedule
security
stale
task
thanks
v1.5.1
v1.5.10
v1.5.11
v1.5.2
v1.5.3
v1.5.3
v1.5.4
v1.5.4
v1.5.5
v1.5.5
v1.5.6
v1.5.7
v1.5.8
v1.5.9
v1.6β
xoauth
~$ bounty $~
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/sms-backup-plus-jberkel#435
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @btittelbach on GitHub (Dec 27, 2014).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/513
Since update to version 1.5.6
Despite the obvious security issue where noone should use this option, the inability to add certificates to stock android makes this option a necessity in some cases on some peoples phones.
@DaHermit commented on GitHub (Dec 27, 2014):
Same problem here on my old s2. Prior to the last update tls was working fine.
Having to set no encryption to get things to work at the moment.
@jberkel commented on GitHub (Dec 28, 2014):
looks like k9 upstream removed the ability to trust all certs (in
github.com/k9mail/k-9@daea7f1ecd)@jberkel commented on GitHub (Dec 28, 2014):
can you guys try https://github.com/jberkel/sms-backup-plus/releases/tag/1.5.7-BETA2 ? should work there.
@DaHermit commented on GitHub (Dec 29, 2014):
Appears to work with ssl/tsl all on port 143,but only ssl all on port 993. Not sure if that's a failing of my email server thougg,I've not been able to access my server logs to check.
Thanks for the quick fix!
@jberkel commented on GitHub (Dec 29, 2014):
i'm closing this for now, please reopen if problem persists