compilation bug fix for bsds

[Yarin]

Haha, it looks like you've updated duende since your latest official release, so when you added the patch, one of the patch's lines got stuffed in a new comment. I've confirmed that everything else is where it's suppose to be though. The below diff, applied on top of it, should put it where it goes.

--- ./tools/duende.c  2011-01-10 20:59:17.709054060 -0600
+++ ./tools/duende.c  2011-01-10 21:00:15.504928526 -0600
@@ -146,7 +146,6 @@
 
 /* The main process forks off the child.  Right now, I will just have
    it fork off the MaraDNS process, hardwired as /usr/sbin/maradns,
-    int exec_argv_offset = 1; /* Also used to determine PID writing */
    directing her standard output to
    /dev/null.  The revision of this file will correctly handle Mara's
    output
@@ -156,6 +155,7 @@
     int exit_status;
     pid_t pid, log_pid;
     int stream1[2]; /* Used for piping */
+    int exec_argv_offset = 1; /* Also used to determine PID writing */
     if(argv[0] == NULL || argv[1] == NULL) {
         printf("Usage: duende (--pid=/path/to/file) [program] [arguments]\n");
         exit(1);

Just recently, MaraDNS freaked when I tried to use a dot in the local part of an SOA record. I then discovered that MaraDNS holds to the classic, using the first dot in the address instead of an at sign. Would you accept a patch that works with this to support dots in the local part? The address would be parsed the same way dig prints it, that is, with the local dots escaped, when lacking an at sign.


----- Original message -----
From: "Sam Trenholme" <strenholme.usenet at gmail.com>
To: list at maradns.org
Date: Mon, 10 Jan 2011 08:22:54 -0700
Subject: Re: compilation bug fix for bsds

>> there are still many people running unmodified [djbdns] 1.05.

> Heh, well, in those cases, that sounds a lot like a poor sys admin,
> I imagine it's kind of obvious that using unmaintained software that
> hasn't been even updated in 10 years is a bad idea regardless.

It's obvious to you.  It's obvious to me.  However, we're not wearing
the blinders that people under the influence of the djb reality
distortion field wear.  For years, their mantra was that djb somehow
had some builtin magic pixie dust that made his software 100% secure
and never need updating.

They started to have to bend reality to continue to believe this lie.
Backscatter spam is not a security problem is probably the first lie
they had to tell themselves.  Then they had to convince themselves
that not catching SIGPIPE is not a security problem.  Once djb himself
admitted that the AXFR issue Dempsky found was a security issue, some
people moved away from the reality distortion field, but others either
haven't heard of this bug or feel it's djbdns' only bug.

One of my pet peeves is people who tell themselves lie to believe some
groupthink.  I get annoyed at pirates who tell themselves "copyright
infringement is morally OK in the 'new economy'"; I get annoyed at
audiophiles who tell themselves "double-blind studies are not
scientifically valid"; as I Christian, I find young-earth creationists
very annoying.  And I get annoyed at people who use self-delusions to
justify using outdated and unmaintained (branches of) software.

> Maybe you should bring the Slashdot community up to speed
> on the matter :-)

I've made a decision to no longer post to Slashdot.  The place has
become too much of a flamefest.

But, instead, I have blogged about it:

http://samiam.org/blog/

More to the point, I have started to integrate your patches in to
MaraDNS.  I have already added your duende patch to Deadwood:

http://maradns.org/deadwood/snap/

If you could, take a look at it and let me know if it works for you.

- Sam