Need help getting started with SSH

[leyvi]

I'm trying to set up an SSH server on my PC, so that I can access it securely from school computers for remote development.
Unfortunately, when trying to connect locally, this happens:

[grknight]

Does the key using to connect exist in /home/leyvi/.ssh/authorized_keys? This is what the server uses to say "yup, this can continue"

[leyvi]

I don't know if this answers your question, but here you go:
I recently made a new ed25519 key-pair, named "my_machine". I ran the following command:

[szatox]

So.... The problem is that your client doesn't offer the key you want to use, do I get it right?

Check permissions on the keyfile. Private key must only be readable by you and nobody else.
Well, it is also possible that you have too many keys. You can try a bunch before ssh gives up, but you do already have a bunch of keys at hand, so maybe you've just hit the cap and your intended key wasn't checked because it was at the end of the queue. You can try that by explicitly telling ssh to use a particular key. Try running ssh with -i <path/to/privkey>
_________________
Make Computing Fun Again

[leyvi]

I think the file permissions are OK:

[pingtoo]

[leyvi]

[pingtoo]

[leyvi]

Ah, alright. I'll give it a try, and let you know how it goes...

[leyvi]

[pingtoo]

Did you see

[grknight]

You have to look at the sshd log to know why it is denying. Asking ssh, the client, won't know why the server is saying no.

[leyvi]

Quick update:
The problem is not fixed, however it did turn out that the permissions on both my ~/.ssh folder and my ~ folder were set incorrectly. I only found out now, because I thought `sshd` logged to syslog, I didn't realize it logged to auth.log. Here is the problem, according to the logs, with some (possibly) sensitive information redacted with "...":

[pingtoo]

may be you could share info after permission fixed, what other error(s) you got.

Your log still contain permission issue if they are after "permission fix"

[leyvi]

To clarify:
The last log I shared contains stuff from both before and after the changes I made to the directory permissions; pay very close attention and you'll see what I mean. When I get home, I'll make a list of line numbers for different stages.

[pingtoo]

[leyvi]

See lines 26 and 30.

[Hu]

It appears to be refusing your key. Check that the ed25519 key you are trying to use is listed in authorized_keys.

[pingtoo]

[leyvi]

Yeah, pretty much. Sorry I wasn't clear about it, I wrote some of those posts from my phone, and I had both limited information and time. Here's the output of history:

[leyvi]

Return value of `ssh-keygen -y -f my_machine | diff - my_machine.pub` was 0, by the way (no difference, I think).

[pingtoo]

Thanks for the information.

Looks alright from the command history. But I am not able to correlate those commands to the execution environment.

So I will suggest few steps and please try them when you are in front of your computer. This way hopefully it will show a clear pictures of execution environment so we don't need to go back and forth.

Assume you can have two terminal sessions,

In session A do

[leyvi]

Alright, thanks. I gotta go to bed now (matriculation exam tomorrow), I'll try it when I get home, and post the results here.

[leyvi]

Alright:

[pingtoo]

no /tmp/ssh.log?

Did client successful connect?

I am not able to understand "shell" post, it seems to me you are able to login, And on the remote server you ran the namei -l command is my understand correct?

from the /tmp/sshd.log,

It show the key was accepted and pty allocated and shell started but later got signal 2 (SIGINT) so I think it is successfully working but a Ctrl-C or something else generate a SIGINT that interrupted the session.