Behind the Masq: Yet More DNS and DHCP Vulnerabilities

Re:Behind the Masq: Yet More DNS and DHCP Vulnerabilities by fulafel on Wednesday October 04, 2017 @04:20PM (#15404213)

I find it really hard to understand the view that a company shipping a defective product that may cause great harm to users should be excused from responsibility because the bad software choices they made happened to be open source.

I suspect the consumer protection laws take similar views in many countries.

Like I said before, there are a number of available DHCP and DNS implementations in memory-safe languages. Many of them are open source. So the vendors don't even have that excuse.

[ Parent | on HN ]

Re:Behind the Masq: Yet More DNS and DHCP Vulnerabilities by feld on Thursday October 05, 2017 @01:37PM (#15410947)

What are they? I've certainly never heard of them or used them. Are they used in production or are they toys?

DHCP: isc-dhcp or dnsmasq

DNS recursor: dnsmasq, unbound, bind, djb's dnscache, maradns

None of these are written in memory safe languages, but they're the only ones I would trust because they have YEARS of testing and getting the RFCs right.

[ Parent | on HN ]