Access OMV from outside

Agricola · 10. Oktober 2020

Zitat von gderf

One thing that can be an 'invisible' factor is that if you use Windows Notepad and possibly other word processing programs on your key files, the CRLFs are not *nix compatible.

I generated the keys in Terminal on a Mac laptop and copy/pasted the public key directly from Terminal to the public keys tab of my user in the OMV GUI.

Zitat von gderf

I used the procedure here to generate a key on my Linux Mint machine and send the public key to my OMV machine. I didn't use any portion of OMV's WebGUI to do this. It was all done from the remote machine.

https://www.howtoforge.com/lin…all-ssh-keys-on-the-shell

I'll check it out.

gderf · 10. Oktober 2020

If OMV accepted the pasted key it should have worked, at least that portion of it.

I used this from the shell on the remote machine which doesn't involve any manipulation (copy, paste, etc.) of the key material:

ssh-copy-id username@omv-ip-address

It all works including tunneling.

Agricola · 11. Oktober 2020

gderf the guide you linked to makes no mention of converting the public key to RFC4716 format. Do you not need to?

Also does the public key file reside in /home/“user”/.ssh in OMV

gderf · 11. Oktober 2020

I typed exactly two commands. One generated the keys the other uploaded the public key to OMV. Apparently the public key was already in the correct format.

Code

ssh-keygen -o -b 4096 -t rsa

ssh-copy-id username@omv-ip-address

In OMV, the key is added to the file: /home/username/.ssh/authorized_keys as one long line.

That's all I had to do besides providing a passphrase during key generation.

Agricola · 11. Oktober 2020

I have been fighting this thing on and off all day. So it turns out that after this last failure I looked at my /home/user folder in OMV and found ownership was "root root." You can laugh or you can groan, but I have it running now.

One last thing. You do leave the port in the SSH tab at 22, don't you? It's just in the router that you forward internal port 22 to external port 12345 (or something else), right?

Thanks gderf for the help and patience. I can't believe that it is so easy. Just two lines of code!

Morlan · 11. Oktober 2020

Just for the record. When you enter the public keys through the web interface the keys are stored under /var/lib/openmediavault/ssh/authorized_keys/username

gderf · 11. Oktober 2020

Zitat von Agricola

One last thing. You do leave the port in the SSH tab at 22, don't you? It's just in the router that you forward internal port 22 to external port 12345 (or something else), right?

Yes, that is correct. Port 22 is not exposed to the internet.

Jetzt mitmachen!