root@pve's password in Welcome-Screen

[andremueller27]

Hello everyone,

when I start updates, I’m asked for the root password after each LXC container:
root@pve's password – why does this prompt appear and how can I disable it?

Example:

--- APT CLEANING ---
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists...
Building dependency tree...
Reading state information...
Del dpkg 1.22.6ubuntu6.1 [1,283 kB]
Del dpkg 1.22.6ubuntu6.2 [1,281 kB]

--- Skip Extra Updates because of Headless Mode or user settings ---

--- Check Status for Welcome-Screen ---
root@pve's password:

Thanks for your help!

Best regards!

[BassT23]

The "problematic" code part for you is here:

ssh -q -p "$SSH_PORT" "$HOSTNAME" "\"$LOCAL_FILES/check-updates.sh\" -u ccontainer" | tee -a $LOCAL_FILES/check-output

maybe you change your hostname after installation, and now, you node don't know himself.

To fix this pls make an on the node, you run the updater:

ssh $HOSTNAME

then you will be asked if you want to add the host to "known hosts". Accept this, and the problem should be gone ;)

[BassT23]

I found a better solution.
Pls tryout latest development version with update develop -up and give feedback.
there it should be fixed ;)

[andremueller27]

Thank you very much for the quick reply! I tried it as described – result is in the screenshot.

[BassT23]

:'(
if you want you can go back to master with update -up

[BassT23]

ok, it seens you will become a problem with the updates, because, my first idea is the problem.

What come up, if you make an

ssh $HOSTNAME

[andremueller27]

I already tried it – here’s the result:

root@pve:~# ssh $HOSTNAME
root@pve's password:
Permission denied, please try again.
root@pve's password:
Permission denied, please try again.
root@pve's password:

[BassT23]

pls tryout this:

ssh-keygen -t rsa -b 4096 -f ~/.ssh/id_rsa -N ""
ssh-copy-id -i ~/.ssh/id_rsa.pub -p 22 root@$HOSTNAME

after this, ssh $HOSTNAME should not ask for password

Ist ok, because you are loged in as root an switch to root user. So no problematic code and no security risks ;)

[andremueller27]

Oh damn, it’s still not working… Thanks again for all the tips! Here’s the output:

root@pve:~# ssh-keygen -t rsa -b 4096 -f ~/.ssh/id_rsa -N ""
ssh-copy-id -i ~/.ssh/id_rsa.pub -p 22 root@$HOSTNAME
Generating public/private rsa key pair.
/root/.ssh/id_rsa already exists.
Overwrite (y/n)? y
Your identification has been saved in /root/.ssh/id_rsa
Your public key has been saved in /root/.ssh/id_rsa.pub
The key fingerprint is:
SHA256:NmflZk7y0I1H6jvvjugrK7URZ9fML9p2ATippTxxxx root@pve
The key's randomart image is:
+---[RSA 4096]----+
| |
| |
| + ++. |
| E o.+oO.+ |
| . S+@.X +. |
| +o X ....|
| ..o +o ..|
| . o .ooo .|
| ..++.o*+. |
+----[SHA256]-----+
/usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/id_rsa.pub"
/usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
/usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys
root@pve's password:
Permission denied, please try again.
root@pve's password:
Permission denied, please try again.
root@pve's password:

[BassT23]

Damn
What you change in your installation? 😀
Pls check /etc/ssh/sshd_config
This should be in and not comment out:

PubkeyAuthentication yes
AuthorizedKeysFile     .ssh/authorized_keys
PermitRootLogin yes

[andremueller27]

The lines
PubkeyAuthentication yes
AuthorizedKeysFile .ssh/authorized_keys

in my case had been commented out. I uncommented them, and now everything works again! Thank you for the fast and effective help!

By the way: after making the change I tried ssh $HOSTNAME again, and I get the same response:

root@pve:# nano /etc/ssh/sshd_config
root@pve:#
root@pve:#
root@pve:# sudo systemctl restart ssh
root@pve:~# ssh $HOSTNAME
root@pve's password: Permission denied, please try again.
root@pve's password:

I wish you a nice weekend and stay just the way you are!
Best regards
Andre

[BassT23]

Nice to hear ;)
After changing the ssh config, you need to restart the service, to make it workable.
You can restart it with
systemctl reload ssh or systemctl restart ssh or systemctl restart sshd