about summary refs log tree commit diff stats
path: root/src/xmpp/connection.c
Commit message (Collapse)AuthorAgeFilesLines
* Add command to change password of logged in userThorben Günther2021-03-111-0/+13
|
* Logging [CONNECTION]Stefan2021-03-091-0/+1
|
* Require libstrophe/libmesode 0.10.0Michael Vetter2020-09-301-8/+0
|
* Apply coding styleMichael Vetter2020-07-071-88/+114
|
* Revert "Apply coding style"Michael Vetter2020-07-071-118/+92
| | | | | | This reverts commit 9b55f2dec0ea27a9ce4856e303425e12f866cea2. Sorting the includes creates some problems.
* Apply coding styleMichael Vetter2020-07-071-92/+118
| | | | Regards https://github.com/profanity-im/profanity/issues/1396
* Fix reading/writing linked filesMichael Vetter2020-06-131-1/+1
| | | | | | "base" was not really base but the filename :-) Fix https://github.com/profanity-im/profanity/issues/1362
* Make legacy auth optionalDmitry Podgorny2020-06-111-0/+9
| | | | | | | | Some systems don't provide recent libstrophe releases. When older version of libstrophe is detected, don't build legacy auth support. To simplify this patch, report about unsupported legacy auth and keep commands option as is.
* Add option for legacy authenticationDmitry Podgorny2020-06-051-6/+28
| | | | | | | | New options: /connect <account> [auth default|legacy] /account <account> set auth default|legacy Fixes #1236.
* Add and use connection_get_barejid()Michael Vetter2020-05-251-0/+12
| | | | Instead of connection_get_fulljid() and then creating a Jid from it.
* Add vim modelineMichael Vetter2019-11-131-0/+1
|
* Display ownership of connection_get_profanity_identifierMichael Vetter2019-10-221-1/+1
|
* Use UUID in origin-id and idMichael Vetter2019-10-221-5/+5
| | | | | Let's use UUID to have a more random string then just 10 alphanumeric values.
* Set prof_ident to NULL after freeMichael Vetter2019-10-211-1/+2
| | | | | | | | | | | | | | | | | | This caused the bug mentioned in the PR comment: ``` It seems with the changes done here we get a crash in: src/xmpp/message.c message_handlers_init() when looking up handlers: ProfMessageHandler *handler = g_hash_table_lookup(pubsub_event_handlers, curr->data);. Steps to reproduce: open Profanity and connect /autoping set 10 /autoping timeout 10 stop WiFi/connection wait for Lost connection restart wifi /connect ```
* Rename _calculate_identifier to _compute_identifierMichael Vetter2019-10-201-3/+3
|
* Rename random_bytes to profanity_instance_idMichael Vetter2019-10-191-6/+6
|
* Free hmac and msgidMichael Vetter2019-10-191-0/+3
|
* Free prof_identifier in case of reconnectMichael Vetter2019-10-191-0/+3
| | | | Bedore we assign it new.
* Change origin-id/id algoMichael Vetter2019-10-181-10/+10
| | | | | Hash twice. Use HMAC SHA256 from glib.
* Log incoming MUC messages if origin-id sais they dont come from usMichael Vetter2019-10-181-10/+7
| | | | Regards https://github.com/profanity-im/profanity/issues/1201
* Remove prefix from stanza idMichael Vetter2019-10-171-1/+1
| | | | | We sent `prof_prefix_uuid` as id. Where the prefix was also optional. We don't need this at all.
* Change algo for connection_create_stanza_id()Michael Vetter2019-10-171-7/+11
|
* Change connection_create_stanza_id()Michael Vetter2019-10-171-11/+11
| | | | | To return identifier and uuid together. We can remove the prefix later on.
* Calculate identifier upon connectMichael Vetter2019-10-161-5/+28
| | | | | | | This will be needed so that we can later detect if messages (origin-in) was sent by us. Regards https://github.com/profanity-im/profanity/issues/1207
* Rename identification fileMichael Vetter2019-10-161-1/+2
|
* Use random string for random-bytes identifierMichael Vetter2019-10-161-4/+5
| | | | | | And rename `instance` to `identifier`. Regards https://github.com/profanity-im/profanity/issues/1207
* Create random-bytes fileMichael Vetter2019-10-161-0/+53
| | | | | | | | | | So far only with dummy value. We will need an identifier that we can hash together with a message ID and put in as the origin-id. So when we receive message we can unsplit it and see if it was sent from this client. Regards https://github.com/profanity-im/profanity/issues/1207
* Fix various OMEMO memleaksPaul Fariello2019-07-101-2/+4
|
* xmpp/connection: fix #1103Dmitry Podgorny2019-06-011-11/+28
| | | | | | | | | | | | When connection is lost, profanity tries to disconnect what leads to an infinite loop. The loop occurs, because connection_disconnet() runs xmpp_run_once() separately and waits for XMPP_CONN_DISCONNECT event. But it doesn't happen, because the connection object is disconnected. As solution, don't disconnect after XMPP_CONN_DISCONNECT is received. Also, don't free libstrophe objects while the event loops executes, because the event loop continues using objects after callbacks quit.
* Wait for discovery end to publish omemo devicelist and bundlePaul Fariello2019-04-101-0/+23
| | | | Add sv_ev_connection_features_received for that purpose
* Update copyright to include 2019Michael Vetter2019-01-221-1/+1
|
* Add option to trust server's certificateDmitry Podgorny2018-11-061-0/+3
| | | | | | | | | | | New tls policy "trust" added to /connect and /account. With the policy TLS connection is established even with invalid certificate. Note, that trust policy forces TLS connection and it fails when server doesn't support TLS. Examples: /connect <jid> tls trust /account <name> set tls trust
* Move ID generation to xmpp folderMichael Vetter2018-08-301-0/+21
| | | | | | | | | | | create_unique_id() was changed to use UUIDs instead of a counter in the last commit. Since now it depends on connection_create_uuid() which is in the xmpp subfolder the function should also be moved there. Renamed it to connection_create_stanza_id() and moved it to src/xmpp/connection.c. Discussion happened in https://github.com/boothj5/profanity/pull/1010
* Update copyrightJames Booth2018-01-211-1/+1
|
* Legacy SSL supportDmitry Podgorny2017-06-241-0/+2
| | | | | | | | | | | | | | | | Add "legacy" tls policy to /account and /connect commands. When this policy is specified the connection is connected with XMPP_CONN_LEGACY_SSL flag. Notice, legacy SSL and STARTTLS are not compatible and user has to know when exactly the new policy should be used. To enable it, run one of the next commands: /connect <jid> tls legacy [server <host>] /account <name> set tls legacy Notice, there is no SRV record for legacy SSL. Therefore, you may need "server" property to connect successfully. Refer to configuration provided by your server.
* Update CopyrightJames Booth2017-01-281-1/+1
|
* Allow clearing account resourceJames Booth2016-11-221-14/+14
| | | | issue #880
* Use server features for account muc serviceJames Booth2016-11-201-0/+4
| | | | issue #878
* Add /tls certpath defaultJames Booth2016-10-171-2/+2
| | | | issue #871
* Free hashtable key list in connection_jid_for_feature()James Booth2016-09-051-0/+1
|
* Tidy headersJames Booth2016-07-241-0/+1
|
* Move event timeout to connection moduleJames Booth2016-07-241-1/+7
|
* Update GPL link in headersJames Booth2016-07-241-1/+1
|
* Check for NULL before clearing connection dataJames Booth2016-06-011-3/+7
|
* Add connection_set_disconnected()James Booth2016-05-111-18/+8
|
* Add connection_clear_data()James Booth2016-05-101-17/+12
|
* Remove connection_free_conn(), connection_free_ctx()James Booth2016-05-101-18/+10
|
* Add connection_shutdown()James Booth2016-05-101-7/+11
|
* Remove JABBER_STARTED, JABBER_UNDEFINED connection statesJames Booth2016-05-101-1/+12
|
* Remove _session_free_session_data from session.cJames Booth2016-05-101-1/+2
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-06-30 05:17:27 +0000