| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It was a great ride!
IDs look instead of
`TE5BTDc2ZTc3YTMwZGU3MDgzMzllOTliNGExNjVmMjZkMTY1ZmUyZGEyNTUxMjVmODBkMmQzOGMxYWI2ZjAxNzdiM2Q=`
more like `7HcnNSoO1MVvb0p9a9e293152922853e910b8b1a65bb26e225a0568` now.
Regards https://github.com/profanity-im/profanity/issues/1520
We still has our identifier into it to filter MUC reflected messages.
profident maybe should be changed to be longer or be generated upon each
start.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This reverts commit 9b55f2dec0ea27a9ce4856e303425e12f866cea2.
Sorting the includes creates some problems.
|
|
|
|
| |
Regards https://github.com/profanity-im/profanity/issues/1396
|
|
|
|
|
|
| |
"base" was not really base but the filename :-)
Fix https://github.com/profanity-im/profanity/issues/1362
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
New options:
/connect <account> [auth default|legacy]
/account <account> set auth default|legacy
Fixes #1236.
|
|
|
|
| |
Instead of connection_get_fulljid() and then creating a Jid from it.
|
| |
|
| |
|
|
|
|
|
| |
Let's use UUID to have a more random string then just 10 alphanumeric
values.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
```
|
| |
|
| |
|
| |
|
|
|
|
| |
Bedore we assign it new.
|
|
|
|
|
| |
Hash twice.
Use HMAC SHA256 from glib.
|
|
|
|
| |
Regards https://github.com/profanity-im/profanity/issues/1201
|
|
|
|
|
| |
We sent `prof_prefix_uuid` as id. Where the prefix was also optional.
We don't need this at all.
|
| |
|
|
|
|
|
| |
To return identifier and uuid together.
We can remove the prefix later on.
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
| |
And rename `instance` to `identifier`.
Regards https://github.com/profanity-im/profanity/issues/1207
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Add sv_ev_connection_features_received for that purpose
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
issue #880
|
|
|
|
| |
issue #878
|
|
|
|
| |
issue #871
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|