[Dnsmasq-discuss] Memory corruption in hostname_isequal (util.c), SIGSEGV

ks ==4077== Rerun with --leak-check=full to see details of leaked memory ==4077== ==4077== For counts of detected and suppressed errors, rerun with: -v ==4077== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) [1]4077 segmentation fault valgrind ./src/dnsmasq --test -C /

[Dnsmasq-discuss] Memory corruption in parse_hex (util.c), SIGSEGV

ocks ==23713== Rerun with --leak-check=full to see details of leaked memory ==23713== ==23713== For counts of detected and suppressed errors, rerun with: -v ==23713== ERROR SUMMARY: 9 errors from 1 contexts (suppressed: 0 from 0) Regards, Stephan -- Stephan Zeisberg Security Researcher m: stephan

[Dnsmasq-discuss] Memory corruption in my_syslog (log.c), SIGABRT (double free)

=) at option.c:4733 #17 0x00457557 in main (argc=2, argv=0x7fffcf5128d0) at dnsmasq.c:89 Regards, Stephan -- Stephan Zeisberg Security Researcher m: stephan.zeisb...@splone.com pgp: 3C2B 7189 9C16 1E71 5BFB 8690 2C3F EF24 6DBF B588 splone UG (haftungsbeschränkt) c/o Freie Universität

Re: [Dnsmasq-discuss] Memory corruption in my_syslog (log.c), SIGABRT (double free)

are not security problems, since they > rely on malformed config files and not untrusted data from the net.) > > Cheers, > > Simon. > > On 03/05/17 17:47, Stephan Zeisberg wrote: >> Hello, >> >> opening the attached sample config input file with dnsmasq results