Full Disclosure mailing list archives
Re: THISISNOTMYEXPLOIT
From: Kingcope <kcope2 () googlemail com>
Date: Fri, 31 Jul 2009 17:58:22 +0200
Hello people, Yes there is a warning when the PoC is compiled. But I guess that is not a big issue. So about what PoC am I talking about? It seems that the moderator of bugtraq keeps blocking me because of fancy headlines maybe. The moderator of bugtraq blocked the actual exploit but let the following messages slip through. The PoC is on milw0rm.com and full disclosure. Thanks for clarifying the issue with the zones, I really have not a 100% understanding of the DNS protocol therefore I took a guess on my named.conf file and put the address into the PoC. Thanks for your time, Kingcope 2009/7/31 yersinia <yersinia.spiros () gmail com>:
Repost for mailing problem. On Fri, Jul 31, 2009 at 12:14 AM, yersinia <yersinia.spiros () gmail com> wrote:On Thu, Jul 30, 2009 at 1:24 PM, Kingcope <kcope2 () googlemail com> wrote:Hello again, the default setting of 127.in-addr.arpa is a bit weird try ./bind <ip> localhostNever mind. I have only a warning from gcc because it was necessary to include stdlib.h for malloc. But, the important thing is that it works as aspected. Regardslewls XD kcope 2009/7/30 Kingcope <kcope2 () googlemail com>:I own nothing. Cheers, kcope_______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
_______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
Current thread:
- THISISNOTMYEXPLOIT Kingcope (Jul 30)
- Re: THISISNOTMYEXPLOIT Kingcope (Jul 30)
- Re: THISISNOTMYEXPLOIT Kingcope (Jul 30)
- Re: THISISNOTMYEXPLOIT yersinia (Jul 30)
- Re: THISISNOTMYEXPLOIT yersinia (Jul 30)
- Re: THISISNOTMYEXPLOIT Kingcope (Jul 31)
- Re: THISISNOTMYEXPLOIT yersinia (Jul 30)
- <Possible follow-ups>
- Re: THISISNOTMYEXPLOIT advisories (Jul 31)