| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Disable Qt keywords completely | Linus Jahn | 2022-12-26 | 1 | -9/+8 |
| | | | | | | | | | | | | | | | | 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. | ||||
| * | Reformat code | Linus Jahn | 2022-09-06 | 1 | -1/+2 |
| | | |||||
| * | 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 |
| | | |||||
| * | Run clang-format also on all cpp files | Linus Jahn | 2020-02-03 | 1 | -2/+2 |
| | | |||||
| * | clang-format: Enable regrouping and sorting of includes | Linus Jahn | 2020-02-03 | 1 | -2/+3 |
| | | |||||
| * | Port majority of old-style connects (#237) | JBB | 2020-01-20 | 1 | -11/+11 |
| | | | | This provides more type safety and is future-proof. | ||||
| * | Bump copyright year to 2020 | Linus Jahn | 2020-01-06 | 1 | -1/+1 |
| | | |||||
| * | Modernize codebase using clang-tidy | Jonah Brüchert | 2019-09-08 | 1 | -1/+1 |
| | | | | | | | | | Using the following checks: * modernize-use-nullptr * modernize-use-override * modernize-use-using * modernize-use-bool-literals | ||||
| * | Bump copyright year to 2019 | Jeremy Lainé | 2019-01-08 | 1 | -1/+1 |
| | | |||||
| * | correctly receive data immediately following a SOCKS5 message (closes #64) | Jeremy Lainé | 2015-08-15 | 1 | -3/+15 |
| | | | | | | | | | | | The SOCKS5 client and server would discard any currently buffered received data when processing a SOCKS5 command as they used readAll(). Now they only consume the SOCKS5 command's bytes, preserving any buffered data. Why this situation should occur is a different matter, I would be surprised to see it happen during file transfer, due to the sequence in which the handshake is performed. | ||||
| * | socks5: make server explicitly return "no acceptable method" | Jeremy Lainé | 2015-07-27 | 1 | -0/+5 |
| | | |||||
| * | socks5: improve test coverage of failed CONNECT | Jeremy Lainé | 2015-07-27 | 1 | -6/+33 |
| | | |||||
| * | socks5: add test case for client | Jeremy Lainé | 2015-07-27 | 1 | -45/+99 |
| | | |||||
| * | improve tests | Jeremy Lainé | 2015-07-27 | 1 | -2/+15 |
| | | |||||
| * | add some tests for invalid SOCKS5 handshake from client | Jeremy Lainé | 2015-07-27 | 1 | -0/+45 |
| | | |||||
| * | don't hardcode port 1080 | Jeremy Lainé | 2015-07-27 | 1 | -2/+1 |
| | | |||||
| * | add some tests for QXmppSocksServer | Jeremy Lainé | 2015-07-27 | 1 | -0/+122 |
 |
index : xavi/qxmpp | |
| Fork of the QXmpp library. |
| aboutsummaryrefslogtreecommitdiff |