| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 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 |