Default SSH authorized_keys for Users of App instances

[dnutan (Marc)]

NethServer Version: ns8
Module/App: ns8-dokuwiki (but possibly other apps as well)

Forgive me if it’s something utterly basic and if I didn’t research it on docs.

From where the SSH authorized_keys of App Users comes from?
It is something done automatically when creating the user?
Is it used for something, like the agent?

The auth key references root@node.ns8.test which does not match the FQDN of node’s hostname (tested on ns8 rocky’s qcow2 image).

I think it is matching the default FQDN of the image although App was installed after setting a FQDN on first cluster+node setup, as requested by ns8 cluster-admin page.
From /etc/hosts:

Is this related to the hostname problem reported here? NS8 - how to set system hostname

[davidep (Davide Principi)]

@dnutan

From where the SSH authorized_keys of App Users comes from?
It is something done automatically when creating the user?

It comes from a skel directory for NS8 modules: /etc/nethserver/skel

@dnutan

Is it used for something, like the agent?

Yes, it was before RC2. We want to remove it as the runagent became the official command to enter the agent environment with an interactive shell, e.g.

runagent -m traefik1

However before removing them, there is a bug to fix for Debian: Bad PATH set by runagent in interactive shell on Debian · Issue #6888 · NethServer/dev · GitHub

@dnutan

Is this related to the hostname problem reported here? NS8 - how to set system hostname

I don’t know, since last year we added many changes: AFAIK the FQDN setup is now working.