Re: SSH madness

wrote:

On the target machine:

- .ssh should be 700
- authorized_keys should 600


On Wed, Aug 16, 2017 at 4:12 PM, Scott Klement <
midrange-l@xxxxxxxxxxxxxxxx> wrote:

Not much information here. About all you've told us is "it doesn't work"
and "from a Mac". But, I use a key generated on my Mac all day long and
can log in via SSH without any problems.

Is it possible that you generated the wrong type of key?

Or that the authorities are wrong?



On 8/16/2017 4:59 PM, Matt Lavinder wrote:

We are trying to give a new employee access to the PASE/Bash command
shell
via Terminal. I have added his Mac’s RSA key to the authorized_keys file,
but it still will not let them connect. It will let them connect with a
password, but that is not what we want.

For the life of me, I cannot figure out what is different between the way
they are configured and I am. This all works for me when using my key
and
my profile. If I add my Mac's key to their authorized_keys file, it will
not let me connect either (yes, I used their user name).

I have a lot more system authorities than the new employee does, but I
can’t imagine why that would be the issue.

Is there a specific authority a user needs to be able to communicate with
the SSHD?

Does anyone have any other ideas?

--

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021

NON-DISCLOSURE NOTICE: This communication including any and all
attachments is for the intended recipient(s) only and may contain
confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further
distribution or use of this communication is prohibited. If you received
this communication in error, please contact the sender and delete/destroy
all copies of this communication immediately.