Date: Sat, 14 Sep 2019 09:24:22 -0400 From: Aryeh Friedman <aryeh.friedman@gmail.com> To: MJ <mafsys1234@gmail.com> Cc: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: OT: My ssh authorized_keys doesn't work with nfs/nis Message-ID: <CAGBxaXmhLmFMFt9tj%2B8fbybi-XNujQjui1xjMnS53eFX_GRZYA@mail.gmail.com> In-Reply-To: <99038e82-9643-cbe8-63d7-e3a04ada43b5@gmail.com> References: <CAGBxaXkVQNE6deyWs9JXh9vqmKz8tLc9HfqC8ZmBLrK2jv7p3A@mail.gmail.com> <99038e82-9643-cbe8-63d7-e3a04ada43b5@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Problem solved it turned out to be really simple the home dir was 777 when the widest ssh wants it is 755 (all the permissions I where look at before where the .ssh dir not the home dir) On Sat, Sep 14, 2019 at 9:22 AM MJ <mafsys1234@gmail.com> wrote: > > > On 14/09/2019 5:39 pm, Aryeh Friedman wrote: > > My ~/.ssh/authorized_keys files works fine on a machine that is not in my > > NIS domain but when I copy my id_rsa.pub (which is what I did to create > the > > non-NIS authorized_keys) to my NIS account and give it the same > permissions > > as the working machine it insists on asking for a password. > > > > ssh faraway (non-NIS machine) > > does not ask for a password > > but > > ssh nearby (NIS machine) does > > > > Both have identical authorized keys and both (and their parent dirs) are > > set to 644. Both machines are FreeBSD 11 and the machine doing the ssh > > call is FreeBSD 12 > > > > Well in desperation I guess you could: > > Nuke the dud server's authorized_keys > Use "ssh-copy-id -i /your/path/to/key aryeh@nearby" to copy your pub key > to the dud server. > Test with "ssh -i /your/path/to/key -vv aryeh@nearby" > > Cheers > Mark. > -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGBxaXmhLmFMFt9tj%2B8fbybi-XNujQjui1xjMnS53eFX_GRZYA>