about summary refs log tree commit diff stats
path: root/src/event
Commit message (Collapse)AuthorAgeFilesLines
* Don't log own messages on incoming MUCMichael Vetter2019-10-061-4/+7
| | | | | | | | | | | | | | `sv_ev_room_message()` called `groupchat_log_msg_in()` to log all incoming MUC messages. `cl_ev_send_muc_msg()` calls `groupchat_log_msg_out()`. So messages sent by the user himself was logged two times. Filter the incoming messages and only log the ones not from our occupant jid/nick. Fix https://github.com/profanity-im/profanity/issues/1201
* Log outgoing carbons instead of incomingMichael Vetter2019-10-041-4/+4
| | | | | | | | Incoming carbons are logged as normal message already. So we had this logged twice but didn't log outgoing carbons, send from our account but by another client, at all. Fix https://github.com/profanity-im/profanity/issues/1181
* Log 1:1 messages from other clients also to fileMichael Vetter2019-09-041-0/+4
| | | | | | Carbons where not logged so far. Fix https://github.com/profanity-im/profanity/issues/1181
* Improve sv_ev_roster_received() last activity checkMichael Vetter2019-08-021-11/+9
| | | | | We don't need to do all the timing stuff if last activity is disabled anyways.
* Don't print subscribed message if contact is already in rosterMichael Vetter2019-08-011-2/+6
| | | | | | | | | | | This occured with a user running Cisco Jabber. It seems this server sends repeated presence subscribed stanzas. And although I find this strange according to RFC this seems to be ok. So let's filter them and only display in the console output and to the log. But don't open seperate windows. Fix https://github.com/profanity-im/profanity/issues/1165
* 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
* Fix handling of encrypted carbonsPaul Fariello2019-06-211-25/+57
|
* Rename prof_message_t into ProfMessagePaul Fariello2019-06-202-17/+17
|
* Add prof_message_t to wrap all message attributesPaul Fariello2019-06-203-146/+154
| | | | | | | 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-201-5/+5
|
* Add myself to copyrightMichael Vetter2019-06-172-0/+2
| | | | Like discussed with James.
* Merge pull request #1110 from profanity-im/feature/704-ui-behaviour-reconnectMichael Vetter2019-06-111-2/+32
|\ | | | | Feature/704 ui behaviour reconnect
| * Safe last MUC message timestamp per MUCMichael Vetter2019-06-111-8/+7
| | | | | | | | | | | | 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-051-1/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Cancel autoping timer on disconnect or connection lossDmitry Podgorny2019-06-031-0/+1
| | | | | | | | | If Profanity is disconnected in any way before ping response is received, the autoping timer will expire after the next connection is established. As result, user will be disconnected immediately. Cancel autoping timer in ev_disconnect_cleanup(), so it is done for all kind of disconnections.
* Close windows on connection loss not general disc.Michael Vetter2019-05-272-1/+1
| | | | | | | | | | Call `ui_close_all_wins();` only if we disconnect on purpose not when connection is lost. Otherwise users might miss messages. This partly reverts 6ac73db876c83c7068c4795b19c09ea59eb18a40. Regards https://github.com/profanity-im/profanity/issues/1083
* Create seperate function for disconnect cleanupMichael Vetter2019-05-194-30/+113
| | | | | Duplicate code in client_events.c and server_events.c. Let's have events/common.c and a function containing that code.
* Fix ifdef guard (should have been OMEMO)Michael Vetter2019-05-061-1/+1
|
* Reset things on connection lossMichael Vetter2019-05-061-0/+5
| | | | | Remove the windows, clear tls certs, clean omemo. Regards https://github.com/profanity-im/profanity/issues/1089
* Merge pull request #1063 from paulfariello/hotfix/presence-before-rosterMichael Vetter2019-04-171-0/+1
|\ | | | | Handle presence received before roster
| * Handle presence received before rosterPaul Fariello2019-04-171-0/+1
| | | | | | | | | | | | | | | | | | | | Presence of contact not found in roster are filtered out. But sometimes roster is received after a first few presences. We choose to store presences until we receive roster and then process this presences. Fixes #1050
* | Follow OMEMO policy even when opening window on message and carbon receptionPaul Fariello2019-04-171-0/+14
|/ | | | This should close #1052
* Try to start sessions with every jid in rosterPaul Fariello2019-04-101-0/+4
|
* Wait for discovery end to publish omemo devicelist and bundlePaul Fariello2019-04-102-0/+9
| | | | Add sv_ev_connection_features_received for that purpose
* Rework MUC reflected message filteringPaul Fariello2019-04-103-13/+11
| | | | | | | | | Reflected messages can't be filtered by nick only otherwise you might ignore messages comming from you on another devices. Consequently we maintain a list of sent messages id in mucwin. To be sure the id will be correctly reflected we use the origin-id stanza.
* Ensure encrypted carbon of own message are marked as encryptedPaul Fariello2019-04-102-3/+39
|
* Add support for disconnect in OMEMOPaul Fariello2019-04-101-0/+3
|
* Log and print outgoing encrypted messagePaul Fariello2019-04-103-18/+81
|
* Add support for sending encrypted message in MUCPaul Fariello2019-04-101-4/+19
|
* Handle decrypted OMEMO messages as suchPaul Fariello2019-04-101-4/+90
|
* Add support for OMEMO, OTR, PGP built togetherPaul Fariello2019-04-101-4/+93
|
* Add support for encrypted carbonPaul Fariello2019-04-102-2/+2
| | | | Fix {signed,}_pre_key store
* Add OMEMO identity materials long term storagePaul Fariello2019-04-101-0/+8
|
* Follow normal workflow for OMEMO message receptionPaul Fariello2019-04-102-2/+2
| | | | | | We try to decrypt all messages, if it's successful we use sv_ev_incoming_message even for OMEMO messages. We pass an OMEMO boolean to let UI be aware that message were encrypted.
* Add OMEMO message encryption and decryptionPaul Fariello2019-04-101-0/+19
|
* Redraw screen after entry of PGP secret keyMichael Vetter2019-02-201-0/+10
| | | | | | | | | | | | | | | | | | | | | | After specifying the PGP key ID with pgp.keyid within the accounts file on startup profanity asks for the secret key passphrase. It then doesn't redraw the screen, leaving it in an odd looking state. This probably only happens with pinentry-curses since it draws in screen. We need this fix for cli only environments. Fixes https://github.com/boothj5/profanity/issues/906 reported by Bob Mottram. Based on https://github.com/boothj5/profanity/pull/908 by Bob Mottram Bob removed his GitHub account, so GitHub created a ghost placeholder user for him, which unfortunately makes it impossible to cherry-pick this commit. To more or less preserve authorship I added him as co-author. Commit picked and message edited by jubalh. Co-authored-by: Bob Mottram <bob@freedombone.net>
* Update copyright to include 2019Michael Vetter2019-01-224-4/+4
|
* Merge pull request #926 from msantos/null-pointer-dereferenceMichael Vetter2018-07-301-6/+8
|\ | | | | server_events: fix potential NULL pointer deref
| * server_events: fix potential NULL pointer derefMichael Santos2017-04-121-6/+8
| |
* | Add preferences for tab displayJames Booth2018-03-091-2/+2
| |
* | Show name in statusbar tabs WIPJames Booth2018-03-081-2/+2
| |
* | Add /rooms service autocompletionJames Booth2018-02-052-0/+8
| |
* | Update copyrightJames Booth2018-01-214-4/+4
|/
* Update CopyrightJames Booth2017-01-284-4/+4
|
* Add pre chat and room message blockingJames Booth2017-01-221-0/+6
|
* Fix compileJames Booth2017-01-161-1/+1
|
* Remove status from cl_ev_presence_sendJames Booth2017-01-153-7/+12
| | | | fixes #888
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-06 05:02:31 +0000