about summary refs log tree commit diff stats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* OMEMO: Separate handling of device listDebXWoody2021-06-051-1/+12
| | | | | | | | | | | | | | | | | | | | | | 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
* Merge pull request #1542 from DebXWoody/bugfix/fix1541Michael Vetter2021-06-031-0/+13
|\ | | | | OMEMO: Don't encrypt to yourself (MUC)
| * OMEMO: Don't encrypt to yourself (MUC)DebXWoody2021-05-291-4/+4
| | | | | | | | Use connection_get_barejid instead of connection_get_fulljid.
| * OMEMO: Don't encrypt to yourself (MUC)DebXWoody2021-05-281-0/+13
| | | | | | | | | | | | | | | | | | 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
* | http upload: use correct content typeMichael Vetter2021-06-021-1/+1
| | | | | | | | | | | | | | | | | | | | 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!
* | Change restarted omemo textMichael Vetter2021-06-021-2/+2
| |
* | Restart OMEMO Session after lost connectionDebXWoody2021-06-021-7/+29
| | | | | | | | | | | | | | | | | | | | 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
* | OMEMO - Unable to publish own device listDebXWoody2021-06-012-2/+19
| | | | | | | | | | | | | | | | | | | | 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.
* | Merge pull request #1543 from DebXWoody/feature/attention-flagMichael Vetter2021-05-3113-1/+235
|\ \ | | | | | | Feature - attention flag
| * | Change ui_win_has_attention() logicMichael Vetter2021-05-311-3/+5
| | |
| * | Change attention descriptionMichael Vetter2021-05-311-1/+1
| | |
| * | Display attention hint in titlebar for mucs tooMichael Vetter2021-05-311-12/+23
| | | | | | | | | | | | | | | | | | | | | | | | * 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`.
| * | Attention-flag: Fix next windowDebXWoody2021-05-291-8/+25
| | |
| * | Attention flag message ( enabled, disabled)DebXWoody2021-05-291-1/+6
| | | | | | | | | | | | | | | When the user enables or disabled the attention flag, a message will be displayed in the chat window.
| * | Attention flag - Implemented Alt+mDebXWoody2021-05-296-11/+86
| | |
| * | Attention flag for groupchatsDebXWoody2021-05-298-3/+80
| | | | | | | | | | | | Attention flag for groupchat and display the windows via "/wins attention"
| * | Attention flag for chat windowsDebXWoody2021-05-298-1/+48
| |/ | | | | | | | | | | | | 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.
* / external editor: don't use absolute paths and allow path searchJörg Thalheim2021-05-302-6/+2
|/
* Merge pull request #1540 from DebXWoody/feature/omemo-display-deviceidMichael Vetter2021-05-281-1/+1
|\ | | | | Display OMEMO device ID
| * Display OMEMO device IDDebXWoody2021-05-281-1/+1
| | | | | | | | | | Display the OMEMO device ID which has been generated, when the user generated OMEMO crytographic materials via /omemo gen.
* | Improved OMEMO loggingDebXWoody2021-05-284-40/+84
|/ | | | | | | | | | | 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
* Fix spelling of "persistent(ly)"Raf Czlonka2021-05-231-3/+3
|
* message: correct type checkingMichael Vetter2021-05-141-1/+1
| | | | | Found by DebXWoody. Led to always be true (which still made it work in most cases).
* Print message about new direct messageMichael Vetter2021-05-121-0/+4
| | | | So users don't get surprised if they don't know the barejid of the nick.
* Use direct messages instead of MUC-PMs for non-anon MUCsMichael Vetter2021-05-121-35/+51
| | | | | | | | | | | | | 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/.
* Have intype on by defaultMichael Vetter2021-05-081-0/+2
|
* Have separate settings for intypeMichael Vetter2021-05-087-14/+62
| | | | | | | | | | 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
* Reduce scope of dir variableMichael Vetter2021-05-061-1/+2
|
* command: Simplify return in autocompletionMichael Vetter2021-05-061-65/+12
|
* Apply pre_chat_message_display hook to historyDustin Lagoy2021-04-271-0/+1
|
* command: Fix serversoftware examplesMichael Vetter2021-04-181-2/+2
|
* Fix random string generationMichael Vetter2021-04-171-1/+2
| | | | | | | | | | | | | 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()`.
* OMEMO - trust mode (#1506)Stefan2021-04-177-0/+94
| | | | | | | Add OMEMO trust mode capabilities. * ToFu / first usage * blind trust * manual
* editor: make editor configurable via /executableMichael Vetter2021-04-164-3/+23
| | | | | | `/executable set editor /full/path/to/edit`. Regards https://github.com/profanity-im/profanity/issues/1521
* editor: adapt help descriptionMichael Vetter2021-04-161-2/+3
|
* editor: Save temp files as .mdMichael Vetter2021-04-161-2/+2
| | | | | Probably many people render text in their head to markdown automatically.
* Editor: improve error messagesMichael Vetter2021-04-161-6/+6
|
* editor: Use g_strdup_printf() instead of g_string_new()Michael Vetter2021-04-161-11/+4
|
* Run clang-format on new editor codeMichael Vetter2021-04-162-18/+18
|
* Editor: Fix redisplayStefan2021-04-161-1/+4
|
* Editor: Use _exit() instead of exit()Stefan2021-04-161-1/+1
|
* Editor: Using preferences compose.editorStefan2021-04-163-9/+25
| | | | compose.editor is the path to the executable ( default /usr/bin/vim )
* Editor command: filename / sensible-editorStefan2021-04-161-9/+50
| | | | | | | | * 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
* Add new editor commandStefan2021-04-163-0/+55
| | | | Goal is to launch an external editor (eg vim) to edit the text there.
* Mention clipboard in version outputMichael Vetter2021-04-161-2/+2
|
* Goodbye beautiful IDsMichael Vetter2021-04-143-30/+18
| | | | | | | | | | | | | | | 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.
* Msg sending: don't write to chatwin nor to log if sending failedMaximilian Wuttke2021-04-081-12/+18
| | | | | | 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).
* OMEMO: Fail if message keys couldn't be encrypted for any recipient deviceMaximilian Wuttke2021-04-082-8/+27
| | | | | | | | | 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.
* OMEMO: Remove duplicate session initalisationMaximilian Wuttke2021-04-082-18/+20
| | | | | | 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.
* Get rid of asprintf and _GNU_SOURCE defineMichael Vetter2021-03-3012-104/+97
| | | | | | | _GNU_SOURCE was even in some files where it was not needed at all (http*). Let's replace asprintf() with g_strdup_printf().
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-08-21 18:53:43 +0000