As related to those bugs it is non-critical. There are three upstream
bug fixes in 3.1.20 however which close remote triggered security
problems. Merge is advised by upstream (me).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3
*** This bug is a duplicate of bug 496886 ***
https://bugs.launchpad.net/bugs/496886
** This bug has been marked a duplicate of bug 496886
Squid crashes with "assertion failed" authenticateUserAuthenticated
--
You received this bug notification because you are a member of Ubuntu
Server Te
balance_on_multiple_ip directive configures whether Squid does any
internal rotation, on/off. The 3.1 default is OFF. Turning it ON
explicitly would cause the issue described.
positive_dns_ttl causes DNS records to be discarded at a forced timeout
ignoring the upstream rotation TTL. The default
GnuTLS has been passed to the upstream bugzilla, so is on the TODO list.
However all we are seeing is demands that we do the *enormous*
conversion task for free. Nobody supposedly "needing" SSL has been
willing to contribute towards development, even as patch submissions to
assist.
I have finally
I am re-opening this due to the closure being based on an assumption
that the original report was accurate.
pt-bz refers to Portuguese reading/writing citizens of Belize (NOT
Brazil). Which is a valid ISO code missing from the squid-langpack
package.
Any information on whether Belize Portuguese d
*** This bug is a duplicate of bug 696460 ***
https://bugs.launchpad.net/bugs/696460
** This bug has been marked a duplicate of bug 696460
package squid 2.7.STABLE9-2ubuntu5 failed to install/upgrade: ErrorMessage:
podproces instalovaný post-installation skript vrátil chybový status 1
* Y
Squid does not use /var/tmp.
** Changed in: squid (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
https://bugs.launchpad.net/bugs/596041
Title:
/var/tmp is not cleared af
** Bug watch added: Squid Bugzilla #2741
http://bugs.squid-cache.org/show_bug.cgi?id=2741
** Also affects: squid via
http://bugs.squid-cache.org/show_bug.cgi?id=2741
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Serve
You should not have to recompile the kernel if its accepting connections
through TPROXY properly. Double-check the IPs squid is identifying as
the client IP though to make sure that arrival is happening correctly.
We found a small bit alignment bug in the 3.2 series not setting the
spoof flag corr
** Bug watch added: Squid Bugzilla #2827
http://bugs.squid-cache.org/show_bug.cgi?id=2827
** Also affects: squid via
http://bugs.squid-cache.org/show_bug.cgi?id=2827
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Serve
Upstream bug referenced here is about cache storage failures during
startup/reconfigure. Which seems a bit at odds with resolv.conf loading
errors, although it may be a secondary bug result of the resolv.conf
reconfigure action being successfully triggered very early after
startup.
A stack trace i
The upstream wiki is somewhat out of date. The Squid-3.3 versions of
Squid which are installed with "aptitude install squid" on current
Ubuntu do contain almost all the Squid-2 features.
The few useful ones which it omits are in later Squid versions not yet
packaged for Ubuntu, but available from
** Changed in: squid (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
https://bugs.launchpad.net/bugs/1277388
Title:
aptitude install squid installs wrong version
To manage noti
** Also affects: squid3 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: squid3 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bu
duplicate of
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
https://bugs.launchpad.net/bugs/1480900
Title:
ancient squid causes security risk
To manage
** Description changed:
- Squid's latest stable upstream version is currently 3.5.6 and fixes
+ Squid's latest stable upstream version is currently 3.5.7 and fixes
important bugs, such as the inability to fall back to IPv4 if a websites
IPv6 connectivity is broken (e.g. http://readlist.com/lis
*** This bug is a duplicate of bug 1473691 ***
https://bugs.launchpad.net/bugs/1473691
** This bug has been marked a duplicate of bug 1473691
Update to latest upstream stable release (3.5)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subsc
Upstream bug tracker for this is http://bugs.squid-
cache.org/show_bug.cgi?id=2741. The (very basic) initial stages have
been added to squid-3.5 which is now available in Debian repositories -
and enabled. There is still a lot to be done though, so it may not be
generally useful for a few versions.
The -v command line option is already available.
If that is not providing a version number then your package is more than
10 years old, contains some severe security vulnerabilities and
desperately needs upgrading.
** Changed in: squid3 (Ubuntu)
Status: New => Fix Released
--
You receive
Also please note that this is not a bug specific to Squid. It is due to
the netfilter/in.h having a cross-include collision with the linux-
headers-4.2 headers. The kernel maintainers have a patch to try to
workaround it, but any software using system headers before
netfilter/in.h will FTBS. Squid
Upstream patch at http://www.squid-
cache.org/Versions/v4/changesets/squid-4-14311.patch should apply fairly
easily to all Squid versions.
** Changed in: squid
Importance: Unknown => Critical
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscr
FYI: The libecap older than 1.0.0 and Squid older than 3.5 are in a
lock-step dependency due to the libecap API and ABI being unstable in
those versions. Even if you can get it to build the call sequence to the
API is wrong at run-time. You get to pick libecap2 (0.2) + squid (3.3,
3.4) or libecap3
This behaviour is a result of the upstream fix for upstream bug 2997. It
is still present in all Squid-3 (will be fixed in Squid-4). When Squid
is assigned an explicit listening IP and that IP has reverse-DNS it is
used instead of halting startup.
Only the first http_port or https_port is checked
Oops, sorry 3.3.3 and later are checking for '.' present in the domin
name. So yes they should be fixed in regards to this.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1098641
Title
Sorry, just read comment #3, that makes it confirmed as CVE-2013-0189
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1194310
Title:
cachemgr.cgi crashes after login
To manage notifi
Sorry, just read comment 3, that makes it confirmed as CVE-2013-0189
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1194310
Title:
cachemgr.cgi crashes after login
To manage notific
This appears to be upstream bug 3790. Which was part of
http://www.squid-cache.org/Advisories/SQUID-2012_1.txt
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-5643
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0189
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvenam
For the record, upstream patch for this was http://www.squid-
cache.org/Versions/v3/3.4/changesets/squid-3.4-13130.patch. The code
part of this should apply fine to any affected version of Squid.
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Server
squid3_ 3.3.8-1ubuntu16 resolves this for Squid
** Changed in: squid3 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1504200
Title:
libec
*** This bug is a duplicate of bug 1214379 ***
https://bugs.launchpad.net/bugs/1214379
** This bug has been marked a duplicate of bug 1214379
pinger crashed with SIGSEGV in malloc_consolidate()
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
*** This bug is a duplicate of bug 1213455 ***
https://bugs.launchpad.net/bugs/1213455
** This bug is no longer a duplicate of bug 1214806
pinger crashed with SIGSEGV in __tzfile_compute()
** This bug has been marked a duplicate of bug 1213455
pinger crashed with SIGSEGV in __strftime_in
*** This bug is a duplicate of bug 1213455 ***
https://bugs.launchpad.net/bugs/1213455
** This bug is no longer a duplicate of bug 1214806
pinger crashed with SIGSEGV in __tzfile_compute()
** This bug has been marked a duplicate of bug 1213455
pinger crashed with SIGSEGV in __strftime_in
*** This bug is a duplicate of bug 1214379 ***
https://bugs.launchpad.net/bugs/1214379
** This bug has been marked a duplicate of bug 1214379
pinger crashed with SIGSEGV in malloc_consolidate()
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I think this bug is not valid.
The config does not meet the documented requirement that the script
interpreter be a *full path* to the sript interpreter, or helper binary.
"php" is not the full path to the PHP executable.
The helper is also closing its stdin communication socket to Squid
before s
** Bug watch added: Squid Bugzilla #3852
http://bugs.squid-cache.org/show_bug.cgi?id=3852
** Changed in: squid
Importance: Medium => Unknown
** Changed in: squid
Status: Invalid => Unknown
** Changed in: squid
Remote watch: Squid Bugzilla #3453 => Squid Bugzilla #3852
--
You rece
*** This bug is a duplicate of bug 1213455 ***
https://bugs.launchpad.net/bugs/1213455
** This bug has been marked a duplicate of bug 1213455
pinger crashed with SIGSEGV in __strftime_internal()
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Description changed:
- Squid's latest stable upstream version is currently 3.5.7 and fixes
+ Squid's latest stable upstream version is currently 3.5 and fixes
important bugs, such as the inability to fall back to IPv4 if a websites
IPv6 connectivity is broken (e.g. http://readlist.com/lists
** Description changed:
Squid's latest stable upstream version is currently 3.5 and fixes
important bugs, such as the inability to fall back to IPv4 if a websites
IPv6 connectivity is broken (e.g. http://readlist.com/lists/squid-
cache.org/squid-users/11/58389.html), #1213455, #1214379, #1
** Summary changed:
- Update to latest upstream stable release (3.5)
+ squid: Update to latest upstream stable release (3.5)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1473691
Title
** Description changed:
- Squid's latest stable upstream version is currently 3.5 and fixes
- important bugs, such as the inability to fall back to IPv4 if a websites
- IPv6 connectivity is broken (e.g. http://readlist.com/lists/squid-
- cache.org/squid-users/11/58389.html), #1213455, #1214379, #1
The squid3.service file is auto-generated. The actual upstream fix was:
commit 6ac65f75a971a4a87c18766f3fe9969e91cef591
Author: Mathieu Parent
Date: Thu Oct 8 09:40:50 2015 +0200
Set pidfile for systemd's sysv-generator
This actually changes the followind settings (from systemctl cat
Fix for this has been added upstream in Debian package 3.5.14-1
** Also affects: squid3 (Debian)
Importance: Undecided
Status: New
** Changed in: squid3 (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, wh
For the record this usage of -N is an intentional addition for Upstart
integration with Squid-3. It is needed to avoid those much worse process
control start/stop issues mentioned in the report, and other less
obvious problems around the system.
The Ubuntu package dropping its Upstart integration
The upstream fix was http://www.squid-
cache.org/Versions/v3/3.5/changesets/squid-3-12982.patch - which is to
increase the number of IPs attempted to 25 instead of just 10.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubunt
And for the record. No Squid does not use libc getaddrinfo(). That API
provides speed restrictions several orders of magnitude too slow for
even small Squid installations.
** Description changed:
Many people run squid (squid-deb-proxy, or maas-proxy) to provide ubuntu
archive mirror caching a
Andres,
Because there is no way to distinguish between a local-only network and one
using NAT without actually trying to connect to the IPs (which is exactly what
Squid is doing - up to the limit of forward_max_tries). The problem is
identical and far more widespread in IPv4. Disabling IPv4 whe
Debian Sid and Jesse package squid3 includes the fix for this bug.
Please update the Ubuntu packages to match the upstream Debain
repository.
** Also affects: squid3 (Debian)
Importance: Undecided
Status: New
** Changed in: squid3 (Debian)
Status: New => Fix Released
--
You rec
This is a feature designed for maximum compatibility with other
software.
>From squid developer discussions:
" hno:
default port in accel mode is the listening port unless told otherwise by the
host header or vport. If you run Squid on port 3128 but it's actually
processing port 80 requests the
There seems to be some confusion over the way these squid processes
operates.
In your trace:
"
root 14719 0.0 0.0 24796 1076 ? Ss 14:26 0:00 /usr/sbin/squid
proxy 14721 2.2 0.2 40212 10352 ? Sl 14:26 0:00 (squid)
"
the process "/usr/sbin/squid" is a daemon supervisor. Ensuring worker
"(squid)" pr
this us a user configuration error.
** Bug watch added: Squid Bugzilla #3934
http://bugs.squid-cache.org/show_bug.cgi?id=3934
** Also affects: squid via
http://bugs.squid-cache.org/show_bug.cgi?id=3934
Importance: Unknown
Status: Unknown
** Changed in: squid (Ubuntu)
Statu
For the record:
http://www.squid-cache.org/ menu link: "Getting Squid" -> /Download/
http://www.squid-cache.org/Download/ links: "Official source code release" ->
/Versions/
http://www.squid-cache.org/Versions/ links: "langpack" -> /Versions/langpack/
(was one clicks deeper off the versi
Can anything be done to better streamline the import of this particular package
from Debian to Ubuntu?
The content installed is non-executable and relatively volatile localization
texts. The schedule Debian keeps is already on the outer border of slow for
spreading corrections.
** Summary chang
The only issue that is unclear is whether the package is on automatic-
import from Debian Testing.
Also, the package version in lucid is quite old and will need another
re-sync. I expect just prior to the April 15th translations deadline. We
should have more texts pushed through Debian QA by then.
configuration settings.
** Also affects: squid
Importance: Undecided
Status: New
** Changed in: squid3 (Ubuntu)
Sourcepackagename: squid => squid3
Assignee: (unassigned) => Amos Jeffries (squid3)
Status: Triaged => In Progress
--
tproxy support (iptables &
The auto-detect default is equivalent to "--with-gnutls --without-
openssl".
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
https://bugs.launchpad.net/bugs/16669
Title:
Squid: Compile with --enable-ssl
To manage no
55 matches
Mail list logo
