- 07 Jun, 2017 1 commit
-
-
Chris Novakovic authored
Commit f77700aa, which fixes a compiler warning, also breaks the behaviour of prepending ".<layer>" to basenames in --pxe-service: in situations where the basename contains a ".", the ".<layer>" suffix is erroneously added, and in situations where the basename doesn't contain a ".", the ".<layer>" suffix is erroneously omitted. A patch against the git HEAD is attached that inverts this logic and restores the expected behaviour of --pxe-service.
-
- 06 Jun, 2017 1 commit
-
-
Simon Kelley authored
-
- 23 May, 2017 1 commit
-
-
Simon Kelley authored
-
- 22 May, 2017 5 commits
-
-
Matthias Andree authored
-
Matthias Andree authored
-
Simon Kelley authored
-
Simon Kelley authored
Remove historic automatic inclusion of IDN support when building internationalisation support. This doesn't fit now there is a choice of IDN libraries. Be sure to include either -DHAVE_IDN or _DHAVE_LIBIDN2 for IDN support
-
Simon Kelley authored
-
- 12 May, 2017 3 commits
-
-
Conrad Kostecki authored
-
Simon Kelley authored
-
Simon Kelley authored
-
- 11 May, 2017 2 commits
-
-
Simon Kelley authored
-
Petr Menšík authored
-
- 10 May, 2017 2 commits
-
-
Simon Kelley authored
-
Simon Kelley authored
-
- 09 May, 2017 2 commits
-
-
Simon Kelley authored
This was causing confusion: DNSSEC queries would be sent to servers for domains that don't do DNSSEC, but because of that status the answers would be treated as answers to ordinary queries, sometimes resulting in a crash.
-
Simon Kelley authored
-
- 04 May, 2017 2 commits
-
-
Vladislav Grishenko authored
This fixes build time warnings with POSIX.1-2008-aware c libraries.
-
Simon Kelley authored
Thanks to Stephan Zeisberg and american fuzzy lop http://lcamtuf.coredump.cx/afl/
-
- 01 May, 2017 1 commit
-
-
Simon Kelley authored
-
- 29 Apr, 2017 3 commits
-
-
Simon Kelley authored
-
Simon Kelley authored
This reverts commit 88a77a78. A least one client has been found which breaks with this change. Since the use-case is not clear, I'm reverting the change, at least for now.
-
Simon Kelley authored
-
- 25 Apr, 2017 2 commits
-
-
Vladislav Grishenko authored
-
Vladislav Grishenko authored
-
- 23 Apr, 2017 1 commit
-
-
Petr Menšík authored
-
- 17 Apr, 2017 5 commits
-
-
Simon Kelley authored
-
-
Simon Kelley authored
-
Simon Kelley authored
-
Petr Menšík authored
-
- 12 Apr, 2017 4 commits
-
-
Simon Kelley authored
-
-
Simon Kelley authored
-
Simon Kelley authored
-
- 11 Apr, 2017 5 commits
-
-
Simon Kelley authored
-
Simon Kelley authored
-
Simon Kelley authored
-
Simon Kelley authored
-
Floris Bos authored
Dnsmasq's startup script seems to assume users always want to use dnsmasq as local DNS resolver, and tells resolvconf to put "nameserver 127.0.0.1" in /etc/resolv.conf The problem with this is that if users just want to use dnsmasq as DHCP server, and put port=0 in /etc/dnsmasq.conf to disable the DNS functionality, they end up with broken name resolving. Put a basic check in the startup script that skips resolvconf configuration if a line starting with port=0 is in /etc/dnsmasq.conf This doesn't cover all cases (e.g. configuration could also be in different file in /etc/dnsmasq.d), but is better than current situation.
-