Bug#399312: cgi.cfg errors after upgrading 1.4.5 to 2.5-3

Package: nagios2 Version: 2.5-3 After upgrading from 1.4.5 , the config has been fully converted and moved to /etc/nagios2/ Previously installed were: nagios, nagios-mysql, nagios-plugins 1: The script /etc/init.d/nagios2 throws up an error each time start or restart is called. "Can't o

Bug#410375: network interfaces not autoconfigured for ipv6 after reboot

Package: linux-image-2.6.18-4-486 Version: 2.6.18-4 After upgrading to this package from linux-image-2.6.18-3-486 the network interfaces are auto-configured with IPv4 and link-local addresses. But the config for the Scope:Global addresses is not done. Router advertisements from the link router

Bug#696130: 2.1-4 upgrade error "Died at /usr/sbin/ferm line 1719"

Package: ferm Version: 2.1-4 Severity: important Upgrade to 2.1-4 dies with an error about stopping ferm. The firewall is left running, but the ferm scripts are already in place and future manual or automatic operations fail with the message "Died at /usr/sbin/ferm line 1719". By commenting

Bug#696130: 2.1-4 upgrade error "Died at /usr/sbin/ferm line 1719"

On 17/12/2012 7:25 p.m., Alexander Wirt wrote: This is funny. -3 had this problem and -4 was expected to fix this. Do you have your configuration file for me? Alex I'm reproducing with two files: /etc/ferm/ferm.conf: include 'test' ; /etc/ferm/defaults: domain (ip ip6) table filter chain

Bug#691153: squid3-dbg binary does not contain symbols

Package: squid3-dbg Source: squid3 Version: 3.1.20-1 Severity: important The squid3 binary packaged in squid3-dbg appears not to contain any symbols. Rendering it useless for debug testing on errors. Adding the following stanza to debian/rules is needed: DEB_BUILD_OPTIONS_squid3-dbg := nos

Bug#672156: Should be dropped in favour of squid3

Are the release team willing to accept a squid-3.2.1 stable release upload 4-6 weeks after Wheezy freeze? That upload will close this RC bug, a CVE security bug in both squid and squid3 packages, and a number of regular bugs. Notice the Ubuntu effort to migrate 2.7 package to 3.1 ahead of up

Bug#664051: squid3: Frequent DOS due to extreme memory consuption of Squid3

Upstream expect this bug to be fixed in the current squid3 packages available in Wheezy. While its not possible to determine with certainty from the information provided whether this is a known leak or not, there are a number of leaks and resource over-allocations fixed between 3.1.6 and 3.1.2

Bug#681122: squid3: digest_pw_auth example incorrect, missing -c switch

syntax for auth_param directive which is being documented in squid.conf.documentated Amos Jeffries Squid Project -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#681987: squid3: please add COSS support

COSS support in Squid-3 is experimental, still buggy, and is certainly not recommended for use by any of the Squid-3 developers. Amos Jeffries Squid Project -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Conta

Bug#682728: ferm: please support the TPROXY target

Package: ferm Version: 2.1-1 Severity: important Tags: patch ipv6 iptables and ip6tables support the TPROXY target, which is an important tool for removing dependency on NAT. A growing selection of system software is making use of the target, but ferm currently does not accept it as valid. T

Bug#660489: squid3: error comm_open: socket failure: (97) Address family not supported

Inspiration finally hits and we have a potential patch for this in upstream http://bugs.squid-cache.org/show_bug.cgi?id=3593 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#660489: squid3: error comm_open: socket failure: (97) Address family not supported

Tags: patch ipv6 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#672156: Should be dropped in favour of squid3

3.2.1 on or before 15 August. It will take something quite major to make us miss that goal now. Amos -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#683255: squid3: error page uses external file

series is currently under review. Amos Jeffries Squid Project -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#682822: squid3: Cleaner way to replace error text

There are three methods of server-side text replacement available through squid.conf (deny_info for targeted responses, error_default_language for custom page names, error_directory for complete page set replacement) and client-side replacement via CSS in /etc/squid3/errorpage.css configuration

Bug#703584: min-size causes squid3 to fail

The min-size= configuration option was introduced in squid-3.2 and does not exist in Squid-3.1. http://www.squid-cache.org/Doc/config/cache_dir/ You will get the same error from 3.1 whenever you try to configure it with not yet invented settings. Amos -- To UNSUBSCRIBE, email to debian-bugs

Bug#652010: squid3: ncsa_auth should support MD5 and SHA1 in htpasswd files

A partial fix for this has been accepted upstream. The fixed helper requires crypt() library support for the SHA hashed algorithm, but when that is provided will accept SHA-256, SHA-512, and Blowfish hashed passwords. http://bugs.squid-cache.org/show_bug.cgi?id=3831 http://www.squid-cache.org

Bug#705983: squid3: Please remove patching of visible_hostname

Package: suqid3 Severity: important Summary: the current squid3 packages are forcing users to manually override the package patch or face HTTP denials from upstream proxies. A good description of what users encounter is documented at http://www.squid-cache.org/mail-archive/squid-users/2

Bug#652010: squid3: ncsa_auth should support SHA1 in htpasswd file

forwarded 652010 http://bugs.squid-cache.org/show_bug.cgi?id=3831 Marking this against the upstream bug entry. I'm not completely certain whether the Debian crypt() implementation supports SHA or Blowfish, upstream debugging was done against OpenBSD which have a few strange extensions there.

Bug#180886: Please provide GNUTLS support in Squid

forwarded 180886 http://bugs.squid-cache.org/show_bug.cgi?id=2741 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#701123: squid-cgi: cachemgr.cgi crashes when passing password in form since applied, patch for CVE-2012-5643 and CVE-2013-0189

It seems library differences between 3.2+ and 3.1 caused this small piece to be missing from the 3.1 patch: http://www.squid-cache.org/Versions/v3/3.1/changesets/squid-3.1-10486.patch Amos -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Tr

Bug#701622: smitools missing dependency on libsmi

Package: smitools Version: 0.4.8+dfsg2-6 Priority: serious The smilint binary is installed as part of the smitools package and requires libsmi. But the smitools package does not depend on any package that installs libsmi.so.2 nor does it install that library itself. On a system without any sm

Bug#665499: clang: code using std::stack crashes with SIGILL when compiled with clang++

Package: clang-3.2 Version: 1:3.2repack-2 I am seeing this bug still in the clang-3.2 package. # clang++ -o test test.cc # ./test Illegal instruction # clang++ -o test test.cc -march=native # ./test # clang++ -v Debian clang version 3.2-2 (tags/RELEASE_32/final) (based on LLVM 3.2) Target: i38

Bug#702417: libmysql++-dev broken includes

Package: libmysql++-dev Version: 3.1.0-2+b1 Severity: serious When installing libmysql++-dev it pulls in several build dependencies. However a basic test application performing: #include int main(int charc, char *argv[]) { my_init(); return 0; } will fail to compile with: In file in

Bug#702417: Not a bug

This is a bug against the *libmysql++-dev* package headers, not the libmysqlclient-dev headers. Yes I could add undocumented flags, or explicit paths to the internal files of *another* library. I could also use that other libraries API directly, or write my own wrapper API. That would work as

Bug#572327: squid3: transparent/intercept port not listening on "all" interfaces

The cause of this was found and fixed upstream. I believe it is resolved in the current 3.1.1 packages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#593815: squid3: bugs.debian.org inaccessible when IPv6 is, enabled but not routed

We have just had some problem solving on the squid-users mailing list for what appears to be this same problem. The solution found there was to check "ip -6 route" and remove the route entries (default route is automatic when IPv6 is enabled). Amos Jeffries -- To UNSUBSCRIBE

Bug#521052: CVE-2009-0801: HTTP Host Header Incorrect Relay Behavior Vulnerability

A partial fix for this problem is now available at http://www.squid-cache.org/Versions/v3/3.1/changesets/squid-3.1-host-verify.patch It does not include the destination IP pinning available in the 3.2 series fix it was based on. So is not a full fix. But does include the IP verification checks

Bug#636287: squid.postrm removes /var/log/squid, even though it's needed by other packages

Since /var/log/squid/ is a private directory added by the squid package for its own use I don't think other packages should be requiring its existence without a clear dependency on the squid package which creates it. squidguard appears to be violating the FHS standard by not using /var/log/squ

Bug#622256: squid makes duplicates in cache

This behaviour you see happens when collapsed forwarding is disabled: http://www.squid-cache.org/Doc/config/collapsed_forwarding/ Objects stored will be de-duplicated when both transactions are completed in any event. AYJ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org

Bug#639755: CVE-2011-3205: squid3: Buffer overflow in Gopher reply parser

This one is far bigger than the popularity of Gopher would indicate. Attack servers are trivial to setup and triggering takes out the web service with a few packets. If one served response fails to create a DoS, the result is an FTP-like file index which merely encourages the unwitting user to

Bug#710014: squid3: Added autopkgtests

Can you document please, what all this new code is exactly? ie what is being tested, how, and why. So far as I can tell this is adding unnecessary dependencies on apache and python to make some simple proxy lookups. Upstream has run-time QA tests for Squid using perl as a backend which is alre

Bug#712754: squid3: occasionally fails assertion in commHandleRead

Control: tags wheezy This only affects the package in wheezy. Referenced patch was applied upstream in packages available in sid. Amos -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#652010: squid3: ncsa_auth should support MD5 and SHA1 in htpasswd files

The NCSA helper bundled with squid3 packages support MD5 hashes already. All it requires is the password file to be created with the -m option to htpasswd. Both salted and non-salted forms are accepted. SHA1 is an open feature request upstream, patches very welcome. Amos -- To UNSUBSCRIBE,

Bug#652010: squid3: ncsa_auth should support MD5 and SHA1 in htpasswd files

The NCSA helper bundled with squid3 packages support MD5 hashes already. All it requires is the password file to be created with the "--md5" option to htpasswd (unfortunately that is not the default output from htpasswd). Both salted and non-salted forms are accepted. SHA1 is an open feature r

Bug#672156: Should be dropped in favour of squid3

Upstream is working on a clean transition from (squid | squid3) -> squid 3.2 without the need for a removal bump. At this time it is not completely clear whether a 3.2 package will make Wheezy before freeze. I'm hopeful though. Amos (upstream maintainer) -- To UNSUBSCRIBE, email to debian-

Bug#798935: Starting dnsmasq deadlock with /etc/resolvconf/update-libc.d/squid3

tags severity important On Mon, 14 Sep 2015 11:11:45 +0200 Patrick Cernko wrote: > > On a system with systemd, dnsmasq and resolvconf installed, the > /etc/resolvconf/update-libc.d/squid3 hook prevents dnsmasq from > starting. That hints that the dnsmasq startup sequence is being done the wrong w

Bug#858556: In case the code is not anywhere...

On 26/03/2017 1:34 p.m., Santiago Garcia Mantinan wrote: >> Maybe it was just that the original code had to be at the >> upgrade|install-upgrade >> block of the case? >> >> But why is the -d /etc/squid3 checked? > IIRC this is for transitions where _both_ squid and squid3 packages are already in

Bug#859072: Contribute extended dep8 testing

Thank you. Biggest issue I see is a bunch of License problems - which will affect Ubuntu inclusion in similar ways IMHO: * debian/tests/test-squid.py not being compatible with the .deb package License. Squid and the .deb packaging are at least GPLv2+. This script states v2-only. It will need to

Bug#859072: Contribute extended dep8 testing

FYI: I am just one of a team in Debian, not 'the' maintainer, Luigi is that. So I am just auditing the patch as presented for inclusion to Debian. On Thu, 30 Mar 2017 14:26:59 +0200 Christian Ehrhardt wrote: > On Thu, Mar 30, 2017 at 1:28 PM, Amos Jeffries wrote: > > > Than

Bug#857137: squid3: on Debian Jessie: /etc/init.d/squid3 returncode is wrong with conf file with errors

Control: notfixed -1 3.5.12-1 Apologies, I misread the diff. It was correct and I have applied the patch for next unstable upload. For Jesse both the upstream and Eric's patches need to be applied to close this bug properly. Amos

Bug#857137: squid3: on Debian Jessie: /etc/init.d/squid3 returncode is wrong with conf file with errors

Control: fixed -1 3.5.12-1 The regex is correct, but Squid itself is not following its own documentation about some FATAL messages. The result is that some types of errors are detected but some are not. The upstream patch fixing this should be applied instead, and can be found at

Bug#855268: squid: PID file at wrong place -> not installable

> However, some init scripts can contain hacky or racy code and this could > potentially lead to such issues in systemd. But again, I'm not able to > reproduce > the problem which is why I am downgrading the severity of this bug report and > tagging it accordingly. systemd is racing the Squid int

Bug#858556: squid 3.5.23-2: upgrade from jesse squid3 fails

Package: squid Version: 3.5.23-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts stop From: Andreas Beckmann Date: Thu, 23 Mar 2017 04:04:15 +0100 Hi, the last upload introduced a regression: Selecting previously unselected package squid. (Reading database ... (Reading

Bug#855268: squid: PID file at wrong place -> not installable

On Thu, 16 Feb 2017 09:25:33 +0100 Andreas Rittershofer wrote: > Package: squid > Version: 3.5.23-1 > > * What led up to the situation? > > I tried to install squid via apt-get install squid > > The problem is here: > > > Feb 16 08:32:08 dx151 systemd[1]: Starting LSB: Squid HTTP Proxy > version

Bug#853668: squid3: ftbfs with GCC-7

Forwarded: 853668 http://bugs.squid-cache.org/show_bug.cgi?id=4671 thanks This is still being worked on upstream. The mentioned memory allocator issues are now gone. However there are quite a few additional warnings which are causing FTBS at later stages. Amos

Bug#859072: Contribute extended dep8 testing

Thank you. I am adding these to the Squid-4 package. Amos

Bug#824571: FTBFS of mosquitto on Hurd-i386

Package: mosquitto Version: 1.4.8-1 Severity: important Hi, the mosquitto package fails to build on Hurd citing the following error: > In file included from /usr/include/errno.h:35:0, > from /usr/include/i386-gnu/bits/spin-lock-inline.h:35, > from /usr/include/pt

Bug#794536: squid3: FTBS on GCC-5

Package: squid3 Version: 3.5.5-1 Severity: important squid3 package is FTBS in sid due to libstdc++6 transition. Adding this bug to hold squid3 in unstable until we can sort out libecap3. Amos -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscrib

Bug#794639: please delay pool creation until squid3 is actually started, to support _installations_ without /dev/shm mounted

Control: tags 794639 pending The message was being logged when postinst script ran squid to format any filesystem areas to be used by the squid cache. New installations of the current version do not use disk / filesystem caches, and the squid.rc init script was duplicating the action for upgrades

Bug#826043: apt: gpg validation fails on hurd

On 3/06/2016 10:38 p.m., David Kalnischkies wrote: > > btw: I just checked: I introduced the first of the two finds (which is > the more obvious problem as that codepath is used more) on 7 Jul 2015 > (25f27319) [the other is 6 Dec 2015], so that problem isn't recent but > lingers there since 1.1 a

Bug#819523: squid3 in wheezy-backports has unmet dependencies

Luigi, Since this is in the amd64 package and wheezy-backports does not even contain the libraries mentioned I suspect this is due to the package binary being the one generated in your build environment for upload. Requesting a re-build on the normal amd64 buildd should resolve this. Amos

Bug#827256: squid3: helper program basic_smb_auth don't work

On Tue, 14 Jun 2016 11:07:52 +0200 herrmann wrote: > > please have a look at Bug #793400. I couldn't reopen this bug, so I had to file > this new one, but it is - in each detail - the very same regression again. That bug (and this behaviour) was fixed by upstream changes in 3.5.7. There is no "ag

Bug#822952: squid3-3.4.8-6

Control: severity -1 wishlist Debian packages are not built with OpenSSL, which makes this not of much relevance for Debian. Upstream supported releases already contain this fix. So if one was following upstream advice and building the latest Squid code for TLS/SSL there would be no problem. Amo

Bug#823968: squid3: CVE-2016-4553 CVE-2016-4554 CVE-2016-4555 CVE-2016-4556

CVE-2016-4553: Patch for 3.4 and older is now available at . CVE-2016-4554: Additional changes are needed than those initially linked to. see the advisory URL for updated patch links. CVE-2016-4555: Squid-3.1 in whee

Bug#770419: postgresql-9.4: Upgrade to 9.4~rc1-1 fails

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: postgresql-9.4 Version: 9.4~rc1-1 Severity: grave Justification: renders package unusable This is addendum to bug #764705 and #768009. Opening a new report since mail replying to update those is rejected "550 Unknown or archived bug" The in

Bug#793128: squid3: CVE-2015-5400: information disclosure due to incorrect handling of peer responses

On Tue, 21 Jul 2015 16:52:18 +0200 Salvatore Bonaccorso wrote: > > [0] https://security-tracker.debian.org/tracker/CVE-2015-5400 > > Please adjust the affected versions in the BTS as needed. In the tracker page I see a note that "squid" packages are not affected due to code not existing. This is i

Bug#793487: squid: fails to install: FATAL: Ipc::Mem::Segment::create failed to shm_open(/squid-cf__metadata.shm): (13) Permission denied

Squid needs the /dev/shm device to be mounted in its normal chmod 777 state. I believe that is taken care of on regular machinery by the init script / system boot dependencies. If not, then ideas on how to ensure it is mounted properly are welcome. Amos -- To UNSUBSCRIBE, email to debian-bugs

Bug#777195: [squid3] tcp_outgoing_address ignored

On Fri, 6 Feb 2015 11:45:05 +0500 Roman Mamedov wrote: > > Hello, > > On some occasions I was using the directive "tcp_outgoing_address 0.0.0.0" to > force Squid on a dual-stack host to be IPv4-only. > > This works fine on 3.1.20-2.2+deb7u2 currently in Wheezy. That behaviour was a bug. It caused

Bug#760303: squid 3.3.8-1.2 segfaults during initscript start/restart

Can someone able to replicate this issue please test the upstream patch: http://www.squid-cache.org/Versions/v3/3.5/changesets/squid-3-13407.patch Amos -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian

Bug#771778: squid3: Pinger segfault on free()

On Tue, 2 Dec 2014 11:47:48 +0100 =?windows-1252?Q?L.P.H._van_Belle?= wrote: > extra info. > > This is on debian wheezy, squid recompiled from jesse with icap and i did rebuild to a deb : squidclamav 6.11 > bug 760303, which looks like it. That bug (and this one) is unrelated to squidclamav. The

Bug#728144: squid3: Pinger Segmentation fault in Debug::finishDebug on delete CurrentDebug;

forwarded 728144 http://bugs.squid-cache.org/show_bug.cgi?id=2656 Amos -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#641944: squid3: SSL unavailable in Squid3. Request SSL-enabled version be available under non-free package set.

forwarded 641944 http://bugs.squid-cache.org/show_bug.cgi?id=2741 Upstream work is being tracked in their bugzilla. Amos -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#742425: assertion error when using URLS with ipv4+ipv6 hostnames

forwarded 742425 http://bugs.squid-cache.org/show_bug.cgi?id=3760 Amos -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#776463: squid3: Excessive memory and CPU consumption when performing NTLM or Negotiate authentication

Severity: grave Amos -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#765479: squid3: Seem to ignore size restriction set by cache_dir (overflow partition)

Upstream work recently indicates that this may also be related to cache_swap_high garbage collection issues. BUT we still need information about what HDD format has been used, and now also what traffic rates are happening at the time of overflow. Amos

Bug#728144: Bug#771778: squid3: Pinger segfault with libc

severity 728144 serious notforwarded 728144 merge 771778 728144 thanks I think we have enough hints now to say that the original reports initiating #771778 and #728144 are the same segfault. I was wrong about the link to upstream bug #2656 for these two crashes, that was for the third one that wa

Bug#728144: squid3: Pinger Segmentation fault in Debug::finishDebug on delete CurrentDebug;

tags 728144 +jesse fixed 728144 3.5.10-1 thanks The patch confirmed by Geralt as fixing this was finalized as upstream patch which still needs to be applied to the 3.4 Jesse packages. I am marking this as fixed in the c

Bug#761159: squid3: pam_auth does not work - needs setuid/setgid

Control: notfound 761159 squid3/3.5.10-1 This issue seems to have disappeared again sometime before 3.5.10. I am able to use the PAM helper just fine for any user account running as a non-root user. Amos

Bug#800341: squid3: systemctl reports squid is running when there is a bungled squid.conf and it has exited.

Hi Alex, Thank you for this report. To summarize: * this appears to be a bug in systemd, or maybe systemd-shim * the systemd init.d script handler is lying and corrupting systemd state On Mon, 28 Sep 2015 14:26:00 +1300 Alex King wrote: > > For example, with squid running, add a nonsense line i

Bug#800341: Fixed in git

On 8/10/2015 8:46 p.m., Mathieu Parent wrote: > Hello, > > I have fixed both problems in git. > > I think commits 444a7fb4df and 6ac65f75a971a4a should be applied for > jessie too. What do you think? NB: the second commit should use > "pidfile: /var/run/squid3.pid" on jessie. > I think this nee

Bug#791247: pstoedit: library transition may be needed when GCC 5 is the default

Even weak symbols have some potential to cause problems. Particularly since templates are involved here. It looks to me like the library uses string types internally, but would prefer to link the libc implementations. It may publish other ABI symbols based on the templates sized or padded to match

Bug#801564: squid: prompting due to modified conffiles which were not modified by the user: /etc/squid/squid.conf

We have the problem that the Squid-2.7 configuration settings which are always present in 2.7 configs, will not run in squid-3.5. In fact will cause the 3.5 process to halt with a fatal error. So we have a mandatory automated edit by during the upgrade. How does one avoid or suppress the dpkg quer

Bug#786855: squid3: doesn't start with adaptation_access option

merge 786855 760303 thanks The problem is memory free() by global object deallocators. Fixed upsream in 3.5 as noted in bug 760303 Amos -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#780904: squid3: assertion failed: MemBuf.cc:280: "size < capacity"

Severity: normal merge 766326 780904 thanks As mentioned this is a duplicate of an issue only affecting Wheezy. Amos -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#780904: squid3: assertion failed: MemBuf.cc:280: "size < capacity"

Package: squid3 Version: 3.1.20-2.2+deb7u2 Severity: normal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#765479: squid3: Seem to ignore size restriction set by cache_dir (overflow partition)

What filesystem type is in use for the device the cache_dir is stored on? Upstream have known issues with ZFS and XFS where the underlying FS uses different amounts of storage space for files than gets reported to Squid. This usually results in smaller on-disk than Squid is aware, but it could as

Bug#728144: squid3: Pinger Segmentation fault in debugFinish from IcmpPinger.cc:190

tags 728144 + moreinfo thanks The CVE issues were discovered by crashes remaining after the TZ issue was resolved. It appears that the TZ issue was one of at least 5 different crashes which could result from the CVE-2014-7142 bug. Both CVE bugs are confirmed resolved. But that does not mean ping

Bug#153712: squidclient: an example init.d script to control offline_mode

"offline_mode" in current packages does not do what the reporter seems to think. It has always been badly named, and actually switches Squid between normal proxy behaviour and "greedy" caching behavour. It does help with intermittent connections but to benefit in that use-case the offline_mode sho

Bug#641944: squid3: SSL unavailable in Squid3. Request SSL-enabled version be available under non-free package set.

FYI: upstream are working on GnuTLS support for a fully free SSL enabled package. This has not made it in time for Jesse. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#760303: squid 3.3.8-1.2 segfaults during initscript start/restart

forwarded 760303 http://bugs.squid-cache.org/show_bug.cgi?id=4057 On Fri, 12 Sep 2014 08:01:25 -0500 Dale Schroeder wrote: > I don't understand how a log rotation can fail, yet succeed. The way the log rotation integrates with external log management tools is that Squid leaves the external tool

Bug#813854: squid: Please rebuild with '--enable-http-violations'

On Sat, 06 Feb 2016 00:50:53 +0100 Kristijan Caprdja wrote: > > In order to remove specific headers from responses, squid must be > built with '--enable-http-violations'. > This feature seems to have been built-in in the version 2 (present in wheezy). In the version 3 this is > a compile time optio

Bug#814333: squid3: SSL error "sec_error_inadequate_key_usage" in the browser

these irrelevant to the Debian security team. Security issues in the custom additions are *your* problem to track and fix. I highly recommend building from the Stretch package instead of patching. Amos Jeffries (Squid upstream)

Bug#811014: Squid 3.5 does not recognize an option "https_port" in squid.conf

? No. The squid binary requires functionality from OpenSSL APIs which is not provided through that wrapper. Upstream is aiming at full native GnuTLS support instead. Amos Jeffries Squid Sofware Foundation

Bug#818744: courier-authdaemon: init.d/courier-authdaemon script hangs

Package: courier-authdaemon Version: 0.66.4-5 Severity: grave The /etc/init.d/courier-authdaemon script hangs on any use. It contains the suspicious I/O loop: if [ -r "$TMPFILES" ]; then while read type path mode user group; do if [ "$type" = "d" ]; then

Bug#818747: courier-authdaemon: init script does not work

Package: courier-authdaemon Version: 0.66.4-5 Severity: grave After a recent upgrade to courier-authdaemon the init scripts have ceased controlling the daemon processes. Producing the error : Unknown option '-' NP: this is after the workaround to bug #818744 has been added to let the init scr

Bug#818747: closed

Control: found 818747 0.66.4-6 Unfortunately the fix applied is still not working properly. Hard-coding the action that the script performs as "start" only works for starting the daemons, not any other init actions. It can start the daemons now: # ps aux | grep "courier-auth" # /etc/init.d/cour

Bug#819102: [squid-users] Negotiate wrappter returns AF = on Debian Jessie

On 18/03/2016 7:29 a.m., James Zuelow wrote: > Hello - > > I have Squid 3.4.8 installed on Debian Jessie. > > I'm using the negotiate wrapper configured like this: > > auth_param negotiate program /usr/lib/squid3/negotiate_wrapper_auth -d \ >--kerberos /usr/lib/squid3/negotiate_kerberos_auth

Bug#817135: jesred: please update links to Squid proxy

Package: jesred Version: 1.2pl1-21 Severity: minor The Debian 'squid3' package has been renamed to 'squid' in Testing/stretch. The 'squid3' package is now a transitional temporary package that will be removed at some point. Please update your package to "Depends: squid (>= 3.4)". If there are a

Bug#817137: calamaris: please update links to Squid proxy

Package: calamaris Version: 2.99.4.5-1 Severity: minor The Debian 'squid3' package has been renamed to 'squid' in Testing/stretch. The 'squid3' package is now a transitional temporary package that will be removed at some point. It appears that the version requirement is also long stale on the ex

Bug#817138: education-main-server: please update links to Squid proxy

Package: education-main-server Version: 1.812 Severity: minor The Debian 'squid3' package has been renamed to 'squid' in Testing/stretch. The 'squid3' package is now a transitional temporary package that will be removed at some point. Please update your package to "Recommends: squid". If there

Bug#817134: squidguard: please update links to Squid proxy

Package: squidguard Version: 1.5-5 Severity: minor The Debian 'squid3' package has been renamed to 'squid' in Testing/stretch. The 'squid3' package is now a transitional temporary package that will be removed at some point. Please update your package to "Recommends: squid (>= 3.4.0)". If there

Bug#817136: c-icap: please update links to Squid proxy

Package: c-icap Version: 1:0.4.2-2 Severity: minor The Debian 'squid3' package has been renamed to 'squid' in Testing/stretch. The 'squid3' package is now a transitional temporary package that will be removed at some point. Please update your package to be "Suggests: squid (>= 3)". If there are

Bug#808095: squid3: Squid3 UNAVAILABLE

On Tue, 15 Dec 2015 15:52:40 -0800 root wrote: > > Tried installing squid 3 on wheezy with aptitude with following error: > > squid3:i386 depends on logrotate:i386 (>= 3.5.4-1) > squid3:i386 depends on netbase:i386 [UNAVAILABLE] > squid3:i386 depends on squid3-common:i386 (= 3.1.20-2.2deb7ue) [UNAV

Bug#784876: squid3: not compiled with -fpic/-fPIC causes execmod issue

On Wed, 22 Jul 2015 17:57:46 +0200 Luigi Gangitano wrote: > Hi Russel, > > Thanks for taking your time and reporting this bug. I did not understand completely what it’s going on and maybe you can help me find out. > > From my understanding: > > - no library is compiled from squid3 sources, thus -

Bug#862915: squid: please drop required dependency on logrotate

FYI: The cache.log, store log, and HDD swap.state journals produced by Squid are system-specific and not able to be sent to any remote logging systems. Logrotate is still the best system in Debian (as far as I am aware anyhow) to manage those log files needs. Where and how the access.log re

Bug#864389: squid: Regression - after upgrade, squid takes over minute to display a web page

FYI: the recent few updates have been for bugs in the install/upgrade process. This type of behaviour is usually encountered when there is a large config file to load, the machine is under high CPU load starting helpers, DNS issues, or network latency to some service that is needed. Anything

Bug#864715: USB netinst fails to identify /media/cdrom as a path for base system packages or /cdrom mounting

Package: installation-reports On running the installer manually from inside the OEM Windows installed, everything appeared to run smoothly up to the reboot following partition and formatting of the machines drives. On that boot the installer now running off the HDD began looping at the "Instal

Bug#864715: USB netinst fails to identify /media/cdrom as a path for base system packages or /cdrom mounting

On 14/06/17 00:44, Steve McIntyre wrote: On Tue, Jun 13, 2017 at 11:39:46PM +1200, Amos Jeffries wrote: Package: installation-reports On running the installer manually from inside the OEM Windows installed, everything appeared to run smoothly up to the reboot following partition and formatting

Bug#864715: USB netinst fails to identify /media/cdrom as a path for base system packages or /cdrom mounting

On 14/06/17 03:38, Steve McIntyre wrote: On Wed, Jun 14, 2017 at 02:41:32AM +1200, Amos Jeffries wrote: On 14/06/17 00:44, Steve McIntyre wrote: On Tue, Jun 13, 2017 at 11:39:46PM +1200, Amos Jeffries wrote: Package: installation-reports On running the installer manually from inside the OEM

  1   2   3   >