ssh-rand-helper probs

[Frank Cusack]

> Hi all
> 
>     Am i doing this right? Is this the right list to post to? If not, a
> quick lesson in ettiquette for me would not hurt.  As I am both just
> starting to use newsgroups and SSH, I am not entirely familiar with the
> processes.

One comment: lose the html email.

> I
> am currently using the SSH packages for Solaris 2.8 available at
> sunfreeware.com.  The environment is Solaris 8 (2.8) on sun4u platforms
> (ultras).  At work, I have constructed a boot and installation server, an

> The first time I tried this type of installation of SSH at home however I
> got an error that read:
> 
>  "ld.so.1: /a/usr/local/bin/ssh-keygen: fatal: libz.so: open failed: No
> such
> file or directory.  Killed"
> 
> So........just feed it some env parameters ....like LD_LIBRARY_PATH...
> right?    nope

No, because the shared lib paths are hardcoded in (generally a good thing).

> the relevant excerpt from the customization script that I uses is here:

Well, do you understand that the problem is your newly installed disk
is mounted on /a, not /?  I imagine so, from the looks of your script,
and your mention of seting LD_LIBRARY_PATH.

So before I give you the answer, :-) I would ask why you want to generate
the keys at install time?  I don't see a part in the script where you
squirrel the keys away someone on the install server, but you may have
not included that part.  If you are not saving the key (eg, to use for
known_hosts distribution) then the easiest thing is to just don't generate
the keys.  The rc.d startup script should generate the keys if they
don't exist.  If it doesn't, then you should complain to sunfreeware.com.

But to make it work without that, a good bet is to run the commands
under chroot:

    chroot /a /usr/bin/ssh-keygen ...
    chroot /a ...

An alternative might be to have the postinstall script do it

    chroot $PKG_INSTALL_ROOT /usr/bin/ssh-keygen ...
    ...

then you just copy the keys out after installing.

/fc