| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This bug was introduced in 1ec606540eb0f474f3d968d3566a7c56d778a367 when
`g_strdup_printf` was used instead of `asprintf`.
Problem discoverd by raspeguy.
Mistake discovered by optmzr and Martin.
Thanks to everybody involved!
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When the connection has been re-established, chat and groupchat with OMEMO
should restat the OMEMO Session.
Fix: #1530
* Added HAVE_OMEMO
* clang-format and user output
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
|\ \
| | |
| | | |
Feature - attention flag
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* Display the `[ATTENTION]` hint in the titlebar for both chatwins and
mucwins.
* Use THEME_TITLE_TEXT instead of THEME_TITLE_ENCRYPT
* Have separate function `_show_attention` and don't do it in unrelated
`_show_privacy`.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
When the user enables or disabled the attention flag, a message will be
displayed in the chat window.
|
| | | |
|
| | |
| | |
| | |
| | | |
Attention flag for groupchat and display the windows via "/wins attention"
|
| |/
| |
| |
| |
| |
| |
| | |
User is able to toggle a flag for chat windows. This flag should be used to mark
the window for "Attention".
Use Ctrl+f to mark the window.
|
|/ |
|
|\
| |
| | |
Display OMEMO device ID
|
| |
| |
| |
| |
| | |
Display the OMEMO device ID which has been generated, when the user generated
OMEMO crytographic materials via /omemo gen.
|
|/
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
| |
Found by DebXWoody.
Led to always be true (which still made it work in most cases).
|
|
|
|
| |
So users don't get surprised if they don't know the barejid of the nick.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In https://github.com/profanity-im/profanity/issues/1070 we have:
`OMEMO encryption for MUC PM (OMEMO MUCs are not anonymous, so we should
start a regular 1:1 in this case instead of MUC PM. A discussion started
to make this a general feature #1531)`
In https://github.com/profanity-im/profanity/issues/1531 we have the
general issue to start regular 1:1 messages instead of MUC PMs if the
room is non-anonymous.
This is like suggested in https://docs.modernxmpp.org/client/groupchat/.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Old: `/intype on|of`
Typing information is printed in console and titlebar.
New: `/intype titlebar|console on|off`
Typing information can be configured in more detail.
Regards https://github.com/profanity-im/profanity/issues/1516
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Our variable `alphabet` contains 62 alphanumeric symbols + '\0'.
When we use sizeof(alphabet) we will get 63 due to that.
But we want to choose a random numbers from the 62 alphanumeric letters only.
This mistake caused us to have strings with a max length of `length`
instead of the exact length.
When doing https://github.com/profanity-im/profanity/issues/1520
this caused our algo for muc reflection to not catch since we expect the
random ID to be exactly 15 symbols long in `message_is_sent_by_us()`.
|
|
|
|
|
|
|
| |
Add OMEMO trust mode capabilities.
* ToFu / first usage
* blind trust
* manual
|
|
|
|
|
|
| |
`/executable set editor /full/path/to/edit`.
Regards https://github.com/profanity-im/profanity/issues/1521
|
| |
|
|
|
|
|
| |
Probably many people render text in their head to markdown
automatically.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
compose.editor is the path to the executable ( default /usr/bin/vim )
|
|
|
|
|
|
|
|
| |
* Generating a unique file name in tmp_dir folder
* Changed exec of vim to exec of sensible-editor
* Test file exists and create file with "private" rights
* Send a preview of the message in the window
* Delete temp file
|
|
|
|
| |
Goal is to launch an external editor (eg vim) to edit the text there.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It was a great ride!
IDs look instead of
`TE5BTDc2ZTc3YTMwZGU3MDgzMzllOTliNGExNjVmMjZkMTY1ZmUyZGEyNTUxMjVmODBkMmQzOGMxYWI2ZjAxNzdiM2Q=`
more like `7HcnNSoO1MVvb0p9a9e293152922853e910b8b1a65bb26e225a0568` now.
Regards https://github.com/profanity-im/profanity/issues/1520
We still has our identifier into it to filter MUC reflected messages.
profident maybe should be changed to be longer or be generated upon each
start.
|
|
|
|
|
|
| |
Currently, only `chat_log_omemo_msg_out` can fail (i.e. return `NULL`
instead of a stanza id). In this case, the message is neither printed to
the chat window nor added to the log (since it wasn't sent).
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
The function `omemo_start_session` was effectively called twice in the
`/msg` command: Once in `chatwin_new` and afterwards in `cmd_msg`. I've
removed the second call.
|
|
|
|
|
|
|
| |
_GNU_SOURCE was even in some files where it was not needed at all
(http*).
Let's replace asprintf() with g_strdup_printf().
|