Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | explicitly use BouncyCastle for file crypto | Christian Schneppe | 2020-03-16 | 1 | -1/+1 |
| | |||||
* | set IqPacket publish in AxolotlService final | Christian Schneppe | 2020-03-16 | 1 | -1/+1 |
| | |||||
* | optimize imports | Christian Schneppe | 2020-01-31 | 1 | -1/+2 |
| | |||||
* | omemo changes: use 12 byte IV, no longer accept auth tag appended to payload | Christian Schneppe | 2020-01-24 | 3 | -316/+291 |
| | |||||
* | prevent crash when deleting account on servers that don't support omemo | Christian Schneppe | 2019-12-08 | 1 | -1/+2 |
| | |||||
* | delete omemo keys when deleting account | Christian Schneppe | 2019-09-29 | 1 | -2/+10 |
| | |||||
* | improved logging for messages waiting for join | Christian Schneppe | 2019-09-20 | 1 | -1/+1 |
| | |||||
* | migrate to AndroidX | Christian Schneppe | 2019-09-20 | 2 | -4/+4 |
| | |||||
* | do not finish or repair sessions for untrusted senders | Christian Schneppe | 2019-09-19 | 1 | -12/+32 |
| | | | | | | | | | finishing (sending a key transport message in response to pre key message) as well as reparing sessions will leak resource and availability and might in certain situations in group chat leak the Jabber ID. Therefor we disable that. Leaking resource might not be considered harmful by a lot of people however we have always doing similar things with receipts. | ||||
* | when parsing omemo messages ensure we only find one element | Christian Schneppe | 2019-09-12 | 1 | -1/+1 |
| | |||||
* | show language in message bubble if multiple language variants were received | Christian Schneppe | 2019-09-12 | 1 | -1/+1 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | XML and by inheritence XMPP has the feature of transmitting multiple language variants for the same content. This can be really useful if, for example, you are talking to an automated system. A chat bot could greet you in your own language. On the wire this will usually look like this: ```xml <message to="you"> <body>Good morning</body> <body xml:lang="de">Guten Morgen</body> </message> ``` However receiving such a message in a group chat can be very confusing and potentially dangerous if the sender puts conflicting information in there and different people get shown different strings. Disabling support for localization entirely isn’t an ideal solution as on principle it is still a good feature; and other clients might still show a localization even if Conversations would always show the default language. So instead we now show the displayed language in a corner of the message bubble if more than one translation has been received. If multiple languages are received we will attempt to find one in the language the operating system is set to. If no such translation can be found it will attempt to display the English string. If English can not be found either (for example a message that only has ru and fr on a phone that is set to de) it will display what ever language came first. Furthermore we will discard (not show at all) messages with with multiple bodies of the same language. (This is considered an invalid message) The language tag will not be shown if we receive a single body in a language not understood by the user. (For example operating system set to 'de' and message received with one body in 'ru' will just display that body as usual.) As a guide line to the user: If you are reading a message where it is important that this message is not interpreted differently by different people (like a vote (+1 / -1) in a chat room) make sure it has *no* language tag. | ||||
* | fix some crashes | Christian Schneppe | 2019-09-03 | 3 | -8/+45 |
| | |||||
* | introduced type private_file_message to handle attachments in PMs | Christian Schneppe | 2019-05-03 | 1 | -1/+1 |
| | |||||
* | optimize imports | Christian Schneppe | 2019-02-08 | 2 | -2/+0 |
| | |||||
* | hide lock icon in channels; modify muc user context | Christian Schneppe | 2019-02-08 | 1 | -34/+0 |
| | |||||
* | handle decrypting/encrypting of omemo messages with duplicate device ids | Christian Schneppe | 2019-01-07 | 2 | -43/+77 |
| | |||||
* | postpone prekey removal and republish to after mam | Christian Schneppe | 2018-12-14 | 2 | -10/+34 |
| | |||||
* | implement self healing omemo | Christian Schneppe | 2018-12-04 | 4 | -14/+105 |
| | | | | | | after receiving a SignalMessage that can’t be decrypted because of broken sessions Conversations will attempt to grab a new pre key bundle and send a new PreKeySignalMessage wrapped in a key transport message. | ||||
* | set access model to open when publishing avatar | Christian Schneppe | 2018-11-30 | 1 | -10/+9 |
| | |||||
* | use bouncycastle provider up to api 27 | Christian Schneppe | 2018-10-20 | 1 | -2/+2 |
| | | | | | | | apparently using conscrypt on Android below version 7? throws an exception when using 16 byte IVs. so we now use BC when ever possible (excluding api 28) we don’t know why Conscrypt behaves differently on various android versions | ||||
* | go back to 16 byte IVs for OMEMO | Christian Schneppe | 2018-10-20 | 2 | -13/+13 |
| | | | | clients like Dino can’t handle 12 byte IVs | ||||
* | added a few TODOs in regards to the handling of inactive devices | Christian Schneppe | 2018-10-04 | 2 | -2/+4 |
| | |||||
* | prevent race condition when fetching device ids | Christian Schneppe | 2018-10-04 | 2 | -43/+47 |
| | |||||
* | use 12 byte IV for omemo and http upload | Christian Schneppe | 2018-10-04 | 1 | -1/+1 |
| | |||||
* | refresh ui after device list update only if list has changed | Christian Schneppe | 2018-10-04 | 1 | -2/+11 |
| | |||||
* | do not use BC provider on android 22+ | Christian Schneppe | 2018-09-26 | 1 | -2/+3 |
| | |||||
* | open trust key screen when download is in progress | Christian Schneppe | 2018-07-09 | 1 | -1/+1 |
| | |||||
* | do not include white listed domains in room list | Christian Schneppe | 2018-06-29 | 1 | -1/+1 |
| | |||||
* | OMEMO: remove omemo device from own list if bundle is broken | Christian Schneppe | 2018-06-01 | 1 | -70/+80 |
| | |||||
* | make session completion work with untrusted devices as well | Christian Schneppe | 2018-05-16 | 3 | -7/+11 |
| | |||||
* | improved logging for node configuration change | Christian Schneppe | 2018-05-05 | 1 | -4/+9 |
| | |||||
* | do not invoke onPushFailed() on timeout | Christian Schneppe | 2018-05-02 | 1 | -4/+9 |
| | |||||
* | very much unoptimized search functionality | Christian Schneppe | 2018-04-30 | 1 | -1/+1 |
| | |||||
* | code cleanup in AxolotlService.fetchDeviceIds() | Christian Schneppe | 2018-04-24 | 1 | -25/+29 |
| | |||||
* | load currently open conversation faster | Christian Schneppe | 2018-04-24 | 1 | -1/+0 |
| | |||||
* | make error message for 'not encrypted for this device' | Christian Schneppe | 2018-04-23 | 1 | -2/+9 |
| | |||||
* | create dedicated exception for not encrypted for this device | Christian Schneppe | 2018-04-23 | 2 | -1/+36 |
| | |||||
* | figure out fallbacks with omemo source id | Christian Schneppe | 2018-04-12 | 2 | -0/+29 |
| | |||||
* | offer a more convienient way to disable omemo from trust keys dialog | Christian Schneppe | 2018-04-08 | 1 | -26/+43 |
| | |||||
* | migrate to xmpp-addr | Christian Schneppe | 2018-04-02 | 4 | -82/+84 |
| | |||||
* | encrypt muc PM only to actual recipient | Christian Schneppe | 2018-01-27 | 1 | -5/+23 |
| | |||||
* | improvements for self messages | Christian Schneppe | 2018-01-27 | 1 | -2/+7 |
| | | | | | | * fix omemo in group chats w/o participants * don't create two axolotl messages when messaging self * fix read marker for self messages | ||||
* | allow axolotl header to be empty in empty mucs | Christian Schneppe | 2018-01-27 | 1 | -4/+4 |
| | |||||
* | make chat markers opportunistic in private mucs | Christian Schneppe | 2018-01-27 | 1 | -2/+2 |
| | |||||
* | disable offline messages. postpone prekey handling until after mam catchup | Christian Schneppe | 2018-01-21 | 1 | -3/+33 |
| | |||||
* | properly handle key transport messages. use prekeyparsing only when that ↵ | Christian Schneppe | 2018-01-21 | 3 | -36/+38 |
| | | | | attribute is set | ||||
* | show pep as available if omemo_all_access has been installed on server | Christian Schneppe | 2017-12-27 | 1 | -0/+1 |
| | |||||
* | fixed omemo device list not getting annouced on empty list | Christian Schneppe | 2017-12-27 | 1 | -1/+1 |
| | |||||
* | fixup for pep omemo notification dedup | Christian Schneppe | 2017-12-16 | 1 | -4/+6 |
| | |||||
* | fixed workaround that allowed us to expire devices | Christian Schneppe | 2017-12-16 | 1 | -7/+8 |
| |