| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | SaslDigestMd5: Fix UB when at the end of input byte array [Qt6 only] | Linus Jahn | 2023-03-09 | 1 | -0/+10 |
| | | | | | | | Also adds a unit test. Fixes #541. | ||||
| * | Disable Qt keywords completely | Linus Jahn | 2022-12-26 | 1 | -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 REUSE | Linus Jahn | 2022-01-14 | 1 | -22/+3 |
| | | |||||
| * | Update copyright years (2022 edition) | Linus Jahn | 2022-01-09 | 1 | -1/+1 |
| | | |||||
| * | Update copyright headers to 2021 | Linus Jahn | 2021-02-19 | 1 | -1/+1 |
| | | |||||
| * | Add SCRAM-SHA3-512 SASL algorithm | Linus Jahn | 2020-10-31 | 1 | -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 algorithm | Linus Jahn | 2020-10-31 | 1 | -0/+1 |
| | | |||||
| * | SaslClientScram: Refactor to simplify adding new algorithms | Linus Jahn | 2020-10-31 | 1 | -8/+12 |
| | | | | | Adding new algorithms only needs a new name/algorithm entry now. | ||||
| * | Run clang-format also on all cpp files | Linus Jahn | 2020-02-03 | 1 | -2/+10 |
| | | |||||
| * | Bump copyright year to 2020 | Linus Jahn | 2020-01-06 | 1 | -1/+1 |
| | | |||||
| * | [sasl] order mechanisms to prefer the most secure | Jeremy Lainé | 2019-01-18 | 1 | -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-256 | Jeremy Lainé | 2019-01-17 | 1 | -1/+92 |
| | | |||||
| * | Bump copyright year to 2019 | Jeremy Lainé | 2019-01-08 | 1 | -1/+1 |
| | | |||||
| * | Fix qxmppsasl test | Niels Ole Salscheider | 2017-09-04 | 1 | -1/+1 |
| | | |||||
| * | Port tests to the new build system | Niels Ole Salscheider | 2017-09-04 | 1 | -3/+0 |
| | | |||||
| * | update project homepage | Jeremy Lainé | 2014-03-28 | 1 | -1/+1 |
| | | |||||
| * | update project homepage | Jeremy Lainé | 2014-03-27 | 1 | -1/+1 |
| | | |||||
| * | update copyright notice to 2008-2014 | Jeremy Lainé | 2014-03-26 | 1 | -1/+1 |
| | | |||||
| * | fix | Jeremy Lainé | 2012-09-27 | 1 | -41/+31 |
| | | |||||
| * | add missing file | Jeremy Lainé | 2012-09-27 | 1 | -0/+3 |
| | | |||||
| * | move sasl test code | Jeremy Lainé | 2012-09-27 | 1 | -0/+447 |
