about summary refs log tree commit diff stats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
...
* | 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
|
* Merge pull request #1090 from jubalh/fix/connection-loss-1089Michael Vetter2019-05-061-0/+5
|\ | | | | Reset things on connection loss
| * 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 #1084 from jubalh/occupants-charMichael Vetter2019-05-038-3/+93
|\ \ | |/ |/| Add occupants char
| * Add occupants charMichael Vetter2019-05-028-3/+93
| | | | | | | | | | | | | | `/occupants char` now sets a character that is displayed before the nick in MUCs. Similar like `/roster char` is displaying a char for the roster. Regards #690
* | Update tests with new URLMichael Vetter2019-05-031-1/+1
| | | | | | | | https://github.com/profanity-im/profanity/issues/1085
* | Update profanity URL in entity capabilities stanzaMichael Vetter2019-05-031-1/+1
| | | | | | | | Regards https://github.com/profanity-im/profanity/issues/1085
* | Update profanity URL in /tiny exampleMichael Vetter2019-05-031-1/+1
| | | | | | | | Regards https://github.com/profanity-im/profanity/issues/1085
* | Check for new profanity version using new URLMichael Vetter2019-05-032-2/+2
|/ | | | Regards https://github.com/profanity-im/profanity/issues/1085
* OMEMO: Initialize result in omemo_automatic_startMichael Vetter2019-04-291-1/+1
| | | | | | | | | This is actually not needed because result will always be set. hartmann had problems building profanity on OpenBSD and he proposed this patch. Let's use it to make the compiler happy there.
* OMEMO: Check if ID is present before using itMichael Vetter2019-04-241-1/+5
| | | | Fixes https://github.com/boothj5/profanity/issues/1079
* Fix statusbar number in themeMichael Vetter2019-04-241-1/+1
| | | | There is a typo here. So this actually never worked ;-)
* Fix formatting for privileges onMichael Vetter2019-04-241-0/+4
| | | | | `/privileges on` lists `Moderator`, `Visitor` etc. Formatting was wrong here. Printing privilige followed by nickaname in the same line.
* Occupantswin: handle newline correctlyMichael Vetter2019-04-241-6/+6
|
* Add occupants wrap to helpMichael Vetter2019-04-241-2/+4
|
* Fix occupants header char messageMichael Vetter2019-04-241-2/+2
|
* Add occupants wrap optionMichael Vetter2019-04-247-2/+33
| | | | | | | Wrapping for the occupants panel like already exists for the roster panel. See `/occupants wrap on`. Regards https://github.com/boothj5/profanity/issues/690
* Update copyright yearskaffeekanne2019-04-241-1/+1
|
* Put occupants update into own functionMichael Vetter2019-04-233-34/+21
|
* Add occupants header charMichael Vetter2019-04-238-6/+154
| | | | | | | | `/occupants header char` now sets a character that is displayed before the role (moderator, visitor..) in a room. Similar to `/roster header char` is displaying a char for the roster. Regards https://github.com/boothj5/profanity/issues/690
* Fix indentation for time configkaffeekanne2019-04-231-2/+2
|
* Adjust jid for occupants indentMichael Vetter2019-04-201-3/+11
| | | | Indent the jid one more space than nick.
* Add occupants indent autocompletionMichael Vetter2019-04-201-0/+1
|
* Allow setting occupants indent outside of MUCMichael Vetter2019-04-202-34/+31
| | | | And when not connected.
* Add /occupants indent commandMichael Vetter2019-04-187-3/+80
| | | | | | | | Roster has a `/roster contact indent` option. Now we have the same for occupants. So contacts in roster and in MUC can have configurable indentation. Regards https://github.com/boothj5/profanity/issues/690
* Fix typo in /help rosterMichael Vetter2019-04-181-1/+1
|
* Merge pull request #1063 from paulfariello/hotfix/presence-before-rosterMichael Vetter2019-04-173-0/+45
|\ | | | | Handle presence received before roster
| * Handle presence received before rosterPaul Fariello2019-04-173-0/+45
| | | | | | | | | | | | | | | | | | | | 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
* | Set correct year in copyright displayMichael Vetter2019-04-171-1/+1
| | | | | | | | Fixes https://github.com/boothj5/profanity/issues/1069
* | Follow OMEMO policy even when opening window on message and carbon receptionPaul Fariello2019-04-171-0/+14
|/ | | | This should close #1052
* Handle MUC anonymous state when auto starting OMEMOPaul Fariello2019-04-172-3/+15
| | | | | | | When auto joining a MUC we don't have access to required information so we just don't start OMEMO at this time. Once we receive disco info we then try to start OMEMO.
* Handle missing real jid in OMEMO encrypted MUCPaul Fariello2019-04-171-3/+7
| | | | | | | This should never happens since we should ensure MUC is Non-Anonymous before enabling OMEMO. But we should neither segfault if this happens.
* Add OMEMO policyPaul Fariello2019-04-1717-23/+253
| | | | | | | | | | | | There is 3 policy: - manual: OMEMO session are only started manually - automatic: OMEMO session are only started if they have been started manually before - always: OMEMO session are always started unless they have been ended manually before Closes #1040 and fixes #1052
* Merge pull request #1066 from ↵Michael Vetter2019-04-173-6/+33
|\ | | | | | | | | paulfariello/hotfix/OMEMO-ensure-muc-is-nonanonymous Ensure MUC is Non-Anonymous before starting OMEMO
| * Ensure MUC is Non-Anonymous before starting OMEMOPaul Fariello2019-04-173-6/+33
| | | | | | | | | | | | Store MUC anonymous type in mucwin for that purpose. Fixes #1065
* | Alert about long OMEMO cryptographic generationPaul Fariello2019-04-171-0/+1
|/ | | | Fixes #1055
* Merge pull request #1061 from ↵Michael Vetter2019-04-151-1/+1
|\ | | | | | | | | paulfariello/hotfix/handle-message-without-id-in-muc Handle message without id in MUC
| * Handle message without id in MUCPaul Fariello2019-04-141-1/+1
| | | | | | | | Some clients seems to send message without id.
* | Don't persist OMEMO {signed,}prekey cleaning on disconnectPaul Fariello2019-04-141-10/+0
| | | | | | | | | | We should not remove signed prekey and prekey from persistent storage when cleaning OMEMO store on disconnect.
* | Handle malformed OMEMO identity.txtPaul Fariello2019-04-141-7/+34
| | | | | | | | | | If OMEMO identity.txt is malformed just abort loading. User should be able to call `/omemo gen` again.
* | Don't unload OMEMO cryto on disconnect if OMEMO wasn't loadedPaul Fariello2019-04-141-0/+4
|/ | | | | | | If OMEMO wasn't loaded, removing key would create empty identity.txt file. Then at load time it would segfault profanity. Another commit should fix load of malformed identity.txt.
* Add random string at the end of the default resourcePaul Fariello2019-04-124-3/+27
| | | | | | | | When connecting for the first time or when creating a new account don't use only 'profanity' as default resource. Some server don't support having 2 connection with same resource. Using profanity as default lead to deconnections.
* Support contact name in /omemo fingerprint commandPaul Fariello2019-04-101-4/+9
|
* Fix issue with first encrypted messagePaul Fariello2019-04-101-1/+5
| | | | | | | | When decrypting first message with prekey, libsignal wants to remove used prekey from storage. Return value on success should be 0. We used to return number of deleted keys. Thus libsignal was considering we failed to remove the key and we were ignoring plaintext.
* Try to start sessions with every jid in rosterPaul Fariello2019-04-103-0/+22
|
* OMEMO should be written uppercasePaul Fariello2019-04-101-10/+10
|
* Fix build on travisPaul Fariello2019-04-101-0/+2
|
* Add /omemo char commandPaul Fariello2019-04-103-1/+25
|
* Automatically starts OMEMO if one identity is trustedPaul Fariello2019-04-103-6/+74
|