Daniel Hess [EMAIL PROTECTED] dixit:
It starts to fail when the dstdom_regex acl is activated.
This could be. But -- I think -- also dstdomain.
Two of my non-correct-working squid-proxy-servers have lines in
squid.conf like these:
- The one server 'acl this_name dstdomain www.domain.tld'
-
On Tue, Aug 23, 2005 at 05:14:31PM +0200, Peter Blancke wrote:
Daniel Hess [EMAIL PROTECTED] dixit:
It starts to fail when the dstdom_regex acl is activated.
This could be. But -- I think -- also dstdomain.
Yes, the problem is the ptr dns-query (get the hostname to the ip).
When you use
Sorry for once more replaying to my own mail, ... :)
On Tue, Aug 23, 2005 at 05:00:12AM +0200, Daniel Hess wrote:
Before the update (without squid-2.4.STABLE7-dns_query-4.patch)
RR-rdlength, which gets added to off, was not passed from
rfc1035RRUnpack to rfc1035NameUnpack. Now it gets passed
Hi Luigi,
On Tue, Jul 26, 2005 at 09:11:31AM +0200, Luigi Gangitano wrote:
this surely helps. Can you please tell me what DNS daemon is at work in
this case (eg. bind, pdnsd, etc.)?
I've investigated a bit further.
With the default config (with minimal changes so that the lan-clients
can use
On Tue, Aug 23, 2005 at 02:48:21AM +0200, Daniel Hess wrote:
It starts to fail when the dstdom_regex acl is activated.
I've made my way through to the actual problem (the change which
triggers the assert in line 410 lib/rfc1035.c).
Before the update (without squid-2.4.STABLE7-dns_query-4.patch)
Il giorno mar, 26/07/2005 alle 03.09 +0200, Daniel Hess ha scritto:
I can reproduce this by using wget on an URL which contains an ip (for
example: wget http://193.99.144.85/;).
Hope this helps, ...
Hi Daniel,
this surely helps. Can you please tell me what DNS daemon is at work in
this case
Luigi Gangitano [EMAIL PROTECTED] dixit:
Il giorno mar, 26/07/2005 alle 03.09 +0200, Daniel Hess ha scritto:
I can reproduce this by using wget on an URL which contains an ip
(for example: wget http://193.99.144.85/;).
Can you please tell me what DNS daemon is at work in this case
(eg.
Hi,
I can reproduce this by using wget on an URL which contains an ip (for
example: wget http://193.99.144.85/;).
Finally, this is the same issue I have with my SuSE box, but which I (and
others) wasn't able to reproduce on Woody. There seems to be another factor.
Very strange.
As I
Hi Luigi,
On Tue, Jul 26, 2005 at 09:11:31AM +0200, Luigi Gangitano wrote:
this surely helps. Can you please tell me what DNS daemon is at work in
this case (eg. bind, pdnsd, etc.)?
it is an dnscache (djbdns) running on the same host.
- Daniel
--
To UNSUBSCRIBE, email to [EMAIL
Hi all,
I prepared an unstripped version of the same binary that has been
distributed by security.d.o. It can be found at
http://people.debian.org/~luigi/squid-unstripped/
It would be helpful if somebody that can reproduce the bug could trace
it with the above binary and istructions from
Hi,
I installed the reported package on a Woody box and wasn't able to
reproduce it either. The problem on my SuSE Box seems to be of a
different nature (BTW: I found that the crash is triggered by every
numeric IP - I will work around with a redirector that tries to resolve
the IP Address to a
Hi all,
I'm investigating this issue with upstream.
squid: rfc1035.c:410: rfc1035RRUnpack: Assertion `(*off) = sz' failed.
Aborted
This is the error. Incorrect parsing of DNS replies.
Since RFC 1035 deals with DNS and the Squid patch ist meant to
specifically fix a DNS issue, I suspect
On 15/07/2005 3:33 AM, Luigi Gangitano wrote:
but didn't succeed. Can somebody please provide some more informations
like
- configuration file
- type of DNS used (BIND, dnscache, etc)
- a core file (if found)
I'm preparing a debug-enabled version to help extract more details, I'll
send to
Hi
I had very similar problems with squid_2.4.6-2woody9_i386.deb yesterday
and resolved them, like you, by reinstalling the previous package
(squid_2.4.6-2woody8_i386.deb).
[EMAIL PROTECTED] wrote:
Looking in the logfiles shows, that squid 2.4.6-2woody9 restarts very
often:
upuaut:~# grep
Peter Blancke [EMAIL PROTECTED] dixit:
I've had the same problem; since removing squids cache, new
creating the cache (squid -z) and a new start of squid, the
2.4.6-2wood9 works fine and the problem didn't turn up.
I have been pleased prematurely; today the same mistake reoccurs.
Now
Hello,
I have tried to install Version 2.4.6-2woody9 of the squid package on
our Internet Gateway (Woody). There were no error messages during
upgrade, but our Client get no connection to the proxy afterwards.
I fix this temporary by reinstalling the previous version
2.4.6-2woody8.
Looking in
[EMAIL PROTECTED] [EMAIL PROTECTED] dixit:
I have tried to install Version 2.4.6-2woody9 of the squid package
on our Internet Gateway (Woody). There were no error messages
during upgrade, but our Client get no connection to the proxy
afterwards. I fix this temporary by reinstalling the
Hi,
Just had the same Problem today on a SuSE server, where a patch was
released last week that adresses (among others) the same DNS spoofing
issue. Looks like a common bug.
Wiping the cache didn't help for me. I increased the debug level to 2
and found the following URL in my cache.log,
18 matches
Mail list logo
