Re: keying a fresh sshd

chris rapier wrote:
> 
> 
> Carl Karsten wrote:
> 
> 
>>> Modify the install routine to use "make install-nokeys" instead of 
>>> "make install". This will prevent your box from generating new keys 
>>> and overwriting your olds one.
>>
>>
>> ah - install isn't install :)
>>
>> I am re-running the OS install each time - like booting from the CD 
>> and doing 'install to first HD, auto partition and mkfs hda1'
>>
>> So there are no "old keys" to overwrite.
> 
> Okay, when you said install I was thinking it was the aplication you 
> were installing. Okay, in this case you have no options other than 
> restoring an old /etc/ssh/ (assuming that is where you put it) over the 
> new one after the OS install is complete.
> 

cool.  This was my suspicion, but my first attempt failed so just getting 
confirmation that it is what I need to do is a big help.

I just copied the whole dir to another box.  I'll reinstall and diff the new dir 
to the old and post the results (not that anyone here asked for them, but may as 
well for posterity.)

>> um... this isn't Gentoo :) apt-get installs binaries.
> 
> It doesn't even give you the option of building from source? Thats kind 
> of stupid. I really don't use package managers much so I'm always 
> surprised by them.

There is always the option to do whatever you want, however and whenever. :) 
The trick is not trashing your box all to hell.

One thing that took me by surprise about Ubuntu: it does not install make and 
gcc by default.  there is the build-essential package that has all that, so it 
is easy to deal with.

On building from source in the package manager world:

easy way: grab source tarbal, ./configure && make && make install.
problem: now the package management config doesn't know about the new package, 
or where it is, so it is possible that a different version gets installed in a 
different place and then you get to untangle that mess.

medium: use the package managers apt-get source foo to get foo's source and the 
config files to build a package.  tweak the source (even replace with tarbal 
source) and build a package, then install the package.

hard way: starting from scratch, when no one has built a package for the app.  I 
have tried, and failed.  lucky for me it was just a matter of looking harder for 
someone elses work, and I could fall back to medium :)

Carl K

--
List Info:      http://erdelynet.com/ssh-l/
List Archives:  http://erdelynet.com/archive/ssh-l/
To Unsubscribe: Mail mailto:[email protected]