Siduction Forum
Siduction Forum => Upgrade Warnings => Topic started by: devil on 2013/12/23, 09:06:11
-
There is a broken new version of OpenSSL, that will prevent rebooting into your graphical environment.
Please wait until further notice.
greetz
devil
-
Unfortunately I did a DU 30 minutes ago on my Asus-Eee-PC and your warning came to late and so I cannot login anymore. I am very curious how this problem will be solved.
Greetings, merry christmas and a happy & healthy 2014 for the whole "siduction-community",
Jörg
-
Alas +1
-
Filed a bug report: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=%23732966
greetz
devil
-
Temporary fix for now: rebuild openssh, reboot, enjoy:
apt-get build-dep openssh
cd /tmp
apt-get source openssh
cd openssh*
debian/rules binary
dpkg -i ../*.deb
You probably need to remove the # in front of deb-src stanza in /etc/apt/sources.list/debian.list and apt-get update before building.
EDIT: There is a fix in our fixes repo, until the debian package arrives. No need to build by yourself.
greetz
devil
-
Temporary fix for now: rebuild openssh, reboot, enjoy:
apt-get build-dep openssh
cd /tmp
apt-get source openssh
cd openssh*
debian/rules binary
dpkg -i ../*.deb
You probably need to remove the # in front of deb-src stanza in /etc/apt/sources.list/debian.list and apt-get update before building.
greetz
devil
Danke. Hat alles einwandfrei funktioniert.
-
The issue is fixed in Debian and will be in the archive as openssh 1:6.4p1-1.1 with the next mirror sync.
greetz
devil
-
Problem solved after DU with 2 "repaired" openssh*-files (5 minutes ago!).
Greetings,
Jörg
-
There is a broken new version of OpenSSL, that will prevent rebooting into your graphical environment.
Please wait until further notice.
I know it's solved now, but was it openssh or openssl?
Here is no openssh
# apt-cache policy openssh
N: Paket openssh kann nicht gefunden werden.
it's ssh or ssh-server/client and openssl shows somewhat different version numbers:
# apt-cache policy openssl
openssl:
Installiert: 1.0.1e-4
Installationskandidat: 1.0.1e-5
Now I guess ssh is meant:
# apt-cache policy ssh
ssh:
Installiert: 1:6.4p1-1
Installationskandidat: 1:6.4p1-1.1
Versionstabelle:
But there still is a doubt whether or not the fixed package really is the one which was broken (i.e. there is nothing solved when openssl was broken and now ssh ist "fixed")
???
-
The bug was in openssh.
-
There is no openssh, but ssh and openssh-client, openssh-server! And the fixed version number corresponds to ssh and it's dependencies.
-
The fixed debian packages are in the repos, so everything is fine.
greetz
devil
-
I got hit with this last night, and thought that it might have something to do with console-common and keymap.sh, since I forgot to move keymap.sh before doing the dist-upgrade. I didn't have time to look at it further, and, I'm happy someone identified the problem correctly. The du tonight solved the problem.
Thanks