Hi,
Something strange here: I got the openssh update, but upon checking the
md5sum I got:
theo:/home/theo $ md5sum openssh-2.3.0p1-0.i386.rpm
3219bf7853c2c27056ec502b5fd3345c openssh-2.3.0p1-0.i386.rpm
where the announcement says:
SuSE-6.4
ftp://ftp.suse.de/pub/suse/i386/update/6.4/sec1/openssh-2.3.0p1-0.i386.rpm
04c17b0eba99c798ae401fb9aafbc7e4
Doing the rpm --checksig it returns md5 ok.
What's going on?
Cheers,
Theo
--
Theo v. Werkhoven
Hi, Something strange here: I got the openssh update, but upon checking the md5sum I got: theo:/home/theo $ md5sum openssh-2.3.0p1-0.i386.rpm 3219bf7853c2c27056ec502b5fd3345c openssh-2.3.0p1-0.i386.rpm
where the announcement says: SuSE-6.4 ftp://ftp.suse.de/pub/suse/i386/update/6.4/sec1/openssh-2.3.0p1-0.i386.rpm 04c17b0eba99c798ae401fb9aafbc7e4
Doing the rpm --checksig it returns md5 ok.
What's going on?
Cheers, Theo
Hi Theo,
the openssh packages were buggy. A bit too buggy: the rcsshd symlink was
broken, and some of the features were either not present or not working.
Jiri, our package maintainer for the openssh package, made new packages
that were built and put on the ftp server before the weekend. We will
reissue the announcement by the beginning of the week.
The checksums that you mentioned were right. Unfortunately, the source
rpms aren't there yet. And what puzzles me is that the build-number is
still 0.
3219bf7853c2c27056ec502b5fd3345c 6.4/sec1/openssh-2.3.0p1-0.i386.rpm
ce12abcff3dec118ceabe62e6cd1e090 7.0/sec1/openssh-2.3.0p1-0.i386.rpm
You see, plenty to do for a weekend. :-]
Thanks,
Roman.
--
- -
| Roman Drahtmüller
On 3 Dec, Roman Drahtmueller wrote:
Hi, Something strange here: I got the openssh update, but upon checking the md5sum I got: theo:/home/theo $ md5sum openssh-2.3.0p1-0.i386.rpm 3219bf7853c2c27056ec502b5fd3345c openssh-2.3.0p1-0.i386.rpm
where the announcement says: SuSE-6.4 ftp://ftp.suse.de/pub/suse/i386/update/6.4/sec1/openssh-2.3.0p1-0.i386.rpm 04c17b0eba99c798ae401fb9aafbc7e4 [..]
The checksums that you mentioned were right. Unfortunately, the source rpms aren't there yet. And what puzzles me is that the build-number is still 0.
Ok Roman, thanks for clearing that.
You see, plenty to do for a weekend. :-]
It's much appreciated Roman.
Cheers,
Theo
--
Theo v. Werkhoven
"Theo v. Werkhoven" wrote:
Something strange here: I got the openssh update, but upon checking the md5sum I got: theo:/home/theo $ md5sum openssh-2.3.0p1-0.i386.rpm 3219bf7853c2c27056ec502b5fd3345c openssh-2.3.0p1-0.i386.rpm
The checksums that you mentioned were right. Unfortunately, the source
I used this package today to update openssh on my SuSE 6.4. After doing that, the DISPLAY variable is not set anymore when I do slogin to some other host. Before (and I tested with reinstalling the old openssh), DISPLAY was set to sth. like "<host>:10.0". Now it's just unset... Yes, I did restart sshd after the update. Anyone else got this problem and maybe a hint what to do? Best regards, Frank -- Dipl.-Inform. Frank Steiner mailto:fst@informatik.uni-kiel.de Lehrstuhl f. Programmiersprachen mailto:fsteiner@web.de CAU Kiel, Olshausenstraße 40 Phone: +49 431 880-7265, Fax: -7613 D-24098 Kiel, Germany http://www.informatik.uni-kiel.de/~fst/
I used this package today to update openssh on my SuSE 6.4. After doing that, the DISPLAY variable is not set anymore when I do slogin to some other host. Before (and I tested with reinstalling the old openssh), DISPLAY was set to sth. like "<host>:10.0". Now it's just unset... Yes, I did restart sshd after the update.
The default configuration of the ssh client has been changed to not forward X11-connections any more. Change it in /etc/ssh/ssh_config or with the commandline option.
Anyone else got this problem and maybe a hint what to do?
Best regards, Frank
Thanks,
Roman.
--
- -
| Roman Drahtmüller
participants (3)
-
Frank Steiner
-
Roman Drahtmueller
-
Theo v. Werkhoven