aboutsummaryrefslogtreecommitdiff
path: root/tests/qxmppsasl
Commit message (Collapse)AuthorAgeFilesLines
* SaslDigestMd5: Fix UB when at the end of input byte array [Qt6 only]Linus Jahn2023-03-091-0/+10
| | | | | | Also adds a unit test. Fixes #541.
* Disable Qt keywords completelyLinus Jahn2022-12-261-27/+27
| | | | | | | | | | | | | | | Previously we had the policy that no qt keywords were allowed in headers that may be included by users. However since there was no automatic test verifying that in some places keywords were still used. This now disables qt keywords completely, also in tests and examples. Qt keywords are in general no good or really good idea as they even conflict with the standard library (`emit` at least). In some cases in the examples I just removed the slot tag if the functions didn't need to be slots (anymore). Closes #503.
* Convert copyright headers to REUSELinus Jahn2022-01-141-22/+3
|
* Update copyright years (2022 edition)Linus Jahn2022-01-091-1/+1
|
* Update copyright headers to 2021Linus Jahn2021-02-191-1/+1
|
* Add SCRAM-SHA3-512 SASL algorithmLinus Jahn2020-10-311-0/+3
| | | | | QCryptographicHash::Sha3_512 was accidentially using Keccak-512 before Qt 5.9.2, thus we can only use SCRAM-SHA3-512 when using Qt >= 5.9.2.
* Add SCRAM-SHA-512 SASL algorithmLinus Jahn2020-10-311-0/+1
|
* SaslClientScram: Refactor to simplify adding new algorithmsLinus Jahn2020-10-311-8/+12
| | | | Adding new algorithms only needs a new name/algorithm entry now.
* Run clang-format also on all cpp filesLinus Jahn2020-02-031-2/+10
|
* Bump copyright year to 2020Linus Jahn2020-01-061-1/+1
|
* [sasl] order mechanisms to prefer the most secureJeremy Lainé2019-01-181-1/+1
| | | | | | | | | | | | | | | | | | 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
* [sasl] add support for SCRAM-SHA-1 and SCRAM-SHA-256Jeremy Lainé2019-01-171-1/+92
|
* Bump copyright year to 2019Jeremy Lainé2019-01-081-1/+1
|
* Fix qxmppsasl testNiels Ole Salscheider2017-09-041-1/+1
|
* Port tests to the new build systemNiels Ole Salscheider2017-09-041-3/+0
|
* update project homepageJeremy Lainé2014-03-281-1/+1
|
* update project homepageJeremy Lainé2014-03-271-1/+1
|
* update copyright notice to 2008-2014Jeremy Lainé2014-03-261-1/+1
|
* fixJeremy Lainé2012-09-271-41/+31
|
* add missing fileJeremy Lainé2012-09-271-0/+3
|
* move sasl test codeJeremy Lainé2012-09-271-0/+447