| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | add missing copyrights | Bob Halley | 2020-08-17 | 1 | -0/+2 |
| | | |||||
| * | unify chaining code | Bob Halley | 2020-07-21 | 1 | -0/+46 |
| | | |||||
| * | Better deal with backwards compatibility. | Brian Wellington | 2020-07-01 | 1 | -2/+3 |
| | | | | | | | | | If dns.tsigkeyring.from_text() creates dns.tsig.Key objects with the default algorithm, that causes problems for code that specifies a different algorithm. There's no good way to handle this, so change dns.tsigkeyring.from_text() to not create dns.tsig.Key objects unless it knows the algorithm. | ||||
| * | Add dns.tsig.Key class. | Brian Wellington | 2020-07-01 | 1 | -2/+2 |
| | | | | | | | | | | | | | | | | | | | | | This creates a new class to represent a TSIG key, containing name, secret, and algorithm. The keyring format is changed to be {name : key}, and the methods in dns.tsigkeyring are updated to deal with old and new formats. The Message class is updated to use dns.tsig.Key, although (to avoid breaking existing code), it stores them in the keyring field. Message.use_tsig() can accept either explicit keys, or keyrings; it will extract and/or create a key. dns.message.from_wire() can accept either a key or a keyring in the keyring parameter. If passed a key, it will now raise if the TSIG record in the message was signed with a different key. If passed a keyring containing keys (as opposed to bare secrets), it will check that the TSIG record's algorithm matches that of the key. | ||||
| * | make _Resolution coverage 100% | Bob Halley | 2020-05-28 | 1 | -0/+55 |
| | | |||||
| * | further tighten resolve() default settings | Bob Halley | 2020-05-27 | 1 | -4/+43 |
| | | |||||
| * | add NXDOMAIN caching | Bob Halley | 2020-05-21 | 1 | -2/+44 |
| | | |||||
| * | pop() with no arguements means last, but I used it intending first | Bob Halley | 2020-05-21 | 1 | -2/+2 |
| | | |||||
| * | conform to Answer constructor change | Bob Halley | 2020-05-20 | 1 | -1/+1 |
| | | |||||
| * | finish testing of resolver business logic | Bob Halley | 2020-05-19 | 1 | -15/+154 |
| | | |||||
| * | start resolution business logic tests. | Bob Halley | 2020-05-19 | 1 | -0/+148 |
 |
index : delta/python-packages/dnspython.git | |
| github.com: rthalley/dnspython.git |
| summaryrefslogtreecommitdiff |