<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to bugs</title><link href="https://sourceforge.net/p/dproxy/bugs/" rel="alternate"/><link href="https://sourceforge.net/p/dproxy/bugs/feed.atom" rel="self"/><id>https://sourceforge.net/p/dproxy/bugs/</id><updated>2008-03-25T14:24:47Z</updated><subtitle>Recent changes to bugs</subtitle><entry><title>dproxy-nexgen cache confused by IPv6</title><link href="https://sourceforge.net/p/dproxy/bugs/13/" rel="alternate"/><published>2008-03-25T14:24:47Z</published><updated>2008-03-25T14:24:47Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.net786396d7881c074b045c35ca695483b87371b398</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;dproxy-nexgen has a very serious bug when dealing with IPv6 and IPv4 addresses. When receiving an AAAA record, the daemon stores the first 4 bytes of the IPv6 address as a (totally false) IPv4 address into the cache.&lt;/p&gt;
&lt;p&gt;As a consequence, client operating system like Ubuntu, which ask for AAAA records first, get afterwards a wrong A record and are not able to connect to systems which already have IPv6 dns entries. This problem will probably become even more important in the future, when other operating systems switch their default to IPv6 as well, and more servers publish AAAA records.&lt;/p&gt;
&lt;p&gt;How to reproduce:&lt;br /&gt;
$ sudo /etc/init.d/dproxy start&lt;br /&gt;
$ dig @localhost AAAA ubuntuusers.de&lt;br /&gt;
--&amp;gt; answer:  2001:780:0:25::80 (correct)&lt;br /&gt;
$ dig @localhost A ubuntuusers.de&lt;br /&gt;
--&amp;gt; answer:  32.1.7.128 (wrong, should be 213.95.41.11)&lt;/p&gt;
&lt;p&gt;32.1.7.12 are exactly the first four bytes of 2001:780:0:25::80.&lt;/p&gt;
&lt;p&gt;dproxy.debug.log:&lt;br /&gt;
--------------------------------&lt;br /&gt;
[ 6998 ]: enter cache_purge()&lt;br /&gt;
[ 6998 ]: cache_add_hosts_entreies()&lt;br /&gt;
[ 6998 ]: cache_add_hosts_entreies(): done&lt;br /&gt;
[ 6998 ]: Dumping list:&lt;br /&gt;
[ 6998 ]: cache_lookup_name(ubuntuusers.de)&lt;br /&gt;
[ 6998 ]: .......... ubuntuusers.de ---- &lt;br /&gt;
[ 6998 ]: Adding to list-&amp;gt; id: 2105&lt;br /&gt;
[ 6998 ]: Addr: 804e008&lt;br /&gt;
[ 6998 ]: Dumping list:&lt;br /&gt;
[ 6998 ]:     ID: 2105 ... Name: ubuntuusers.de ---- IP: &lt;br /&gt;
[ 6998 ]: 1. Name: ubuntuusers.de  ....  2105  --- 2. 2105&lt;br /&gt;
[ 6998 ]: Found query in list&lt;br /&gt;
[ 6998 ]: Replying with answer from 192.168.4.12&lt;br /&gt;
[ 6998 ]: Cache append: ubuntuusers.de ----&amp;gt; 32.1.7.128&lt;br /&gt;
[ 6998 ]: enter cache_purge()&lt;br /&gt;
[ 6998 ]: cache_add_hosts_entreies()&lt;br /&gt;
[ 6998 ]: cache_add_hosts_entreies(): done&lt;br /&gt;
[ 6998 ]: Dumping list:&lt;br /&gt;
[ 6998 ]: cache_lookup_name(ubuntuusers.de)&lt;br /&gt;
[ 6998 ]: .......... ubuntuusers.de ---- 32.1.7.128&lt;br /&gt;
[ 6998 ]: Cache hit&lt;br /&gt;
[ 6998 ]: enter cache_purge()&lt;br /&gt;
[ 6998 ]: cache_add_hosts_entreies()&lt;br /&gt;
[ 6998 ]: cache_add_hosts_entreies(): done&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>SECURITY: remotely exploitable buffer overflow</title><link href="https://sourceforge.net/p/dproxy/bugs/12/" rel="alternate"/><published>2007-03-22T09:00:19Z</published><updated>2007-03-22T09:00:19Z</updated><author><name>Alexander Klink</name><uri>https://sourceforge.net/u/alech/</uri></author><id>https://sourceforge.netb0271798d8e5d60e25456ebc607c9c743446e334</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;dproxy 0.x suffers from a remotely exploitable buffer overflow vulnerability. For a security advisory with detailed information see&lt;br /&gt;
&lt;a href="https://www.klink.name/security/aklink-sa-2007-001-dproxy-bufferoverflow.txt" rel="nofollow"&gt;https://www.klink.name/security/aklink-sa-2007-001-dproxy-bufferoverflow.txt&lt;/a&gt;&lt;br /&gt;
(this is the CVE candidate CVE-2007-1465).&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>dproxy-netgen doesn't support MX records</title><link href="https://sourceforge.net/p/dproxy/bugs/11/" rel="alternate"/><published>2002-05-14T21:58:33Z</published><updated>2002-05-14T21:58:33Z</updated><author><name>Alexander Nofftz</name><uri>https://sourceforge.net/u/alexnofftz/</uri></author><id>https://sourceforge.netfcbeae695b96eb33d079d383399093e9e6a64a47</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi!&lt;/p&gt;
&lt;p&gt;dproxy is really great and I enjoy using it, but after&lt;br /&gt;
installing it postfix stops delivering any mails. I&lt;br /&gt;
noticed that dproxy isn't serving any MX records, it&lt;br /&gt;
just timeouts. That makes it impossible to use postfix&lt;br /&gt;
or any other SMTP server in a &amp;amp;quot;dproxied&amp;amp;quot; network.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;
Alex&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>reverse lookup bug</title><link href="https://sourceforge.net/p/dproxy/bugs/10/" rel="alternate"/><published>2002-04-21T18:24:08Z</published><updated>2002-04-21T18:24:08Z</updated><author><name>Roland</name><uri>https://sourceforge.net/u/kaylog/</uri></author><id>https://sourceforge.netd2eec5f3baee305bdf75d201b89fc881c60be235</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi all, &lt;br /&gt;
first, i must say, dproxy is a really cool &lt;br /&gt;
piece of software. &lt;br /&gt;
I have some &amp;amp;quot;special&amp;amp;quot; requirement , that&lt;br /&gt;
i deceided to bring dproxy into discussion in a &lt;br /&gt;
project. I`m testing for some days now (also included &lt;br /&gt;
the reverse lookup bugfix (--&amp;amp;gt; hostnames with &amp;amp;quot;-&amp;amp;quot; &lt;br /&gt;
won't resolve correctly) and still recognised, there &lt;br /&gt;
seems to be a bug with reverse lookup.&lt;/p&gt;
&lt;p&gt;i.e.:&lt;/p&gt;
&lt;p&gt;If i have:&lt;br /&gt;
server_a is 10.0.0.22&lt;br /&gt;
server_b is 10.0.0.222 &lt;br /&gt;
&lt;/p&gt;
&lt;p&gt;reverse lookup &amp;amp;quot;10.0.0.22&amp;amp;quot; gives me &amp;amp;quot;server_b&amp;amp;quot; as a &lt;br /&gt;
result (in some cases) - depends on the position of &lt;br /&gt;
server_a/server_b in the cachefile.&lt;br /&gt;
I think the IP-Comparison in the code must have some &lt;br /&gt;
sort of &amp;amp;quot;design-flaw&amp;amp;quot;.  (didn't study yet, but maybe &lt;br /&gt;
some form of simple substring comparison??)&lt;/p&gt;
&lt;p&gt;Can someone acknowlede this behaviour ?&lt;br /&gt;
I'm not very good at programming, but maybe i can fix &lt;br /&gt;
this by myself. Perhaps someone other already knows &lt;br /&gt;
and has already a fix?&lt;br /&gt;
This bug renders dproxy completely usesless for me....&lt;br /&gt;
:(&lt;br /&gt;
regards&lt;br /&gt;
roland&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>failure in reverse cache lookup</title><link href="https://sourceforge.net/p/dproxy/bugs/9/" rel="alternate"/><published>2001-04-02T21:15:01Z</published><updated>2001-04-02T21:15:01Z</updated><author><name>Real Name</name><uri>https://sourceforge.net/u/dijinai/</uri></author><id>https://sourceforge.net1ce4e70ff4fd51da43ead06cc7577b2e7c0b22dd</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;names with character '-' like&lt;br /&gt;
&amp;amp;quot;xxxxxxxxx.dip.t-dialin.net&amp;amp;quot;&lt;br /&gt;
will be responded incorrect&lt;br /&gt;
--&amp;amp;gt;&amp;amp;quot;xxxxxxxxx.dip.t&amp;amp;quot;&lt;/p&gt;
&lt;p&gt;reason:&lt;br /&gt;
file      cache.c&lt;br /&gt;
function  cache_lookup_ip&lt;br /&gt;
line      110&lt;br /&gt;
added     line[i]=='-'&lt;/p&gt;
&lt;p&gt;works well jet, but i dont think that's the way&lt;br /&gt;
it should do.&lt;/p&gt;
&lt;p&gt;better you change the term in&lt;br /&gt;
&amp;amp;quot;is not a space character&amp;amp;quot;&lt;br /&gt;
because  ..i dont know?  perhabs its saver?&lt;/p&gt;
&lt;p&gt;that's all :-)&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Compilation problem on LinuxPPC</title><link href="https://sourceforge.net/p/dproxy/bugs/8/" rel="alternate"/><published>2001-03-19T05:22:47Z</published><updated>2001-03-19T05:22:47Z</updated><author><name>Martin Heck</name><uri>https://sourceforge.net/u/mheck/</uri></author><id>https://sourceforge.net079be5a7e54b8c3ab9a33372a3ed8c246b0c77d2</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi there,&lt;/p&gt;
&lt;p&gt;I'm trying to use dproxy 0.5 on a LinuxPPC system, &lt;br /&gt;
and I get this warning when I compile:&lt;/p&gt;
&lt;p&gt;dproxy.c: In function `get_options':&lt;br /&gt;
dproxy.c:576: warning: comparison is always true &lt;br /&gt;
due to limited range of data type&lt;/p&gt;
&lt;p&gt;It makes a zero length dproxy.conf file, and &lt;br /&gt;
whenever I try to run the resulting binary, it just &lt;br /&gt;
displays the usage message. I also tried copying a&lt;br /&gt;
dproxy.conf file that dproxy's make created on a &lt;br /&gt;
Linux Mandrake (80x86) machine, and same &lt;br /&gt;
problem.&lt;/p&gt;
&lt;p&gt;It's complaining about this comparison:&lt;br /&gt;
while( (c = getopt( argc, argv, &amp;amp;quot;c:dhP&amp;amp;quot;)) != EOF ) {&lt;br /&gt;
however, I'm not sure what other comparison &lt;br /&gt;
would alleviate this problem.&lt;/p&gt;
&lt;p&gt;Thanx much for any help,&lt;/p&gt;
&lt;p&gt;Martin&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>dproxy doesn´t support AAAA records (IPv6)</title><link href="https://sourceforge.net/p/dproxy/bugs/7/" rel="alternate"/><published>2000-11-04T19:35:01Z</published><updated>2000-11-04T19:35:01Z</updated><author><name>Volker Stolz</name><uri>https://sourceforge.net/u/vssf/</uri></author><id>https://sourceforge.nete50c3ff25aa9b0b563e2d5247a0917ba384251ed</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Subject says it all. Sorry :(&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>qmail CNAME lookup failure</title><link href="https://sourceforge.net/p/dproxy/bugs/6/" rel="alternate"/><published>2000-07-22T11:39:46Z</published><updated>2000-07-22T11:39:46Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.netf9953603c282f46d3307d4a7e38fa9fe6862efe0</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;On dproxy nexgen I always get `CNAME lookup failed temporarily' if qmail tries to send a mail to a remote host. &lt;br /&gt;
qmail FAQ: The SMTP standard does not permit aliased hostnames, so qmail&lt;br /&gt;
has to do a CNAME lookup in DNS for every recipient host. If the&lt;br /&gt;
relevant DNS server is down, qmail defers the message. &lt;br /&gt;
temporary fix: add a real nameserver to the 127.0.0.1 in the resolv.conf&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>wrong cache matches for in.-addr.arpa queries</title><link href="https://sourceforge.net/p/dproxy/bugs/5/" rel="alternate"/><published>2000-04-19T12:52:48Z</published><updated>2000-04-19T12:52:48Z</updated><author><name>Anonymous</name><uri>https://sourceforge.net/u/userid-None/</uri></author><id>https://sourceforge.neta9c30bac54d47f7ec5b91a1de05e9e5a9367b4d7</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;in-addr.arpa reserved query for 1.2.3.4 also matches eg. 1.2.3.44&lt;br /&gt;
change line 238 in cache.h to:&lt;/p&gt;
&lt;p&gt;if( !strcasecmp( token, ip ) ){&lt;/p&gt;
&lt;p&gt;and it work right for me&lt;br /&gt;
to lazy for a &amp;amp;quot;diff&amp;amp;quot;&lt;/p&gt;
&lt;p&gt;bye Ben&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>dproxy does not proxy MX lookups</title><link href="https://sourceforge.net/p/dproxy/bugs/4/" rel="alternate"/><published>2000-04-04T09:24:50Z</published><updated>2000-04-04T09:24:50Z</updated><author><name>Alistair Lambie</name><uri>https://sourceforge.net/u/alambie/</uri></author><id>https://sourceforge.net43536652eb8fd27b2e7ef9abd2e7ef4ac4e79e6b</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;When dproxy is sent an MX lookup request the child process segv's.  It goes into the the dns_reverse_lookup function with a name which causes the segv.&lt;/p&gt;
&lt;p&gt;This is probably more a request for enhancement, although it would be nice if it at least returned something rather than just die.&lt;/p&gt;
&lt;p&gt;I am using SuSE 6.3. &lt;/p&gt;&lt;/div&gt;</summary></entry></feed>