Bug#961907: ca-certificates: Remove expired mozilla/AddTrust_External_Root.crt
This is accurate to my understanding of the situation. On Mon, Jun 1, 2020 at 11:33 AM Kurt Roeckx wrote: > Just to clarify, as I understand it, openssl 1.0.2 (so libssl1.0.2 > in oldstable) still has the problem, which means things like > libcurl in oldstable have that problem. And removing the > certificate from the trust store fixes it. > > > Kurt > >
Bug#961907: ca-certificates: Remove expired mozilla/AddTrust_External_Root.crt
On Mon, Jun 1, 2020 at 1:29 AM Axel Beckert wrote:
> > You will need to workaround this. As such this motivates critical me
> think.
>
> I think "grave" is severe enough, as it "only" breaks HTTPS including
> apt with HTTPS-based mirrors (as the one mentioned above) and hence
> only "unrelated software/packages", not the whole system (like the
> kernel or the bootloader would do if the system won't boot anymore
> after an upgrade).
>
ok.
I read the description about unrelated software a bit differently indeed.
("makes unrelated software on the system (or the whole system) break, or
causes serious data loss, or introduces a security hole on systems where
you install the package.")
> > just doing a straight up curl will hang until timeout. With the expired
> > cert disabled this is bypassaed (without curl -k).
>
> Nope. curl exits immediately for me, at least in unstable (7.68.0-1):
>
Indeed. Sorry, me being inaccurate. I was testing this on old stable.
As you noted later on as well =)
Ack, stretch is affected, too, at least with lynx and — funnily again
> — curl (7.52.1-5+deb9u10).
>
Thanks for digging further into this issue.
Bug#672695: wordpress: no sane way for security updates in stable releases
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2012-05-13 14:54, Yves-Alexis Perez wrote: Wordpress upstream doesn't seem to be able to support a stable branch long enough for us (and I don't blame them for that, we do know how painful it is). This pretty much sounds like the web browser situation where we don't support the current version for the entire life cycle of the stable release. Document and be done with it. http://www.debian.org/releases/stable/i386/release-notes/ch-information.en.html#browser-security - -- brother http://sis.bthstudent.se -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBCAAGBQJPsNiFAAoJEJbdSEaj0jV7pWEH/j3mqJqcUMQ4gyzu8yANpAf0 pM4nxSqc4bey43VXBluunNO67yiJAPv3WDnuhoBNcCm43+Q8EN+uC1x2PukMVNvD hUIfT3TafJ5YVMV/lhnek0EayUOaxm+B/Tn1ocCgke4b9gBB+U9lkaAfIf+wPMNs dTmY+jOM6S3TPKWyjDGXYvp1EQlZGYKvUyZ0gBOH/srvt7uWM4AVmPSDL0DtI1WV ELRucoPNs5n5IZhnPywHo2Y8JmGROhkU3BJlkV9YcS1MheIW+KdMQbh97Ljsspwz sgbW0EYiwscFV5NDzAfi+o9bEEabO/BXZalYaIWi1ah2AAJFhzlNadc11vGuW1Q= =BPA0 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627958: Pootle is not compatible with django 1.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2011-05-26 19:29, Christian PERRIER wrote: Once upon a time, there was an intent to work on new upstream version integration. I was planning to do some initial work but left it unachievedand I don't really foresee when I can work again on this. Maybe the package should be orphaned? It would be really disappointing to me but I am not skilled enough to do anything about it. I mostly added the bug report to make it obvious to others that might pop into the problem. Maybe the install base for packaged pootle on debian is really slim or less than that... - -- brother http://sis.bthstudent.se -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBCAAGBQJN34ysAAoJEJbdSEaj0jV7EwEIAKvnuSENVt6lmEfpwEtnyZwP zMCOfptbzSL3XdIrrhVnlkQA91Vu1sq0V/5DM1icZco3C2ytcDh5aofTpsLB0cw/ B9TNrch3GGFhH7y8l2m4KmQutW/BjVjSeGhT526lNZm/hmW5hY4Ng/Gx9t0yq4pr e0f1r5MgpzOIOi5p/FlzUGL/NS37FQCSElSFr0OjSZyKu1fAUH1X0YcBY/rB+WZ/ KHIDubdTQdXs3XsjGTNc4Dag7S4ommXx9i/YWnZsjZRCIdTMnOVKl1kw8WZwCmEr 04P85lRGsqxOY3yWOmNUEbRBBz49vFjmDtjCcyFnQrloqDKnyLt1SjN3pClKd3U= =23Dh -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627958: workaround
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 as expected it will work to install the python-django package from squeeze (and I guess you will want to HOLD it there until this is solved =)) to make it work again. peace out. - -- brother http://sis.bthstudent.se -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBCAAGBQJN3l4LAAoJEJbdSEaj0jV7NV4H/jVIfmC6STPfOcWRk4onxtmJ wAMe9XyhNCKonoelD/dVhHVcniEEPM5+AVT9VQuM9CH7LQVwLvJJL4IMU/1vg1Vp /yfs2D1UTgmyl5up9S65g1GtngW4myHSZieeWC+inps4a/PeHI5mPOis9ZyFQiWe Kz4PfZUXagY5boe8OzebMomX/GNq7mH4m3gn4MYsD/KN/OLqtMrxXExWhlnJpKrA 7+ZnvxYyyVCX9swja06Uus0jLjaz3yG2pyINbWJxrRTsW+2aRqfGmuiDPe1o7THr Ne965kJq/d/LpX2rQhhztWvMbL6qTlALYiK6dZRuLN+uEmPwqE8mOXHXhpKL1hM= =xefy -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627958: Pootle is not compatible with django 1.3
package: pootle
severity: grave
After a safe-upgrade and dist-upgrade to wheezy from squeeze my Pootle
setup does not work and leaves the following in the Apache error log:
[Wed May 25 20:29:08 2011] [error] [client 81.170.177.108] mod_wsgi (pid=5264):
Exception occurred processing WSGI script '/usr/share/doc/pootle/wsgi.py'.
[Wed May 25 20:29:08 2011] [error] [client 81.170.177.108] Traceback (most
recent call last):
[Wed May 25 20:29:08 2011] [error] [client 81.170.177.108] File
/usr/lib/pymodules/python2.6/django/core/handlers/wsgi.py, line 250, in
__call__
[Wed May 25 20:29:08 2011] [error] [client 81.170.177.108]
self.load_middleware()
[Wed May 25 20:29:08 2011] [error] [client 81.170.177.108] File
/usr/lib/pymodules/python2.6/django/core/handlers/base.py, line 47, in
load_middleware
[Wed May 25 20:29:08 2011] [error] [client 81.170.177.108] raise
exceptions.ImproperlyConfigured('Error importing middleware %s: %s' %
(mw_module, e))
[Wed May 25 20:29:08 2011] [error] [client 81.170.177.108] ImproperlyConfigured: Error
importing middleware pootle_misc.middleware.siteconfig: No module named
thread_support
this is my apache virtual host
VirtualHost *:80
ServerAdmin brot...@bsnet.se
ServerName pootle.lxde.bsnet.se
# point at the wsgi loader script
WSGIScriptAlias / /usr/share/doc/pootle/wsgi.py
# directly serve static files like css and images, no need to go
through mod_wsgi and django
Alias /html /usr/share/pootle/html
Directory /usr/share/pootle/html
Order deny,allow
Allow from all
/Directory
LogLevel warn
ErrorLog /var/log/apache2/pootle-error.log
CustomLog /var/log/apache2/pootle-access.log combined
# Allow downloading translation files directly
Alias /export /var/lib/pootle/po
Directory /var/lib/pootle/po
Order deny,allow
Allow from all
/Directory
/VirtualHost
found this build log that hilighted the error earlier.
http://piuparts.debian.org/sid/fail/pootle_2.0.5-0.3.log
--
/brother
http://martin.bagge.nu
A vigenere cipher with the Key BRUCESCHNEIER is in fact unbreakable.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588370: symbol not found: 'grub_xputs'
On 2010-07-08 12:31, Colin Watson wrote: This means that your GRUB core image, as installed by grub-install, and your GRUB modules in /boot/grub are out of sync. This happens when you grub-install to a location other than that from which your computer actually boots. I did manage to get a CD to burn the Live image of ubuntu to and using that to create the chroot as described in the link I found earlier. It all worked after that. Sorry to bother. -- brother http://sis.bthstudent.se -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588370: symbol not found: 'grub_xputs'
severity: critical package: grub2 I am not sure but I do think I did a dist-upgrade in sid and installd grub2 to replace the old solution. I haven't used the computer for some days now but it can not boot anymore. Right after Welcome to grub! it drops to the grub rescue prompt. I can list my drives with ls. I can set root to hd0,1 and list the file system for / as far as I can tell. When doing insmod /boot/grub/linux.mod I get the grub_xputs error above. What to do? found some livecd suggestion at #grub at freenode and will try to test that during the coming week. http://grub.enbug.org/Grub2LiveCdInstallGuide -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#580553: related to #575150
I think this is the same error as in #575150. I do think the RC is appropriate and that should be present still if the bugs merge. -- brother -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#346226: txt2regex: syntax error on line 520
Package: txt2regex
Version: 0.8-2
Severity: grave
Justification: renders package unusable
Just installed txt2reg via apt and got the following error on the first (and
for that
matter second execution:
[EMAIL PROTECTED]:~$ txt2regex
/usr/bin/txt2regex: line 520: syntax error near unexpected token `('
/usr/bin/txt2regex: line 520: ` eval Menui=(\[EMAIL PROTECTED]);
menu_n=$((${#Menui[*]}-1))
# ini'
And then it stops. Two of my unstable machines shows this behaviour, a stable
machine
runs the program with no errors.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14-2-686-smp
Locale: LANG=sv_SE, LC_CTYPE=sv_SE (charmap=ISO-8859-1)
Versions of packages txt2regex depends on:
ii bash 3.1-1 The GNU Bourne Again SHell
txt2regex recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#729991: syslog-ng-core uninstallable
> Bug#729991: syslog-ng-core uninstallable debian-bugs-rc -- Thread -- -- Date -- Bug#729991: syslog-ng-core uninstallable Martin Bagge / brother Processed: Re: Bug#729991: syslog-ng-core uninstallable Debian Bug Tracking System Bug#729991: syslog-ng-core uninstallable Andrei POPESCU Bug#729991: syslog-ng-core uninstallable Gergely Nagy Bug#729991: syslog-ng-core uninstallable Martin Bagge / brother Bug#729991: syslog-ng-core uninstallable Gergely Nagy Bug#729991: marked as done (syslog-ng-core uninstallable) Debian Bug Tracking System Reply via email to
Bug#729991: syslog-ng-core uninstallable
> Bug#729991: syslog-ng-core uninstallable debian-bugs-rc -- Thread -- -- Date -- Bug#729991: syslog-ng-core uninstallable Martin Bagge / brother Processed: Re: Bug#729991: syslog-ng-core uninstallable Debian Bug Tracking System Bug#729991: syslog-ng-core uninstallable Andrei POPESCU Bug#729991: syslog-ng-core uninstallable Gergely Nagy Bug#729991: syslog-ng-core uninstallable Martin Bagge / brother Bug#729991: syslog-ng-core uninstallable Gergely Nagy Reply via email to Bug#729991: syslog-ng-core uninstallable Martin Bagge / brother Processed: Re: Bug#729991: syslog-ng-core uninstallable Debian Bug Tracking System Bug#729991: syslog-ng-core uninstallable Andrei POPESCU Bug#729991: syslog-ng-core uninstallable Gergely Nagy Bug#729991: syslog-ng-core uninstallable Martin Bagge / brother Bug#729991: syslog-ng-core uninstallable Gergely Nagy Bug#729991: marked as done (syslog-ng-core uninstallable) Debian Bug Tracking System Reply via email to
Bug#729991: syslog-ng-core uninstallable
> Processed: Re: Bug#729991: syslog-ng-core uninstallable debian-bugs-rc -- Thread -- -- Date -- Bug#729991: syslog-ng-core uninstallable Martin Bagge / brother Processed: Re: Bug#729991: syslog-ng-core uninstallable Debian Bug Tracking System Bug#729991: syslog-ng-core uninstallable Andrei POPESCU Bug#729991: syslog-ng-core uninstallable Gergely Nagy Bug#729991: syslog-ng-core uninstallable Martin Bagge / brother Bug#729991: syslog-ng-core uninstallable Gergely Nagy Reply via email to Bug#729991: syslog-ng-core uninstallable Martin Bagge / brother Processed: Re: Bug#729991: syslog-ng-core uninstallable Debian Bug Tracking System Bug#729991: syslog-ng-core uninstallable Andrei POPESCU Bug#729991: syslog-ng-core uninstallable Gergely Nagy Bug#729991: syslog-ng-core uninstallable Martin Bagge / brother Bug#729991: syslog-ng-core uninstallable Gergely Nagy Bug#729991: marked as done (syslog-ng-core uninstallable) Debian Bug Tracking System Reply via email to
Bug#729991: syslog-ng-core uninstallable
> Bug#729991: syslog-ng-core uninstallable debian-bugs-rc -- Thread -- -- Date -- Bug#729991: syslog-ng-core uninstallable Martin Bagge / brother Processed: Re: Bug#729991: syslog-ng-core uninstallable Debian Bug Tracking System Bug#729991: syslog-ng-core uninstallable Andrei POPESCU Bug#729991: syslog-ng-core uninstallable Gergely Nagy Bug#729991: syslog-ng-core uninstallable Martin Bagge / brother Bug#729991: syslog-ng-core uninstallable Gergely Nagy Reply via email to Bug#729991: syslog-ng-core uninstallable Martin Bagge / brother Processed: Re: Bug#729991: syslog-ng-core uninstallable Debian Bug Tracking System Bug#729991: syslog-ng-core uninstallable Andrei POPESCU Bug#729991: syslog-ng-core uninstallable Gergely Nagy Bug#729991: syslog-ng-core uninstallable Martin Bagge / brother Bug#729991: syslog-ng-core uninstallable Gergely Nagy Bug#729991: marked as done (syslog-ng-core uninstallable) Debian Bug Tracking System Reply via email to
Bug#729991: syslog-ng-core uninstallable
> Bug#729991: syslog-ng-core uninstallable debian-bugs-rc -- Thread -- -- Date -- Bug#729991: syslog-ng-core uninstallable Martin Bagge / brother Processed: Re: Bug#729991: syslog-ng-core uninstallable Debian Bug Tracking System Bug#729991: syslog-ng-core uninstallable Andrei POPESCU Bug#729991: syslog-ng-core uninstallable Gergely Nagy Bug#729991: syslog-ng-core uninstallable Martin Bagge / brother Bug#729991: syslog-ng-core uninstallable Gergely Nagy Reply via email to Bug#729991: syslog-ng-core uninstallable Martin Bagge / brother Processed: Re: Bug#729991: syslog-ng-core uninstallable Debian Bug Tracking System Bug#729991: syslog-ng-core uninstallable Andrei POPESCU Bug#729991: syslog-ng-core uninstallable Gergely Nagy Bug#729991: syslog-ng-core uninstallable Martin Bagge / brother Bug#729991: syslog-ng-core uninstallable Gergely Nagy Bug#729991: marked as done (syslog-ng-core uninstallable) Debian Bug Tracking System Reply via email to
Bug#729991: syslog-ng-core uninstallable
> Bug#729991: syslog-ng-core uninstallable debian-bugs-rc -- Thread -- -- Date -- Bug#729991: syslog-ng-core uninstallable Martin Bagge / brother Processed: Re: Bug#729991: syslog-ng-core uninstallable Debian Bug Tracking System Bug#729991: syslog-ng-core uninstallable Andrei POPESCU Bug#729991: syslog-ng-core uninstallable Gergely Nagy Bug#729991: syslog-ng-core uninstallable Martin Bagge / brother Bug#729991: syslog-ng-core uninstallable Gergely Nagy Reply via email to Bug#729991: syslog-ng-core uninstallable Martin Bagge / brother Processed: Re: Bug#729991: syslog-ng-core uninstallable Debian Bug Tracking System Bug#729991: syslog-ng-core uninstallable Andrei POPESCU Bug#729991: syslog-ng-core uninstallable Gergely Nagy Bug#729991: syslog-ng-core uninstallable Martin Bagge / brother Bug#729991: syslog-ng-core uninstallable Gergely Nagy Reply via email to Bug#729991: syslog-ng-core uninstallable Martin Bagge / brother Processed: Re: Bug#729991: syslog-ng-core uninstallable Debian Bug Tracking System Bug#729991: syslog-ng-core uninstallable Andrei POPESCU Bug#729991: syslog-ng-core uninstallable Gergely Nagy Bug#729991: syslog-ng-core uninstallable Martin Bagge / brother Bug#729991: syslog-ng-core uninstallable Gergely Nagy Bug#729991: marked as done (syslog-ng-core uninstallable) Debian Bug Tracking System Reply via email to
