about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 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.
* Merge pull request #1515 from mwuttke97/fix_omemo_empty_devlistMichael Vetter2021-04-084-30/+57
|\ | | | | [OMEMO] Fix sending messages
| * 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().
* Fix segfault in cmd_autoaway()Michael Vetter2021-03-291-9/+12
| | | | | | | | | Two mistakes were here: * `/autoaway time away` without a time argument segfaulted * `/autoaway message away` without a mesage set to (null). We have `/autoaway message off to set it off. Also use g_strcmp0() instead of strcmp().
* Merge pull request #1514 from profanity-im/fix/1512-rpiMichael Vetter2021-03-2644-0/+88
|\ | | | | Include config.h in omemo files
| * Add config.h in files were it was missingMichael Vetter2021-03-2642-0/+84
| | | | | | | | Related to https://github.com/profanity-im/profanity/issues/1512
| * Include config.h in omemo filesMichael Vetter2021-03-262-0/+4
|/ | | | | | | | | 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!
* iq: use define for 'cancel'Michael Vetter2021-03-261-2/+2
|
* message: parse stanzaid in MUC caseMichael Vetter2021-03-251-1/+9
| | | | | | | | | | | | | | | | | | There was a todo for this in message.c which got forgotten. This was most likely also the reason why there were NULL entries for this in the DB which DebXWoody mentioned in the MUC. Thus comparison was with NULL and no new entries were added to the database. Edit: After checking pull requests I see Stefans draft PR: https://github.com/profanity-im/profanity/pull/1505 So let's add him as co-author. Co-authored-by: Stefan Kropp <stefan@debxwoody.de>
* Merge pull request #1513 from profanity-im/fix-possible-segfault1Michael Vetter2021-03-257-204/+298
|\ | | | | Fix potential problems caused by unexpected stanzas
| * ox: fix memleak in ox_announce_public_keyMichael Vetter2021-03-251-1/+3
| |
| * message: make _handle_error saferMichael Vetter2021-03-251-2/+4
| |
| * event: make log_database_get_previous_chat saferMichael Vetter2021-03-251-2/+4
| |
| * database: make log_database_get_previous_chat saferMichael Vetter2021-03-251-0/+2
| |
| * database: simplify _log_database_add_outgoingMichael Vetter2021-03-251-2/+1
| |
| * database: simplify log_database_add_incomingMichael Vetter2021-03-251-2/+1
| |
| * avatar: make _avatar_request_item_result_handler saferMichael Vetter2021-03-251-0/+4
| |
| * avatar: make _avatar_metadata_handler saferMichael Vetter2021-03-251-11/+20
| |
| * ox: make _ox_public_key_result saferMichael Vetter2021-03-251-5/+15
| |
| * ox: guard printing of fingerprintMichael Vetter2021-03-251-1/+3
| |
| * ox: improve error log in _ox_metadata_resultMichael Vetter2021-03-251-1/+1
| |
| * ox: add logging prefixMichael Vetter2021-03-251-15/+15
| |
| * stanza: guard mallocsMichael Vetter2021-03-251-70/+88
| | | | | | | | | | If this happens we have more serious problems :-) But anyways..
| * stanza: simplify stanza_get_muc_destroy_alternative_roomMichael Vetter2021-03-251-4/+1
| |
| * stanza: replae strcmp with g_strcmp0Michael Vetter2021-03-251-17/+17
| | | | | | | | since its NULL safe
| * message: simplify _handle_headlineMichael Vetter2021-03-251-4/+2
| |
| * message: make _receipt_request_handler saferMichael Vetter2021-03-251-1/+1
| |
| * message: make _handle_receipt_received saferMichael Vetter2021-03-251-1/+5
| |
| * message: make _handle_groupchat saferMichael Vetter2021-03-251-0/+6
| |
| * message: simplify _handle_conferenceMichael Vetter2021-03-251-7/+5
| |
| * message: make _handle_form saferMichael Vetter2021-03-251-0/+3
| |
| * message: make _message_handler saferMichael Vetter2021-03-251-7/+9
| |
| * mesage: make _handle_ox_chat saferMichael Vetter2021-03-251-11/+27
| | | | | | | | And on the way fix a memleak
| * message: make _handle_chat saferMichael Vetter2021-03-251-0/+3
| |
| * message: make _handle_muc_private_message saferMichael Vetter2021-03-251-0/+7
| |
| * message: fix potential segfault in _receipt_request_handlerMichael Vetter2021-03-251-3/+7
| |
| * message: safeguard _handle_receipt_receivedMichael Vetter2021-03-251-15/+17
| | | | | | | | | | | | This shouldnt be necessary since we check for the receipt outside alreayd. Let's be on the safe side though in case code gets changed later.
| * message: reorder _handle_groupchatMichael Vetter2021-03-251-12/+9
| |
| * message: fix possible segfault in _handle_conferenceMichael Vetter2021-03-251-19/+23
| |
| * message: fix possible segfault in _handle_muc_userMichael Vetter2021-03-251-0/+4
|/
* message: fix possible segfault in _message_handlerMichael Vetter2021-03-251-3/+3
|
* Merge pull request #1510 from profanity-im/fix/1210-muc-registerMichael Vetter2021-03-258-6/+164
|\ | | | | Register nickname with MUC
| * Add support to register with a roomMichael Vetter2021-03-258-6/+164
|/ | | | | | | | | | `/affiliation register` can now be used to register a nickname with a MUC. Tested with a server without forms. Couldn't find a server which supports forms yet. Implements https://github.com/profanity-im/profanity/issues/1210
* debug build: build without -fsanitize=addressMichael Vetter2021-03-241-1/+1
| | | | | | | | | | | | Sorry :-) Seems then we can't use valgrind since that does its own ASAN things. So maybe developers needs to set some flags by themselves to find these memory issues. https://fuzzing-project.org/tutorial-cflags.html might be of help. Regards: https://github.com/profanity-im/profanity/issues/1512
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-14 23:14:17 +0000