Hi, On Fri Jul 18, 2008 at 07:45:32 +0200, Frans Pop wrote: > reassign 491263 debian-installer 20070308etch2 > thanks > > On Friday 18 July 2008, Mike Edwards wrote: > > A few issues relating to network-console on etch netinst 4.0r3: > > > > * Keys generated by network-console are found on the blacklist included > > with newer versions of openssh-server. > > > > * If network-console is used for a new installation, openssh-server is > > installed on the new system, but .broken keys are left lying around in > > /etc/ssh. > > > > * Likewise to above, the rsa host key (/etc/ssh/ssh_host_rsa_key.pub) > > is found to be on the blacklist, and appears that it may be the same > > rsa key used during installation via network-console. > > That is correct. Thanks for alerting us to the issue. > > For most architectures c.q. installation methods this will be fixed > automatically with the next point release (coming very soon) as the fixed > version of openssh will be included on the CD images. > > What (I personally at least) had not realized yet is that that still > leaves a few cases where network-console is included in the D-I initrds. > This affects in particular s390, arm (iop32x/ixp4xx) and mipsel (cobalt). > > Stable Release team: > Have fixed versions of openssh/openssl already been accepted into p-u?
[EMAIL PROTECTED]:~% dak ls -S -sstable,proposed-updates openssh openssl openssh-client | 1:4.3p2-9 | stable | alpha, amd64, arm, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc openssh-client | 1:4.3p2-9etch2 | proposed-updates | alpha, amd64, arm, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc openssh-client-udeb | 1:4.3p2-9 | stable | alpha, amd64, arm, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc openssh-client-udeb | 1:4.3p2-9etch2 | proposed-updates | alpha, amd64, arm, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc openssh-server | 1:4.3p2-9 | stable | alpha, amd64, arm, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc openssh-server | 1:4.3p2-9etch2 | proposed-updates | alpha, amd64, arm, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc openssh-server-udeb | 1:4.3p2-9 | stable | alpha, amd64, arm, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc openssh-server-udeb | 1:4.3p2-9etch2 | proposed-updates | alpha, amd64, arm, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc ssh | 1:4.3p2-9 | stable | all ssh | 1:4.3p2-9etch2 | proposed-updates | all ssh-askpass-gnome | 1:4.3p2-9 | stable | alpha, amd64, arm, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc ssh-askpass-gnome | 1:4.3p2-9etch2 | proposed-updates | alpha, amd64, arm, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc ssh-krb5 | 1:4.3p2-9 | stable | all ssh-krb5 | 1:4.3p2-9etch2 | proposed-updates | all openssh | 1:4.3p2-9 | stable | source openssh | 1:4.3p2-9etch2 | proposed-updates | source libcrypto0.9.8-udeb | 0.9.8c-4etch1 | stable | alpha, amd64, arm, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc libcrypto0.9.8-udeb | 0.9.8c-4etch3 | proposed-updates | alpha, amd64, arm, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc libssl-dev | 0.9.8c-4etch1 | stable | alpha, amd64, arm, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc libssl-dev | 0.9.8c-4etch3 | proposed-updates | alpha, amd64, arm, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc libssl0.9.8 | 0.9.8c-4etch1 | stable | alpha, amd64, arm, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc libssl0.9.8 | 0.9.8c-4etch3 | proposed-updates | alpha, amd64, arm, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc libssl0.9.8-dbg | 0.9.8c-4etch1 | stable | alpha, amd64, arm, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc libssl0.9.8-dbg | 0.9.8c-4etch3 | proposed-updates | alpha, amd64, arm, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc openssl | 0.9.8c-4etch1 | stable | source, alpha, amd64, arm, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc openssl | 0.9.8c-4etch3 | proposed-updates | source, alpha, amd64, arm, hppa, i386, ia64, mips, mipsel, powerpc, s390, sparc > If they have and given the above I propose to do a new upload of > debian-installer to be included in 4.0r4. If all goes well, they should > be built with time to spare for the planned schedule but we would need > quick responses if there are issues. > > Any objections against an upload? There would be no other changes. go ahead. if you need any assistance, don't hesitate to contact me (see IRC) Greetings Martin -- Martin Zobel-Helas <[EMAIL PROTECTED]> | Debian Release Team Member Debian & GNU/Linux Developer | Debian Listmaster Public key http://zobel.ftbfs.de/5d64f870.asc - KeyID: 5D64 F870 GPG Fingerprint: 5DB3 1301 375A A50F 07E7 302F 493E FB8E 5D64 F870 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]