[colug-432] Creating SSH for New User

[Steve VanSlyck]

Yes sir, root is able to login securely with no problem

On May 10, 2015 10:54:56 PM EDT, Chris Embree <cembree at ez-as.net> wrote:
>Kinda figured you did.  Beyond permissions, ownership and PuTTY keys.
>Is sshd.conf set to allow keys?
>
>Oh look, the last straw was grasped.
>
>On 5/10/15, Steve VanSlyck <s.vanslyck at postpro.net> wrote:
>> Yes that is a good point, & I am aware of the differences between the
>putty
>> public key and the way it needs to be on the server.
>>
>> On May 10, 2015 10:43:38 PM EDT, Chris Embree <cembree at ez-as.net>
>wrote:
>>>It's been a while, but I think PuTTY uses different keys than
>>>ssh-keygen style.  You probably have to run them thru PuTTY's keytool
>>>thing.
>>>
>>>
>>>On 5/10/15, Steve VanSlyck <s.vanslyck at postpro.net> wrote:
>>>> I create the keys in putty.
>>>>
>>>> On May 10, 2015 10:34:39 PM EDT, Zach Villers
><zachvatwork at gmail.com>
>>>> wrote:
>>>>>On the remote box, I would su - new user, ssh-keygen -t dsa (or
>rsa),
>>>>>ssh
>>>>>copy-id me at myhomebox. I think you are using root's key instead of
>the
>>>>>new
>>>>>users' key?
>>>>>
>>>>>On Sun, May 10, 2015 at 10:26 PM, Steve VanSlyck
>>>>><s.vanslyck at postpro.net>
>>>>>wrote:
>>>>>
>>>>>>  My new user (me) can't log on via SSH. Can someone look this
>over
>>>>>and
>>>>>> tell me what super basic thing I've done wrong?
>>>>>>
>>>>>> What I did:
>>>>>>
>>>>>> *As root*:
>>>>>>
>>>>>> Add user "name"
>>>>>>      /usr/sbin/adduser name
>>>>>> Create password
>>>>>>      passwd name
>>>>>>           [created the password]
>>>>>> Give root permissions
>>>>>>      sudo nano /etc/sudoers
>>>>>>           [added the line name ALL=(All) ALL
>>>>>> Re-enabled password authentication in sshd_config and restarted
>>>sshd
>>>>>>
>>>>>> *As the new user "name"*:
>>>>>>
>>>>>> made directory
>>>>>>      mkdir ./ssh
>>>>>> created file and added public key to file authorized keys
>>>>>>      sudo nano ~/.ssh/authorized_keys
>>>>>>           [entered the public key (which I call a "lock")]
>>>>>> updated permissions "just in case"
>>>>>>      chmod 700 ~/.ssh
>>>>>>      chmod 600 ~/.ssh/authorized_keys
>>>>>>
>>>>>> tried to login with the private key
>>>>>>      Result: server refused the key.
>>>>>>
>>>>>> Any idea what I'm doing wrong?
>>>>>>
>>>>>> _______________________________________________
>>>>>> colug-432 mailing list
>>>>>> colug-432 at colug.net
>>>>>> http://lists.colug.net/mailman/listinfo/colug-432
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>------------------------------------------------------------------------
>>>>>
>>>>>_______________________________________________
>>>>>colug-432 mailing list
>>>>>colug-432 at colug.net
>>>>>http://lists.colug.net/mailman/listinfo/colug-432
>>>>
>>>_______________________________________________
>>>colug-432 mailing list
>>>colug-432 at colug.net
>>>http://lists.colug.net/mailman/listinfo/colug-432
>>
>_______________________________________________
>colug-432 mailing list
>colug-432 at colug.net
>http://lists.colug.net/mailman/listinfo/colug-432
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.colug.net/pipermail/colug-432/attachments/20150510/59dcd275/attachment.html