Re: A Few Additional Words About CVE-2014-0591

2014-01-13 Thread Evan Hunt
On Mon, Jan 13, 2014 at 04:44:22PM -0600, Lawrence K. Chen, P.Eng. wrote: > Hmmm, from what I vaguely recall from my software engineering days, was > that memcpy() didn't ever handle overlapped memory buffers and that you > should consider memmove() in such cases. Yes, that's correct, and in fact

Re: A Few Additional Words About CVE-2014-0591

2014-01-13 Thread Lawrence K. Chen, P.Eng.
Hmmm, from what I vaguely recall from my software engineering days, was that memcpy() didn't ever handle overlapped memory buffers and that you should consider memmove() in such cases. Doesn't really make sense that it should, though I think I first learned about this during a code review. Don't

A Few Additional Words About CVE-2014-0591

2014-01-13 Thread Michael McNally
Hello, Bind-Users Readers -- Since you are all subscribers to bind-announce as well [You are, aren't you? It's where we make announcements about security vulnerabilities and about new versions of BIND] you are probably already aware that ISC has announced CVE-2014-0591, a vulnerability which can