@@ -3,6 +3,10 @@ getdns-python-bindings
3
3
4
4
Python bindings for getdns
5
5
6
+ * Date: 2016-03-29
7
+ * Github: https://github.com/getdnsapi/getdns-python-bindings
8
+ * Current version: v1.0beta
9
+
6
10
External dependencies
7
11
=====================
8
12
@@ -13,12 +17,11 @@ called "python-dev"
13
17
Currently building against the getdns v0.9.0 release.
14
18
getdns external dependencies include:
15
19
16
- * [ libldns from NLnet Labs] ( https://www.nlnetlabs.nl/projects/ldns/ ) version 1.6.11 or later (ldns requires ope
17
- nssl headers and libraries)
18
20
* [ libunbound from NLnet Labs] ( http://www.nlnetlabs.nl/projects/unbound/ ) version 1.4.16 or later
19
- * [ libexpat] ( http://expat.sourceforge.net/ ) for libunbound.
20
21
* [ libidn from the FSF] ( http://www.gnu.org/software/libidn/ ) version 1.
21
-
22
+ * [ libssl and libcrypto from the OpenSSL project] ( https://www.openssl.org/ ) version 0.9.7 or later.
23
+ (Note: version 1.0.1 or later is required for TLS support,
24
+ version 1.0.2 or later is required for TLS hostname authentication)
22
25
23
26
Building
24
27
========
@@ -30,7 +33,7 @@ python setup.py build
30
33
31
34
During the development process and before the module is installed, I
32
35
find it convenient to have a symlink in the current directory pointing
33
- to the library in the build directory:
36
+ to the library in the build directory. For example :
34
37
35
38
```
36
39
getdns.so -> build/lib.linux-i686-2.7/getdns.so
@@ -68,6 +71,29 @@ source tree in doc/_build/html. It is also available online at [readthedocs.org
68
71
Changes from the earlier release
69
72
================================
70
73
74
+ * A number of performance improvements.
75
+
76
+ * Installable via PyPi.
77
+
78
+ * Removed libevent dependency
79
+
80
+ * For consistency with Python 3, the Python 2 bindings now return
81
+ Context() attributes as longs
82
+
83
+ * TSIG support
84
+
85
+ * GETDNS_AUTHENTICATION_HOSTNAME is replaced by
86
+ GETDNS_AUTHENTICATION_REQUIRED (but remains available as an alias).
87
+ Upstreams can now be configured with either a hostname or a SPKI
88
+ pinset for TLS authentication (or both). If the
89
+ GETDNS_AUTHENTICATION_REQUIRED option is used at least one piece of
90
+ authentication information must be configured for each upstream, and
91
+ all the configured authentication information for an upstream must
92
+ validate.
93
+
94
+ Older changes
95
+ =============
96
+
71
97
In addition to adding Python 3 support, we've changed the callback
72
98
argument to the asynchronous methods to accept a callable by name,
73
99
rather than as a literal string.
0 commit comments