From strenholme.usenet at gmail.com Mon Sep 1 11:20:27 2008 From: strenholme.usenet at gmail.com (Sam Trenholme) Date: Mon, 1 Sep 2008 10:20:27 -0500 Subject: MaraDNS snapshot update Message-ID: <7bd685720809010820j1d77067ajb5a255cde09f948@mail.gmail.com> Hello, everyone, I'm just letting people know I have just released a new snapshot of MaraDNS. The big changes are: * Deadwood 2 updated to Deadwood 2.02. This version has a couple of bugfixes that make it a usable thread-free security-aware forwarding cache resolver. * BSD updates: This version should compile fine in the various BSDs out there. There is a report Duende doesn't run on FreeBSD; if anyone using FreeBSD wants to fix Duende's code, please sent a patch to the mailing list. It is available here: http://www.maradns.org/download/1.3/snap/200809 - Sam Note: If you send me a MaraDNS-related support question, I reserve the right to post your support email to the Mara-DNS mailing list so that the community at large can examine your issue. MaraDNS security vulnerability reports, however, will be kept confidential. From strenholme.usenet at gmail.com Tue Sep 2 11:14:11 2008 From: strenholme.usenet at gmail.com (Sam Trenholme) Date: Tue, 2 Sep 2008 10:14:11 -0500 Subject: I have found and fixed the Duende FreeBSD problem Message-ID: <7bd685720809020814y5a2072bal4001bcd557d21cbe@mail.gmail.com> Since someone sponsoring MaraDNS uses FreeBSD on the server side, I was able to reproduce and resolve the problem with "duende" (MaraDNS' daemonizer) not logging messages. There are two ways of resolving it, one that the sysadmin can implement, and one that I have implemented. It would appear that FreeBSD's syslog daemon does not log Duende's messages by default. In order to fix this, we first must create a /var/log/daemon file, which will log all of MaraDNS' messages (or any other messages created by a program that logs files with a "facility" of LOG_DAEMON and a priority of LOG_INFO). Next, we need to edit /etc/syslog.conf to add a line like this: daemon.info /var/log/daemon (That should be a tab, but just a space should work in FreeBSD) Please be sure to add this line *before* any lines that begin with a '!' character or a '+' character in the /etc/syslog.conf file. This is the fix for MaraDNS 1.2 and stable MaraDNS 1.3. For the development 1.3 branch, I changed the Duende code to have it so, when compiled in FreeBSD (#ifdef __FREEBSD__), it logs messages as "daemon.alert" (which is logged in FreeBSD's default /etc/syslog.conf) instead of "daemon.info" (which isn't logged). I have updated the MaraDNS snapshot to incorporate this change: http://www.maradns.org/download/snap/1.3/200809/ It took me about a day to find the issue and resolve this; a lot of the work was just getting FreeBSD working in VMware. Things like configuring the virtual interface VMware uses and then figuring out how to ssh to and from the VMware instance of FreeBSD (ssh 192.168.72.128 -l username). Once that was going, it didn't take too long to fix the Duende problem ("man syslog" helped a lot) Since I now have a working FreeBSD VMware image, I can more fully support FreeBSD. From devolder.killian at student.ha.be Tue Sep 2 12:23:42 2008 From: devolder.killian at student.ha.be (Killian De Volder) Date: Tue, 02 Sep 2008 18:23:42 +0200 Subject: unscribe Message-ID: <48BD688E.90501@student.ha.be> From lew.payne at gmail.com Tue Sep 2 13:31:51 2008 From: lew.payne at gmail.com (Lew Payne) Date: Tue, 2 Sep 2008 11:31:51 -0600 Subject: I have found and fixed the Duende FreeBSD problem In-Reply-To: <7bd685720809020814y5a2072bal4001bcd557d21cbe@mail.gmail.com> References: <7bd685720809020814y5a2072bal4001bcd557d21cbe@mail.gmail.com> Message-ID: Sam - I didn't really expect you to be able to take a look at this, much less fix it. I know it's a pain in the ass to set up another OS just to test things out. I will give this a try over the next few weeks (with version 1.2). The thing is, when I tested last year, I even did a "catch all" and still did not see any duende output, to-wit: /etc/syslog.conf: !maradns *.* /var/log/maradns !duende /var/log/maradns *.* and then as I got more angry, I did the following... /etc/syslog.conf: *.* /var/log/all.log ... and in each instance I did a SIGHUP to make sure syslog reloaded its configuration. In the last case, it was logging plenty of system activity (basically everything), but still no duende. So I will carefully give your suggestion a try on a spare box. Also, if it's simply a matter of needing a box to play on, I'm perfectly willing to give you ssh access to a spare box here. Regards, Lew Payne Boise Stock Exchange On Tue, Sep 2, 2008 at 9:14 AM, Sam Trenholme wrote: > Since someone sponsoring MaraDNS uses FreeBSD on the server side, I > was able to reproduce and resolve the problem with "duende" (MaraDNS' > daemonizer) not logging messages. > > There are two ways of resolving it, one that the sysadmin can > implement, and one that I have implemented. > > It would appear that FreeBSD's syslog daemon does not log Duende's > messages by default. In order to fix this, we first must create a > /var/log/daemon file, which will log all of MaraDNS' messages (or any > other messages created by a program that logs files with a "facility" > of LOG_DAEMON and a priority of LOG_INFO). > > Next, we need to edit /etc/syslog.conf to add a line like this: > > daemon.info /var/log/daemon > > (That should be a tab, but just a space should work in FreeBSD) > > Please be sure to add this line *before* any lines that begin with a > '!' character or a '+' character in the /etc/syslog.conf file. > > This is the fix for MaraDNS 1.2 and stable MaraDNS 1.3. > > For the development 1.3 branch, I changed the Duende code to have it > so, when compiled in FreeBSD (#ifdef __FREEBSD__), it logs messages as > "daemon.alert" (which is logged in FreeBSD's default /etc/syslog.conf) > instead of "daemon.info" (which isn't logged). > > I have updated the MaraDNS snapshot to incorporate this change: > > http://www.maradns.org/download/snap/1.3/200809/ > > It took me about a day to find the issue and resolve this; a lot of > the work was just getting FreeBSD working in VMware. Things like > configuring the virtual interface VMware uses and then figuring out > how to ssh to and from the VMware instance of FreeBSD (ssh > 192.168.72.128 -l username). Once that was going, it didn't take too > long to fix the Duende problem ("man syslog" helped a lot) > > Since I now have a working FreeBSD VMware image, I can more fully > support FreeBSD. From strenholme.usenet at gmail.com Tue Sep 2 14:07:42 2008 From: strenholme.usenet at gmail.com (Sam Trenholme) Date: Tue, 2 Sep 2008 13:07:42 -0500 Subject: I have found and fixed the Duende FreeBSD problem In-Reply-To: References: <7bd685720809020814y5a2072bal4001bcd557d21cbe@mail.gmail.com> Message-ID: <7bd685720809021107m11d39ecaqc4746196ebae69be@mail.gmail.com> Well, someone who made a donation to the MaraDNS cause wanted to see the issue fixed so I got FreeBSD going yesterday. > The thing is, when I tested last year, I > even did a "catch all" and still did not see any duende output, > to-wit: > > /etc/syslog.conf: > > !maradns > *.* /var/log/maradns > !duende /var/log/maradns > *.* > > and then as I got more angry, I did the following... > > /etc/syslog.conf: > > *.* /var/log/all.log Hmm, that ! syntax with syslog is confusing. If you have something like !foo *.* /var/log/foo *.* /var/log/all Only information from the "foo" application will get logged. What you have to do is this: !foo *.* /var/log/foo !* *.* /var/log/all And then things work. This might have been the problem. And, yes, having more *NIX accounts is a good thing. I'll send you my PGP key. As an aside, I *like* FreeBSD. Ubuntu wastes disk space with eye candy and silly things like playing a song after you log in, but doesn't come with a usable compiler nor development environment, and you have to do a number of "apt-get install"s to make it a usable system (libc-devel; patch; etc.) And, oh, Ubuntu is quite unstable; my wireless card sometimes works and sometimes doesn't work. The other day I was logging in to Gnome and Ubuntu crashed during the login, forcing a system reset. FreeBSD, on the other hand, in the "User" install doesn't have Bash, doesn't have X, any editor besides "vi", and doesn't have three-piece bands playing songs to celebrate you successfully logging in. On the other hand, it's a usable system out of the box: gcc; patch; libraries and header files to compile programs; sshd; it's all there by default. It looks like the important stuff in my laptop is supported in FreeBSD. I wonder if FreeBSD now supports extended partitions. I want a free *NIX system that is stable, but still gets new drivers for new hardware. Ubuntu is too unstable; CentOS/RHEL takes too long getting new drivers in to the kernel. The problem a stable Linux has is that it's really hard to get new drivers in to a stable kernel because the Linux kernel developers constantly tweak the driver API. Linux still feels like a hack. I will try downloading FreeBSD in the next few days. It's a 2 gig torrent, so it'll take me a while to get it down here in Mexico, but I like what I see so far. - Sam From chimak_quarg at yahoo.co.uk Mon Sep 22 22:13:41 2008 From: chimak_quarg at yahoo.co.uk (Mohammed Ahmed) Date: Tue, 23 Sep 2008 03:13:41 +0100 Subject: Compiling under MinGW Message-ID: <20080923021406.4DDD073833B@woodlane.webconquest.com> First of all, thanks to Sam for writing a great program and all the hard work he puts in. I've noticed that the snapshots are only available in the form of source packages and there aren't any binaries for Windows users to download and test. I've compiled MPlayer under MinGW on previous occasions by following a step-by-step guide and I was wondering if anyone is interested in writing a similar guide for MaraDNS. The MPlayer guide was fairly popular judging by some of the posts on the MPlayer-Cygwin list. I'm sure many Windows users would like to try the snapshots yet have little idea how to compile from source - I myself have unsuccessfully tried more than once. MinGW/MSYS isn't that difficult to install and anyone familiar with using the command line under Windows ought to be able to figure things out. More feedback could be reported at an earlier stage too. Mo