| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
Remove support for libsignal-protocol-c < 2.3.2.
Debian 10 uses 2.3.2, Debian 11 and 12 use 2.3.3.
openSUSE from 15.2 onward uses 2.3.3.
Fedora since 28 uses 2.3.2.
We should be good.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The most loggings has been set to debug. Just in case of error / problem the
logging should be done with log-level ERROR or WARNING.
We will see later, which loggings should be switched to log-level INFO.
This improvement has been done to find OMEMO bugs.
See also: #1070 #1530 #1538
|
| |
|
|
|
|
|
|
| |
This reverts commit 9b55f2dec0ea27a9ce4856e303425e12f866cea2.
Sorting the includes creates some problems.
|
|
|
|
| |
Regards https://github.com/profanity-im/profanity/issues/1396
|
| |
|
|
|
|
| |
I don't see a reason for strdupping here.
|
|
|
|
| |
I don't see a reason for strdupping here.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Probably missing copy of body to plain in carbon and privmessage.
Only covers the incoming message path because goal is OMEMO decryption
of untrusted message.
Cover some of the log functions but not all.
|
|
|
|
| |
Use it to print message on red background if not trusted.
|
|
|
|
|
| |
Trust all key as long as it's for reading. This code isn't multithread
safe.
|
| |
|
|
|
|
|
|
| |
We have to store known_devices in a long term fashion otherwise we might
not be able to delete session if it is remove from device list server
side.
|
|
|
|
|
|
|
|
| |
When decrypting first message with prekey, libsignal wants to remove
used prekey from storage. Return value on success should be 0.
We used to return number of deleted keys. Thus libsignal was considering
we failed to remove the key and we were ignoring plaintext.
|
|
|
|
|
| |
Stop using "jid:device_id" keys. And move long term storage to its own
file: trust.txt.
|
| |
|
| |
|
|
|
|
|
| |
Also add long terme storage of known identity keys.
If a key is stored it means it is trusted.
|
| |
|
| |
|
|
|
|
| |
Fix {signed,}_pre_key store
|
| |
|
|
|