From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Revert "proxy.cgi: Fix for Bug #12826 'squid >=5 crashes on literal IPv6 addresses'"
Date: Mon, 08 Jan 2024 18:31:00 +0000 [thread overview]
Message-ID: <a40f196b-3680-433f-874a-1459a46e7f98@ipfire.org> (raw)
In-Reply-To: <20240108164248.3794991-1-michael.tremer@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1469 bytes --]
Acked-by: Peter Müller <peter.mueller(a)ipfire.org>
> This reverts commit e0be9eab47d621545e5498c32c0fef39f7ef84a9.
>
> This change is now producing problems on IPv6-enabled systems as it will
> deny access to any website that is IPv6-enabled as well, even if the
> client connected using IPv4.
>
> I have tested if squid is now running on fine on systems where IPv6 is
> disabled and can confirm that its running just fine.
>
> Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
> ---
> html/cgi-bin/proxy.cgi | 12 +-----------
> 1 file changed, 1 insertion(+), 11 deletions(-)
>
> diff --git a/html/cgi-bin/proxy.cgi b/html/cgi-bin/proxy.cgi
> index 71be315f6..c8e3576df 100644
> --- a/html/cgi-bin/proxy.cgi
> +++ b/html/cgi-bin/proxy.cgi
> @@ -3525,19 +3525,9 @@ END
> $_ =~ s/__PROXY_PORT__/$proxysettings{'PROXY_PORT'}/;
> print FILE $_;
> }
> - print FILE "\n#End of custom includes\n\n";
> + print FILE "\n#End of custom includes\n";
> close (ACL);
> }
> -
> - print FILE <<END
> -# Prevent ipv6 requests to avoid crash in squid > 5.x
> -acl to_ipv6 dst ipv6
> -acl from_ipv6 src ipv6
> -http_access deny to_ipv6
> -http_access deny from_ipv6
> -END
> - ;
> -
> if ((!-z $extgrp) && ($proxysettings{'AUTH_METHOD'} eq 'ncsa') && ($proxysettings{'NCSA_BYPASS_REDIR'} eq 'on')) { print FILE "\nredirector_access deny for_extended_users\n"; }
>
> # Check if squidclamav is enabled.
prev parent reply other threads:[~2024-01-08 18:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-08 16:42 Michael Tremer
2024-01-08 18:31 ` Peter Müller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a40f196b-3680-433f-874a-1459a46e7f98@ipfire.org \
--to=peter.mueller@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox