Replies: 1 comment
-
I haven't been able to duplicate the issue in my testbed so there isn't an issue with zfsbootmenu. Something must have gone awry with the installation I experienced the issue on. A reinstall should resolve it, but since I found a workaround to use an existing key then I have no reason to reinstall just yet. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've had a problem with the remote access feature. I don't know if the issue is caused by zfsbootmenu.
I added a new key to my user's authorized_keys file. I confirmed the new key works by logging in to my server remotely without issue. I ran "sudo generate-zbm --debug" to update the initramfs, which completed successfully. I confirmed the content of the authorized_keys file in the initramfs using lsinitrd. The new key was there.
Unfortunately I can't login to dropbear when I reboot and attempt to login remotely using the new key. I get a publickey error. I logged in remotely using another key successfully to dropbear. I then checked the content of the authorized_keys in the initramfs of the live running instance (/root/.ssh/authorized_keys). The new key wasn't there. I'm not sure how that can be.
I've run generate-zbm twice to make sure the backup img file also has the new key in case rEFInd was starting using the backup for some reason.
Does anyone have any ideas of troubleshooting I can do?
Beta Was this translation helpful? Give feedback.
All reactions