From scottr at nist.gov Wed Sep 12 18:29:20 2007 From: scottr at nist.gov (Scott Rose) Date: Wed, 12 Sep 2007 14:29:20 -0400 Subject: [dsc] bug(?) in upload-rsync.sh Message-ID: <46E83000.5040907@nist.gov> I'm using the 200706121022 build of dsc and using rsync to transfer the xml files from the collector to the presenter (probably the only one doing this :) Anyway, the script had a few minor bugs I had to correct. I don't know if this is already corrected or not. The diff: diff upload-rsync.sh cron/upload-rsync.sh 28c28 < cd $PREFIX/var/run/$NODE/upload/$DEST --- > cd $PREFIX/run/$NODE/upload/$DEST 40c40 < md5 $k > MD5s --- > md5 -r $k > MD5s I'm using the md5sum 5.97 for the md5, which doesn't have a -r option, so just dropping that seems to work. Same with adding "/var" to after $PREFIX. Anyway, after those fixes, it's working as advertised. I did a very quick search in the archives and didn't see this mentioned. Scott -- ---------------------------------------- Scott Rose Computer Scientist NIST ph: +1 301-975-8439 scott.rose at nist.gov http://www-x.antd.nist.gov/dnssec http://www.dnsops.gov/ ----------------------------------------- From wessels at measurement-factory.com Thu Sep 13 18:35:38 2007 From: wessels at measurement-factory.com (Duane Wessels) Date: Thu, 13 Sep 2007 12:35:38 -0600 (MDT) Subject: [dsc] bug(?) in upload-rsync.sh In-Reply-To: <46E83000.5040907@nist.gov> References: <46E83000.5040907@nist.gov> Message-ID: <20070913123340.X22729@measurement-factory.com> On Wed, 12 Sep 2007, Scott Rose wrote: > I'm using the md5sum 5.97 for the md5, which doesn't have a -r option, > so just dropping that seems to work. Same with adding "/var" to after > $PREFIX. Thanks for the fixes! The upload-rsync script doesn't really use the MD5 values anyway, so I think we could remove it entirely from the script if it continues to be a problem. Duane W. From pierre.lebrech at laposte.net Tue Sep 25 13:15:57 2007 From: pierre.lebrech at laposte.net (Pierre LEBRECH) Date: Tue, 25 Sep 2007 15:15:57 +0200 Subject: [dsc] DSC and base64 Message-ID: <46F90A0D.9030706@laposte.net> Hello, I got this on one of my DNS servers a few minutes ago : ########################################## cut ########################################## cut Question : what is it? I've never heard of base64 within DSC documentation. Thx From wessels at measurement-factory.com Tue Sep 25 18:15:59 2007 From: wessels at measurement-factory.com (Duane Wessels) Date: Tue, 25 Sep 2007 12:15:59 -0600 (MDT) Subject: [dsc] DSC and base64 In-Reply-To: <46F90A0D.9030706@laposte.net> References: <46F90A0D.9030706@laposte.net> Message-ID: <20070925120823.G24471@measurement-factory.com> On Tue, 25 Sep 2007, Pierre LEBRECH wrote: > Question : what is it? I've never heard of base64 within DSC documentation. Base64 is a method for encoding a string into another string that contains only "safe" or printable characters. DSC uses base64 encoding when a query name contains "special" characters because certain characters should not appear in the XML attribute value. This is mentioned in the user manual (around p34): For some indexers these values are numeric, for others they are strings. If the value contains certain non-printable characters, the string is base64-encoded and the optional BASE64 attribute is set to 1. In your case, that particular query name was actually a URL. You can see it with a command like this: echo 'aHR0c ... h5LnBs' | /usr/local/lib/python2.5/base64.py -d | less Duane W. From pierre.lebrech at laposte.net Tue Sep 25 20:24:41 2007 From: pierre.lebrech at laposte.net (Pierre LEBRECH) Date: Tue, 25 Sep 2007 22:24:41 +0200 Subject: [dsc] DSC and base64 In-Reply-To: <20070925120823.G24471@measurement-factory.com> References: <46F90A0D.9030706@laposte.net> <20070925120823.G24471@measurement-factory.com> Message-ID: <46F96E89.70707@laposte.net> Duane Wessels wrote : > > > On Tue, 25 Sep 2007, Pierre LEBRECH wrote: > >> Question : what is it? I've never heard of base64 within DSC >> documentation. > > Base64 is a method for encoding a string into another string that > contains > only "safe" or printable characters. > > DSC uses base64 encoding when a query name contains "special" characters > because certain characters should not appear in the XML attribute value. > This is mentioned in the user manual (around p34): > > For some indexers these values are numeric, for others they > are strings. If the value contains certain non-printable > characters, the string is base64-encoded and the optional > BASE64 attribute is set to 1. > > In your case, that particular query name was actually a URL. You can > see it with a command like this: > > echo 'aHR0c ... h5LnBs' | /usr/local/lib/python2.5/base64.py -d | less > > Duane W. Thanks Duane. Very interesting. Could it be possible that such queries belong to normal DNS traffic? Are they used for something? For me, it's quite strange to receive such queries! From wessels at measurement-factory.com Tue Sep 25 21:12:46 2007 From: wessels at measurement-factory.com (Duane Wessels) Date: Tue, 25 Sep 2007 15:12:46 -0600 (MDT) Subject: [dsc] DSC and base64 In-Reply-To: <46F96E89.70707@laposte.net> References: <46F90A0D.9030706@laposte.net> <20070925120823.G24471@measurement-factory.com> <46F96E89.70707@laposte.net> Message-ID: <20070925150949.R24471@measurement-factory.com> On Tue, 25 Sep 2007, Pierre LEBRECH wrote: > Thanks Duane. Very interesting. > Could it be possible that such queries belong to normal DNS traffic? Are > they used for something? For me, it's quite strange to receive such queries! It probably depends on your definition of "normal" but I would say: No. Queries such as this (URL instead of a hostname) most likely come from buggy software that cannot tell the difference between the two. Duane W.