ssh host key fingerprint no longer available in the console log
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ec2-init (Ubuntu) |
Invalid
|
High
|
Scott Moser | ||
Karmic |
Invalid
|
High
|
Scott Moser | ||
linux-ec2 (Ubuntu) |
Fix Released
|
High
|
Tim Gardner | ||
Karmic |
Fix Released
|
High
|
Tim Gardner |
Bug Description
Binary package hint: ec2-init
When booting an instance the generated public key for sshd used to be printed
in the console so that one could verify the public key upon the first
connection.
After more than 20 minutes of uptime the console log ends with:
[ 1.847386] kjournald starting. Commit interval 5 seconds
[ 1.847406] EXT3-fs: mounted filesystem with writeback data mode.
[ 3.043120]
[ 3.043132] *******
[ 3.043138] *******
[ 3.043143] ** WARNING: Currently emulating unsupported memory accesses **
[ 3.043147] ** in /lib/tls glibc libraries. The emulation is **
[ 3.043152] ** slow. To ensure full performance you should **
[ 3.043156] ** install a 'xen-friendly' (nosegneg) version of **
[ 3.043161] ** the library, or disable tls support by executing **
[ 3.043165] ** the following as root: **
[ 3.043170] ** mv /lib/tls /lib/tls.disabled **
[ 3.043174] ** Offending process: dbus-uuidgen (pid=1119) **
[ 3.043179] *******
[ 3.043184] *******
[ 3.043188]
ProblemType: Bug
Architecture: i386
Date: Thu Sep 17 00:52:01 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelMo
Package: ec2-init 0.4.999-0ubuntu1
PackageArchitec
ProcEnviron:
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: ec2-init
Uname: Linux 2.6.31-300-ec2 i686
Changed in ec2-init (Ubuntu): | |
assignee: | nobody → Scott Moser (smoser) |
milestone: | none → ubuntu-9.10-beta |
Changed in linux-ec2 (Ubuntu Karmic): | |
importance: | Undecided → High |
Changed in linux-ec2 (Ubuntu Karmic): | |
assignee: | nobody → Tim Gardner (timg-tpi) |
status: | New → Fix Committed |
tags: | added: iso-testing |
Going through the /var/log/syslog file, the fingerprint is printed there. However there is a line related to rsyslog just after the line printed in the console:
rsyslogd-2039: Could no open output file '/dev/xconsole' [try http:// www.rsyslog. com/e/2039 ]