mdz at ubuntu.com
Wed Mar 8 19:18:37 UTC 2006
On Mon, Mar 06, 2006 at 08:51:33PM +0100, Oliver Grawert wrote:
> Am Montag, den 06.03.2006, 11:36 -0800 schrieb Matt Zimmerman:
> > What changes when you run ltsp-update-sshkeys the second time, relative to
> > the first run?
> he wont see the first run easily, its done in the installer :)
The purpose of ltsp-update-sshkeys is to write out a configuration file.
That configuration file isn't changed by anything later in the install.
I am asking for the differences in that file before and after he fixes it by
re-running ltsp-update-sshkeys, so that I can see what was wrong in the
> there is something wring with the preseeded late_command (either sshd
> isnt up and there are no keys yet or its simply not executed ... i hope
> to have found the issue before flight 5, i suspect it has to do with the
> changed order of installing and rebooting we have without base-config in
> the installer now)
If the file is empty, then the most likely cause is that sshd is no longer
running when late_command is executed, due to the architectural changes in
the installer. ssh-keyscan exits successfully and outputs nothing if it is
unable to contact sshd.
This is easy to fix, at a small cost of some additional logic, by changing
ltsp-update-sshkeys to avoid using ssh-keyscan and get the keys directly
from the filesystem.
More information about the edubuntu-devel