225cca4566
provide extra 'network is unreachable' account state
2017-08-02 18:58:51 +02:00
4ff3c36ed9
updated build tools and some library versions
2017-08-02 17:42:21 +02:00
768eadde36
use random string generator instead of BigInteger in DigestMd5
2017-08-01 12:27:26 +02:00
82c5924434
display messages that only contain emoji slightly larger
2017-07-30 22:04:58 +02:00
e11277c70f
use base64 instead of base36 when creating random strings
2017-07-30 11:39:47 +02:00
01b207d44d
avoid empty strings when figuring out display name
2017-07-30 11:39:16 +02:00
d3194172c5
update dependencies
2017-07-29 13:50:59 +02:00
f5da4791ad
avoid unnecessary roster sync in OMEMO code. fixed startup performance regression
2017-07-29 13:50:32 +02:00
837c212931
refresh omemo activity after failing to fetch keys due to lack of ids
2017-07-28 18:37:07 +02:00
ad601e47c8
fixed roster items w/o subscription (request) not being shown
2017-07-28 18:34:55 +02:00
ea6289c02e
pulled translations from transifex
2017-07-26 13:23:40 +02:00
d6e51288c3
Merge pull request #2564 from yushijinhun/fix-decryption-blocked
...
Give up PGP decryption when intent is cancelled
2017-07-25 09:20:51 +02:00
48147b7fd1
Give up PGP decryption when intent is cancelled
...
When receiving a PGP message which is not encrypted with YOUR key,
OpenKeychain shows a dialog, which tells you the private key to decrypt
the message is unavailable. However, Conversations won't give up
decrypting the message. So whether the subsequent messages are
decryptable or not, the decryption is blocked at the current message.
The commit fixes the bug in this way: Give up the current message when
the decryption intent is cancelled, so that subsequent messages can be
handled.
2017-07-25 15:09:18 +08:00
432598f896
Merge branch 'bugfixes'
2017-07-23 07:53:09 +02:00
7ac26952d7
version bump to 1.19.5 + changelog
2017-07-23 07:51:13 +02:00
c8bd5bc1f5
made OF selfSigned() workaround only available >=kitkat
...
this undos 8a729061d5
2017-07-23 07:47:39 +02:00
2fc216bfc4
skip initial socket closing if thread was already interrupted
2017-07-21 08:30:16 +02:00
74cde1d60a
incorporate support for publish-options into server info
2017-07-18 12:51:15 +02:00
85dc0c284d
made omemo always available but in public mucs
2017-07-18 12:51:15 +02:00
002dbf2e17
enable all encryption options
2017-07-18 12:51:15 +02:00
da87eac48e
provide upgrade path for accounts with publish-options
2017-07-18 12:51:15 +02:00
9a57673130
use publish-options instead of always pushing node configuration
2017-07-18 12:51:15 +02:00
8d6b2074cb
let hasPendingFetches() return true when fetching device ids
2017-07-18 12:51:15 +02:00
7a2856ac86
fetch required device ids on demand
2017-07-18 12:51:15 +02:00
f7258d16e1
explicitly fetch device ids before building sessions in single mode conversation
2017-07-18 12:51:15 +02:00
25e993693f
change access model of omemo pep nodes after every publish
2017-07-18 12:51:15 +02:00
6c95897f09
fetch device ids for muc members w/o known devices
2017-07-18 12:51:15 +02:00
2a198793b1
fixed otr jingle file size reporting
2017-07-18 12:43:53 +02:00
58f3787795
increment version code for 1.19.4
2017-07-17 23:14:02 +02:00
8a729061d5
use CN-workaround for pre-kitkat
2017-07-17 23:13:55 +02:00
8285a4fe1c
pulled translations from transifex
2017-07-17 22:06:56 +02:00
217335703c
fix regression introduces with OF fix. properly fall back to common name
2017-07-17 21:11:15 +02:00
0a20b87ebe
check length first in timestamp parser
2017-07-16 21:03:59 +02:00
febee9863f
catch IllegalArgumentException caused by invalid custom hostname
2017-07-16 21:02:56 +02:00
2dce71cd96
version bump to 1.19.4 + changelog
2017-07-16 11:38:17 +02:00
8afe7efc2c
workaround for OpenFire: check CN first in self signed certs
...
The self signed certificates created by OpenFire (Not sure if other
certs are affected as well) will crash the Java/Android TLS stack when
accessing getSubjectAlternativeNames() on the the peer certificate.
This usually goes unnoticed in other applications since the
DefaultHostnameVerifier checkes the CN first. That however is a
violation of RFC6125 section 6.4.4 which requires us to check for the
existence of SAN first.
This commit adds a work around where in self signed certificates we
check for the CN first as well. (Avoiding the call to
getSubjectAlternativeNames())
2017-07-16 11:05:25 +02:00
dfa17d1339
more migration fixes for updating from 1.6.0 to 1.19.3
2017-07-14 10:34:01 +02:00
91119ab691
add reminder to remove minidns workarounds once those are fixed
2017-07-14 09:09:26 +02:00
ea6b756c0f
fixed bug in db migrations when going from <15 to something recent
2017-07-13 19:28:16 +02:00
3d0b127a8f
verify with hostname in direct tls connections
2017-07-13 19:27:43 +02:00
7623accfd5
prefer DNS servers from VPNs
2017-07-12 22:19:45 +02:00
35a4b848a5
version bump to 1.19.3 + changelog
2017-07-12 14:46:12 +02:00
45f92553c4
pulled translations from transifex
2017-07-12 11:54:05 +02:00
ecc0ef45c5
disable foreground service if all accounts are disabled
2017-07-12 11:03:32 +02:00
edb28ccb31
throw state changing exception on failed tls only if no more connection options left
2017-07-11 23:25:59 +02:00
19c1484053
catch runtime exceptions from minidns
2017-07-11 23:24:09 +02:00
8de81e0bc8
sync around Conversation.getLatestMessage()
2017-07-11 23:09:51 +02:00
4d1b6d4404
version bump to 1.19.2 + changelog
2017-07-10 12:38:48 +02:00
c5824a3b2a
catch all exceptions around minidns :(
2017-07-10 12:33:04 +02:00
a1f9f5e774
version bump to 1.19.1 + changelog
2017-07-10 10:06:20 +02:00
Daniel Gultsch