about summary refs log tree commit diff stats
path: root/src/xmpp
Commit message (Collapse)AuthorAgeFilesLines
* form.c: fix memleak in form_tag_existsMichael Vetter2021-03-171-0/+1
|
* Add support to approve MUC voice requestsMichael Vetter2021-03-173-2/+52
| | | | | | A form will open. One can then use `/field4 on` `/form submit`. Implements https://github.com/profanity-im/profanity/issues/1507
* MUC: Add voice requestThorben Günther2021-03-124-1/+77
| | | | closes https://github.com/profanity-im/profanity/issues/1211
* Merge pull request #1501 from xenrox/change-passwordMichael Vetter2021-03-115-1/+87
|\ | | | | Add command to change password of logged in user
| * Add command to change password of logged in userThorben Günther2021-03-115-1/+87
| |
* | Update to the newest version of XEP 0363 (HTTP Upload)Maximilian Wuttke2021-03-113-36/+35
|/ | | | | | | | | | | | | Main changes: 1. Attributes instead of tags 2. Read the optional <header> tags and send them in the HTTP PUT header: * Authorization * Cookie * Expires Co-authored-by: Martin Dosch <martin@mdosch.de>
* [OMEMO]: Fix bundle publishingMaximilian Wuttke2021-03-091-14/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | Use the following options in `omemo_bundle_publish()`: - "pubsub#persist_items" = "true" - "pubsub#access_model" = "open" The same options are also used in Gajim. I've tested this on two different servers. The bundle was successfully added as a new PEP node. Test cases: 1. Normal use on my main account 2. Log in into a fresh tesst account on a different server 3. `/omemo clear_device_list`. In this case, the client(s) may have to be restarted. Note: In `_omemo_bundle_publish_result`, there's a route that is taken when the bundle publish stanza failed. In this case, the node is configured manually, i.e. the access_model is set to 'open'. I have manually tested this case, but this case didn't naturally occur for me. Note: The option "pubsub#max_items=max" is REQUIRED for the bundle publication, as per XEP-0384. However, this is not done in other clients (I've checked the source code of Gajim and Conversations), and it is also not supported by Prosody. Cf. <https://github.com/xsf/xeps/pull/988>.
* Logging [OMEMO]Maximilian Wuttke2021-03-091-1/+26
| | | | | Also "handle" some errors in `_omemo_bundle_publish_configure` if the stanzas can't be found
* Variadic version of `stanza_attach_publish_options`Maximilian Wuttke2021-03-092-16/+37
|
* Logging [OMEMO]Maximilian Wuttke2021-03-091-6/+10
|
* Logging [CONNECTION]Stefan2021-03-091-0/+1
|
* Remove forgotten debug lineMichael Vetter2021-02-151-1/+0
|
* Use correct time for MAM messagesMichael Vetter2021-02-041-8/+17
| | | | | | We need the delay value from the <forward> element. Regards https://github.com/profanity-im/profanity/issues/660
* Enable error logging on MAM RSMMichael Vetter2021-01-281-4/+1
|
* Get MAM from last 7 daysMichael Vetter2021-01-281-1/+1
| | | | Probably should make this configurable later.
* MAM: Request more pages via RSMMichael Vetter2021-01-281-6/+22
| | | | Send another request with same jid and last id we got.
* Adapt MAM RSM code to latest functionsMichael Vetter2021-01-281-3/+3
| | | | | | Some functions changed in the meantime. stanza_get_child_by_name_and_ns() got dropped and xmpp_stanza_get_child_by_name_and_ns() from newer libstrophe is used.
* wip: add rsm after we get the first couple of mam messagesMichael Vetter2021-01-283-5/+46
|
* mam: Use correct ID in rsm handlerMichael Vetter2021-01-281-3/+1
| | | | Thanks to DebXWoody for the help.
* mam: fix logging messageMichael Vetter2021-01-281-1/+1
|
* Start working on MAM RSM to get more pagesMichael Vetter2021-01-282-1/+27
| | | | Regards https://github.com/profanity-im/profanity/issues/660
* Update copyrightMichael Vetter2021-01-085-5/+5
|
* Remove not needed includeMichael Vetter2020-12-161-1/+0
|
* Fix various typosMichael Vetter2020-12-103-5/+5
|
* Declare counter var inside loopMichael Vetter2020-11-092-10/+5
| | | | We require c99/gnu99 anyways.
* Print all error stanzasMichael Vetter2020-10-301-5/+5
| | | | | | | | | | | | | | | | | | Regards https://github.com/profanity-im/profanity/issues/1435 So far we didn't print the error if it contained `<error type="cancel">`. It appears that the code always thought this is a service-not-available (so one is either blocked or the account doesn't exist) and printed `Recipient not found`. But there can be other errors as well. Like in above mentioned issue `not-allowed`. Let's just print the text. In case of the cancel type we still remove the jid from the chat sessions. I'm not entirely sure whether this needs to be done in other cases too.
* Fixed Date format for MAM requestDebXWoody2020-10-281-2/+2
| | | | | | | | | Using g_date_time_new_now_utc instead of g_date_time_new_now_local Using g_date_time_format(timestamp, "%FT%TZ") instead of "%FT%T%:::z" Edit: DebXWoody created this patch because ejabberd returned an error with the old date format.
* xmpp/bookmark: don't use uninitialised fieldDmitry Podgorny2020-10-191-0/+1
| | | | | | | | | | When a bookmark is created with '/bookmark add' command, ext_gajim_minimize remains uninitialised in new bookmark object and is read further in _send_bookmarks(). Initialise the field with 0. Fixes #1432.
* Since the string from strerror should never be modified, use const.Philipp Klaus Krause2020-10-141-1/+1
|
* Enable _handle_ox_chat() payload/body decryptionMichael Vetter2020-10-091-3/+0
| | | | | This part of the code was waiting for xmpp_stanza_new_from_string() from libstrophe 0.10.0.
* Replace stanza_get_child_by_name_and_ns with ↵Michael Vetter2020-09-306-32/+10
| | | | | | | | xmpp_stanza_get_child_by_name_and_ns Replace our own stanza_get_child_by_name_and_ns() with the upstreamed xmpp_stanza_get_child_by_name_and_ns() provided by the new libstrophe/libmesode 0.10.0.
* Require libstrophe/libmesode 0.10.0Michael Vetter2020-09-301-8/+0
|
* Fix memory leak in _handle_chat()Dmitry Podgorny2020-08-071-21/+7
| | | | | jid_create() for attribute "to" was called twice and the 1st object was lost.
* Parse stanza-idMichael Vetter2020-07-233-6/+40
| | | | | | | | | | | | Add stable stanza IDs to ProfMessage struct. We parse this for 1:1 messages (MUC needs to be done too). <stanza-id> for live messages <result id="x"> for MAM messages Regards MAM: https://github.com/profanity-im/profanity/issues/660 Regards Stable IDs: https://github.com/profanity-im/profanity/issues/1207
* ox review: Use english not germanMichael Vetter2020-07-101-5/+5
|
* OX: XEP-0373: OpenPGP for XMPP - Version 0.5.0 (2020-06-19)DebXWoody2020-07-102-3/+241
| | | | | | | | | | | Discovering Public Keys via PEP * 4.3 Discovering Public Keys of a User * 4.4 Requesting Public Keys * Import Public Keys into GnuPG's local keyring. Issue: #1331
* Apply coding styleMichael Vetter2020-07-0739-3203/+3233
|
* OX: Fix testsMichael Vetter2020-07-071-1/+2
| | | | | | | | Fix: ``` /usr/bin/ld: src/xmpp/ox.o: in function `ox_announce_public_key': src/xmpp/ox.c:90: undefined reference to `p_ox_gpg_readkey' ```
* Revert "Apply coding style"Michael Vetter2020-07-0739-3321/+3295
| | | | | | This reverts commit 9b55f2dec0ea27a9ce4856e303425e12f866cea2. Sorting the includes creates some problems.
* Apply coding styleMichael Vetter2020-07-0739-3295/+3321
| | | | Regards https://github.com/profanity-im/profanity/issues/1396
* OX: Announce public key on PEPDebXWoody2020-07-063-0/+287
| | | | | | | | | | | | | | | src/pgp/gpg.c:p_ox_gpg_readkey Used to read a public key from a file. The function will return the fingerprint of the file and the base64 encoded key. src/xmpp/ox.[hc] ox_announce_public_key(const char* const filename) can be called from the /ox announce <filename> command. The key within the file will be pushed on PEP and the Metadata node will be set. Issue: #1331
* Merge branch 'omemofix'Michael Vetter2020-07-041-20/+39
|\
| * Messages are not shown in ChatSecureDebXWoody2020-07-041-20/+39
| | | | | | | | | | | | | | | | In 0.9.x we fixed an issue, because OMEMO devices should be defined in "item" with id "current". This should work, but it won't work if there is no "current". If there is no "current" we will just use the first item. Issue #1384
* | message.c: Use message->to_jid instead of to_jidMichael Vetter2020-07-031-1/+1
| | | | | | | | This one will always be set.
* | message.c: _handle_carbons() check from field outside of functionMichael Vetter2020-07-031-15/+17
| | | | | | | | | | So that we don't have to pass the wrapping stanza and can handle the error nicer.
* | message.c: Dont duplicate code in _handle_carbon and _handle_chatMichael Vetter2020-07-031-111/+66
| | | | | | | | | | Trying to simplify the conditions so we don't have duplicate code in both of those functions.
* | message.c: Remove from/to setting out of conditionMichael Vetter2020-07-031-6/+3
| | | | | | | | Since its done in both cases.
* | message.c: Small code improvementsMichael Vetter2020-07-031-16/+16
| |
* | message.c: Put XEP-0085 code in helper functionMichael Vetter2020-07-031-18/+25
| |
* | Change formattingMichael Vetter2020-07-031-1/+2
| |
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-09-06 23:33:09 +0000