Hello all, Are they any thoughts around, how to handle yesterday's glibc vulnerability[1][2] from the side bind?
Since it is a rather painful task in order to update all hosts to a new version of glibc, we were thinking about other possible workarounds. Any ideas how to drop non-compliant responses in bind? I.e. with an extension/adaptation of bind? [1]https://sourceware.org/ml/libc-alpha/2016-02/msg00416.html [2] https://googleonlinesecurity.blogspot.com/2016/02/cve-2015-7547-glibc-getaddrinfo-stack.html
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
