[mythtv-users] Is there interest for a couple very short HOWTO's?

[Joseph A. Caputo]

Jeff wrote:
> Friday, March 26, 2004, 1:00:31 PM, Joseph A. Caputo wrote:
> 
> 
>>On Friday 26 March 2004 12:39, Jeff wrote:
>>
>>>Friday, March 26, 2004, 11:57:41 AM, Joseph A. Caputo wrote:
>>>
>>>>On Friday 26 March 2004 11:14, Jeff wrote:
>>>>
>>>>>The one tricky part which I can't remember the command for is
>>>>>after you generate your key pair on the client (eg. puTTYgen)
>>>>>you copy the public key to the server. There is a ssh command that
>>>>>reads the public key file and generates a .ssh/authorized_keys
>>>>>entry. You don't just paste the public key into this file.
>>>>
>>>>Sure you can:
>>>>
>>>>	cat public_key_file >> authorized_keys
>>>>
>>>>works fine.
>>>>
>>>>-JAC
>>>
>>>Perhaps for you. If I look at my public key and the
>>>contents of the authorized_keys file, they are in slightly
>>>different formats.
> 
> 
> 
>>Hmmm, shouldn't be, unless you're digitally signing your keys with a
>>certificate.  Every resource I've seen on SSH (man pages, howtos, etc)
>>just says "add your public key to the authorized_keys file".  No 
>>mention of needing any special utility to do it.  Are you using a 
>>vanilla OpenSSH ?
> 
> 
>>Of course, I've never generated a key with PuTTYgen before; maybe the
>>keys it produces require tweaking?
> 
> 
>>-Joe
> 
> 
> puTTY, and other generators, make keys in "SECSH Public Key File
> Format". This looks something like:
> ---- BEGIN SSH2 PUBLIC KEY ----
> Subject: <name>
> Comment: <text>
> <key bytes>
> ---- END SSH2 PUBLIC KEY ----
> 
> If you copy this to your SSH server into the /home/<user>/.ssh
> directory of the user it belongs to and use:
>     ssh-keygen -i -f <filename> >> authorized_keys
> it will add this to the list of valid keys for that user.
> 
> You need to be root because root owns all of the authorized_keys
> files.
> 

Ah, that's it then -- I use ssh-keygen to generate my keys in the first 
place.  Now I understand why any time I've tried to use a key made with 
PuTTY it didn't work.

Oh, and on any OpenSSH implementation I've worked with, the 
${HOME}/.ssh/authorized_keys file is owned by the user, with 0600 
permissions.

-JAC