[GUIDE] Enable SSH with Public Key Authentication (Securing remote webUI access to OMV)

Zitat von subzero79

You can list the directory to find out what files are there

ls -la ~/.ssh

Depends if you defined different output names for the keys

I think your command is missing the home folder shortcut

[fubz.LOCA_MACHINE] ➤ ssh ssh-user-access@192.168.1.135 -i ~/.ssh/sshacess

I've marked in red

Alles anzeigen

I'm having a similar issue.. I followed the guide. I can login to my nas using 'sshremote' but I can't with 'sshacess'. I get an error: "Warning: Identity file /Users/RS/.ssh/sshacess not accessible: No such file or directory.
Permission denied (publickey)."

The output from ls -la ~/.ssh reveals that I do not have sshacess (attached image).

Should I have it?

Does this guide still apply in OMV 2 and OMV 3?

Also, I'd like to make a new sudo account to SSH into so I'm not logged in as root, where I can accidentally mess things up. Is there a preferred "OMV" way of doing this, or should I follow Debian guides?

I'm mainly wondering what groups the new sudo user should belong to.

Thanks!

Is this what you are looking for: Creating a new 'admin' user for SSH ?

Hey, I posted that and I did get an answer for that part of the question.

I'm still curious if this OMV 1.0 guide is still good for 2 and 3, or if they are significantly different.

Sorry but I didn´t take care who has posted that. I thought I fits quite good to the second part of your question.

I'm running OMV 5.5.3.

Adding public keys to users through OMV web interface doesn't seem to produce any effect.

If I manually add the public key to ~/.ssh/authorized_keys of a user it works as expected (no password asked on ssh login).

If I add the public key through OMV web interface it has no effect... Password is still asked on ssh login.

Am I missing something or is this feature broken?

Thanks,

Bruno

My guide for accessing from Windows workstation:

RE: Certificates: only tears

Zitat von tekkb

/var/lib/openmediavault/ssh/authorized_keys

a good tip, but not complete, this is complete solution to fix the "public authentication key issue"

add all your public keys to the file under the authorized_keys directory, the file usually named "username" that you use to login webUI of OMV7

for example I use "pi" as the login user id, the file for my OMV7 is named "pi", so appending your public keys to this file by any methods you knew