about summary refs log tree commit diff stats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* Free omemo_ctx.device_list_handlerMichael Vetter2019-07-041-0/+1
|
* Dont initialize omemo autocompleter twiceMichael Vetter2019-07-041-2/+0
| | | | | We already do this in omemo_init() no need to do it again in omemo_on_connect().
* Add omemo_close functionMichael Vetter2019-07-043-0/+13
| | | | | | | | | | | | | | | | | | | | | | We call omemo_init() when starting profanity and should have an omemo_close() at exit. For now we free the fingerprint autocompleter in there. Fixes valgrind: ``` ==13226== 24 bytes in 1 blocks are definitely lost in loss record 2,855 of 6,958 ==13226== at 0x483677F: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so) ==13226== by 0x48AD39: autocomplete_new (autocomplete.c:57) ==13226== by 0x4AB89F: omemo_init (omemo.c:127) ==13226== by 0x42C283: _init (profanity.c:206) ==13226== by 0x42BFF3: prof_run (profanity.c:98) ==13226== by 0x4B25E6: main (main.c:172) ``` Regards https://github.com/profanity-im/profanity/issues/1131
* Use correct jid variableMichael Vetter2019-07-031-1/+1
|
* Define goto out in _private_chat_handler()Michael Vetter2019-07-031-0/+1
|
* Set plain message in _private_chat_handlerMichael Vetter2019-07-031-0/+7
| | | | | | In case that plain is NULL we need to copy over from body. Fix https://github.com/profanity-im/profanity/issues/1144
* Show MUC history on intentional reconnectMichael Vetter2019-07-034-7/+42
| | | | | Small bug caused by 13675fb and ce5a4ed. Fix https://github.com/profanity-im/profanity/issues/1142
* Mark messages received from a session as trustedPaul Fariello2019-06-253-10/+25
|
* Fix a segfault when carbon has no bodyPaul Fariello2019-06-211-11/+13
|
* Fix handling of encrypted carbonsPaul Fariello2019-06-213-30/+62
|
* Don't highlight cleartext message as untrustedPaul Fariello2019-06-211-0/+1
|
* Fix segfault when receiving messages without IDPaul Fariello2019-06-211-1/+3
|
* Fix NULL pointer when handling non encrypted message in MUCPaul Fariello2019-06-211-1/+9
|
* Rename prof_message_t into ProfMessagePaul Fariello2019-06-2013-45/+45
|
* Set foreground color for untrusted messagesPaul Fariello2019-06-205-9/+10
|
* Add prof_message_t to wrap all message attributesPaul Fariello2019-06-2017-337/+410
| | | | | | | 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 flags in xmmp/message.c for encryption and trustPaul Fariello2019-06-206-25/+44
|
* Add trusted state after OMEMO decryptionPaul Fariello2019-06-207-18/+24
| | | | Use it to print message on red background if not trusted.
* Decrypt all incoming OMEMO msgPaul Fariello2019-06-203-1/+23
| | | | | Trust all key as long as it's for reading. This code isn't multithread safe.
* _bookmark_destroy: follow normal logicMichael Vetter2019-06-201-7/+5
|
* Call message_handlers_clear() upon disconnectMichael Vetter2019-06-203-0/+10
| | | | Free pubsub_event_handlers. Fix memory leaks.
* Call iq_handlers_clear() upon disconnectMichael Vetter2019-06-203-0/+10
| | | | Free id_handlers. Fix memory leaks.
* Free contacts in omemo_start_sessions()Michael Vetter2019-06-191-0/+1
|
* Free OMEMO session store upon disconnectMichael Vetter2019-06-191-0/+1
|
* Fix prefs_get_string mem leaks in statusbarMichael Vetter2019-06-191-6/+18
|
* Free last_msg_timestampMichael Vetter2019-06-191-0/+4
| | | | Fix memory leak.
* Add option to set all window related time formatsMichael Vetter2019-06-173-4/+51
| | | | | | | | | | | | | | | | | | | Implements feature requested at: https://github.com/profanity-im/profanity/issues/632 So instead of: /time console set <format> /time chat set <format> /time muc set <format> /time mucconfig set <format> /time private set <format> /time xml set <format> As a short cut the user can do: /time all set <format> Excluding statusbar and lastactivity settings since they are not for main windows, but used slightly differently.
* Add copyright to omemo codeMichael Vetter2019-06-176-0/+199
|
* Add myself to copyrightMichael Vetter2019-06-1714-0/+16
| | | | Like discussed with James.
* Use profanity channel as exampleMichael Vetter2019-06-171-3/+3
|
* Merge pull request #1110 from profanity-im/feature/704-ui-behaviour-reconnectMichael Vetter2019-06-115-2/+57
|\ | | | | Feature/704 ui behaviour reconnect
| * Safe last MUC message timestamp per MUCMichael Vetter2019-06-113-8/+10
| | | | | | | | | | | | After pasis review of my code he thinks it's better to safe the timestamp per MUC so we can account for some problems that could occur with timing.
| * Only show MUC subject on first connectMichael Vetter2019-06-051-1/+1
| | | | | | | | | | | | For #704 we don't show the room history upon reconnect. Now we also don't show the room subject in the channel upon re-established connection.
| * Reduce timestamp call when saving last muc messageMichael Vetter2019-06-051-12/+13
| | | | | | | | Let's test for mucwin earlier.
| * Only print room history for new messages upon reconnectMichael Vetter2019-06-053-1/+53
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If re-establish a connection don't print the room history again. In case there there happened nothing at all since we got the room history on the last connection. And in case there were no new messages during the time we have been disconnected. Instead of printing the room history again we now print 'Re-established Connection'. This adds a bit of overhead since we save the timestamp upon every MUC message. See: https://github.com/profanity-im/profanity/issues/704
* | Rejoin all MUCs on reconnectMichael Vetter2019-06-101-5/+3
| | | | | | | | Should fix https://github.com/profanity-im/profanity/issues/1120
* | Merge pull request #1125 from profanity-im/fix/519-logrotateMichael Vetter2019-06-101-6/+9
|\ \ | | | | | | Iterate logfiles until 100 are reached
| * | Iterate logfiles until 100 are reachedMichael Vetter2019-06-071-6/+9
| | | | | | | | | | | | Fix https://github.com/profanity-im/profanity/issues/519
* | | Merge pull request #1124 from ↵Michael Vetter2019-06-082-16/+122
|\ \ \ | |/ / |/| | | | | | | | paulfariello/feature/remove_session_when_untrusting_omemo_device Remove OMEMO session when untrusting a fingerprint
| * | Remove OMEMO session when untrusting a fingerprintPaul Fariello2019-06-072-16/+122
| | | | | | | | | | | | | | | | | | 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.
* | | Merge pull request #1123 from profanity-im/fix/1093-already-started-messageMichael Vetter2019-06-071-40/+25
|\ \ \ | | | | | | | | Print omemo start related msgs into correct window
| * | | Refactor cmd_omemo_startMichael Vetter2019-06-071-38/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some code was duplicated/similar. The parts about using a chatwin while being started from another window (recipient provided) and being a chatwin were the same. Like this it should be easier to read and less code.
| * | | Print omemo start related msgs into correct windowMichael Vetter2019-06-071-3/+3
| | | | | | | | | | | | | | | | | | | | Print them in the window of the contact. Not just the current window. Fix https://github.com/profanity-im/profanity/issues/1093
* | | | Merge pull request #1118 from profanity-im/fix/1117-omemo-autocompletion-crashMichael Vetter2019-06-071-26/+27
|\ \ \ \ | |/ / / |/| | | Only complete certain omemo commands if connected
| * | | Only complete certain omemo commands if connectedMichael Vetter2019-06-061-26/+27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Some of the omemo commands depend on the roster being present. Several of those functions call `assert()` if that's not the case. Modify omemo autocompletion in such a way that only things that don't need the roster will be completed. Only works on first level. When typing `/omemo` it will still complete to `/omemo start` but not offer suggestions for that, but print a message that you need to be connected. Fix https://github.com/profanity-im/profanity/issues/1117
* | | | Merge pull request #1121 from profanity-im/feature/notify-plugin-failMichael Vetter2019-06-073-16/+31
|\ \ \ \ | |_|/ / |/| | | Improve plugin load/install failure message
| * | | Improve plugin load/install failure messageMichael Vetter2019-06-073-16/+31
| |/ / | | | | | | | | | | | | | | | In case Python or C plugins are disabled install/load failed silently. Notify the user that we can't load them because profanity was built without support for plugins.
* | | Check for sane argument in autoconnect setMichael Vetter2019-06-051-4/+8
| | | | | | | | | | | | | | | Check that user doesnt do `/autoconnect set `. Which would result in: `Account '(null)' does not exist`.
* | | Check if valid account before setting autoconnectMichael Vetter2019-06-051-3/+7
|/ / | | | | | | Fixes https://github.com/profanity-im/profanity/issues/1112
* / Add omemo.char theme optionMichael Vetter2019-06-051-0/+8
|/ | | | Thanks to @kaffekanne for noticing this!
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-09-08 23:29:06 +0000