SOLVED public/private SSH key for FreeNAS user?

[nojohnny101]

Hello All,
my ultimate goal is to run an rysnc task from FreeNAS that pulls a directory from a remote raspberry pi through SSH. It seems I have to generate a public/private key for the FreeNAS user that will run the rsync task. Is that correct?

I just wanted to check because there doesn't seem to be a generated public/private key pair for FreeNAS users. I wanted to make sure I just was not looking in the wrong place before I generate them on FreeNAS in the appropriate user's .ssh folder.

Thanks.

 

[danb35]

there doesn't seem to be a generated public/private key pair for FreeNAS users

That's correct, generating an SSH keypair isn't part of building a new user.

 

[nojohnny101]

Thank you. Did I miss this explicitly in the manual? It talks a lot about external accounts connecting to FreeNAS but never mentions the reciprocal. If it isn't there, might be helpful to add a sentence or a short paragraph.

 

[wblock]

https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/openssh.html#security-ssh-keygen

I'm not sure if this should be documented in our user guide, but maybe a link.

 

[CPP-IT]

https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/openssh.html#security-ssh-keygen

I'm not sure if this should be documented in our user guide, but maybe a link.

Would the keys generated the above manner survive an upgrade/update? Whenever I SSH into the FreeNAS then `su` to root it tells me

Warning: settings changed through the CLI are not written to the configuration database and will be reset on reboot.

 

[danb35]

Would the keys generated the above manner survive an upgrade/update?

Yes. SSH keypairs are user data, not configuration settings.

 

[CPP-IT]

Yes. SSH keypairs are user data, not configuration settings.

I always draw up short when I see that message. Thanks for the reassurance.