xavi/qxmpp/src/client/QXmppConfiguration.cpp, branch fork
Fork of the QXmpp library.
https://gitea.privatedns.org/xavi/qxmpp/atom?h=fork
2022-12-28T20:57:11+00:00
Configuration: Minor documentation improvements
2022-12-28T20:57:11+00:00
Linus Jahn
lnj@kaidan.im
2022-12-28T20:57:11+00:00
urn:sha1:3dd4267a5842d5b956dd79633fa2c8b81fb80d53
Reformat code
2022-09-05T22:46:56+00:00
Linus Jahn
lnj@kaidan.im
2022-09-05T18:37:05+00:00
urn:sha1:5f813f8a4bbe1e075daad7b3933829044befffb4
Run 'clang-format' on all files
2022-01-15T13:04:15+00:00
Melvin Keskin
melvo@olomono.de
2022-01-08T08:26:46+00:00
urn:sha1:fd11e024a6079be3e0bc62911b6e3070c7553224
Convert copyright headers to REUSE
2022-01-14T21:41:49+00:00
Linus Jahn
lnj@kaidan.im
2022-01-14T21:41:49+00:00
urn:sha1:37359c7928d7fad38f064b6b5f26af59440ed7f9
Update copyright years (2022 edition)
2022-01-09T16:38:42+00:00
Linus Jahn
lnj@kaidan.im
2022-01-09T16:38:42+00:00
urn:sha1:33eea347565352fcc85d8229e33bf9039f2f0402
Update copyright headers to 2021
2021-02-19T15:04:54+00:00
Linus Jahn
lnj@kaidan.im
2021-02-19T15:04:54+00:00
urn:sha1:0b0d73cc4b3edd548221594efdda42c2fb518770
Run clang-format also on all cpp files
2020-02-02T23:11:55+00:00
Linus Jahn
lnj@kaidan.im
2020-02-02T17:14:27+00:00
urn:sha1:57f1b775197aed1d32e98b0299c0999339a7d5f6
clang-format: Enable regrouping and sorting of includes
2020-02-02T23:11:55+00:00
Linus Jahn
lnj@kaidan.im
2020-02-02T17:13:26+00:00
urn:sha1:99b850a3008bbb03d3449d683adb87839f7d5c4b
Bump copyright year to 2020
2020-01-06T18:39:13+00:00
Linus Jahn
lnj@kaidan.im
2020-01-06T18:38:49+00:00
urn:sha1:81b590545c590840f99fa5a96460726cb16db88a
[sasl] order mechanisms to prefer the most secure
2019-01-18T13:02:50+00:00
Jeremy Lainé
jeremy.laine@m4x.org
2019-01-17T22:25:37+00:00
urn:sha1:2a34abcd74d8d8369d81d9e4131d34185d9154a5
The previous logic was:
- use the preferred SASL mechanism if available
- otherwise use the first supported mechanism offered by the server
However RFC 6120, section 6.3.3 states:
"The initiating entity MUST maintain its own preference order independent
of the preference order of the receiving entity."
The new logic is:
- order our supported mechanisms from most secure to least secure
- if the user sets QXmppConfiguration::saslMechanism, put it first
- use the best mechanism supported by the server