| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
This reverts commit 19921f61c14095cadc55b329dd7c8f02bdc79d31, reversing
changes made to ac581c29bfa7c31fbfb6fe8019d257d3883b33bb.
|
|
|
|
|
|
|
|
| |
Use gchar instead of char in most of the cases where gchar is intended.
Reason: improve compatibility and stability. Issue #1819
Minor refactoring.
|
|
|
|
|
|
|
| |
As stated in
https://github.com/profanity-im/profanity/pull/1820#issuecomment-1498083383
profanity uses "..." (three dots) in a lot of places instead the proper
ellipsis char "…".
|
|
|
|
| |
Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
|
|
|
|
|
| |
The macro is effective on OpenBSD and basically a no op on other platforms.
Use it for one existing and the other known debug statements.
|
|
|
|
| |
OpenBSD's kernel warns about NULL printfs. Fix this with a standard check.
|
|
|
|
| |
Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
|
| |
|
| |
|
|
|
|
|
|
|
| |
Current clients sid/fingerprint will be shown in following format:
`xmpp:<user@server>?omemo-sid-<numerical-sid>=<omemo-fingerprint-hex-string>`
Fix https://github.com/profanity-im/profanity/issues/1320
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
As all parts of the code invoking the `files_get_account_data_path()`
function did the same afterwards, a function has been added with the same
behavior.
1. create path
2. `mkdir` of that path
3. return final path
Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Signed-off-by: Steffen Jaeckel <jaeckel-floss@eyet-services.de>
|
|
|
|
|
| |
Now the sender devices are acknowledged only after omemo is loaded. That
is, after key generation has been completed or identity has been loaded.
|
|
|
|
|
|
|
|
| |
After generation of an identity we observe that `omemo_ctx.device_list`
has an entry for sender's jid. But on application restart it is absent
thus messages are not encrypted for the rest set of sender devices.
This commit fixes this by applying code for acquiring the aforementioned device list after the connection.
|
| |
|
|
|
|
| |
Fix https://github.com/profanity-im/profanity/issues/1584
|
|
|
|
|
|
|
|
| |
Fixes the bug mentioned in
https://github.com/profanity-im/profanity/issues/1478#issuecomment-794161606
The rest of https://github.com/profanity-im/profanity/issues/1478 I
can't reproduce. Seems to work fine.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In profanity are two handlers for device list:
* _handle_own_device_list
* _handle_device_list_start_session
I seems both handler will start a session via
omemo_start_device_session_handle_bundle
_handle_own_device_list will also make sure, that the own device is withing the
omemo device list. If we add the _handle_device_list_start_session into the
hashmap, we are not going the republish ourself, in case we clean-up the device
list from another client.
This will maybe fix #1552
99 Little Bugs in my Code.
Take one down.
Patch it around.
113 Bugs in my Code
|
|\
| |
| | |
OMEMO: Don't encrypt to yourself (MUC)
|
| |
| |
| |
| | |
Use connection_get_barejid instead of connection_get_fulljid.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
As defined in XEP-0384 the application should not encrypt the message to own
devices. Within a groupchat, yourself are a recipients as well.
We will check the recipients and filter out the own device of the own jid.
This Pull Request will fix Issue: #1541
|
|/
|
|
|
|
|
|
|
|
| |
If we are not able to publish our own device list, we just ignored it.
This commit will show at least an error message and informs the user that this
device is currently not in the list of devices.
See Issue: #1538
Next task will be to handle the <precondition-not-met/> conflict properly.
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
Add OMEMO trust mode capabilities.
* ToFu / first usage
* blind trust
* manual
|
|
|
|
|
|
|
|
|
| |
If the message (key) can't be encrypted for any device, sending the
message is refused and an informative error message is presented to the
user.
Also, don't encrypt for the same device, since the OMEMO XEP disallows
this.
|
|
|
|
|
|
|
|
|
| |
So that off_t is defined in all files (so far http_upload.c and
http_download.c too) the same way.
Fix https://github.com/profanity-im/profanity/issues/1512
Thanks @pasis for finding the solution!
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
We require c99/gnu99 anyways.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This reverts commit 9b55f2dec0ea27a9ce4856e303425e12f866cea2.
Sorting the includes creates some problems.
|
|
|
|
| |
Regards https://github.com/profanity-im/profanity/issues/1396
|
|\ |
|
| |\
| | |
| | | |
Request Device and Key, when OMEMO is in use
|