Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] 9.7_p1-r4-ls175 fails to start with WARNING: UNPROTECTED PRIVATE KEY FILE! #98

Open
1 task done
gchux opened this issue Nov 25, 2024 · 3 comments
Open
1 task done

Comments

@gchux
Copy link

gchux commented Nov 25, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

9.7_p1-r4-ls175 fails to start with WARNING: UNPROTECTED PRIVATE KEY FILE!

Expected Behavior

9.7_p1-r4-ls174 is OK

Steps To Reproduce

  1. create an image using lscr.io/linuxserver/openssh-server:9.7_p1-r4-ls175
  2. create a container using the created image
  3. it will fail with: WARNING: UNPROTECTED PRIVATE KEY FILE! Permissions 0640 for '/etc/ssh/ssh_host_ed25519_key' are too open.

Environment

- OS: Ubuntu 22.04
- How docker service was installed: using Docker's provided install script

CPU architecture

x86-64

Docker creation

docker buildx build -f Dockerfile -t ssh-server .

Container logs

ssh-keygen: generating new host keys: RSA ECDSA ED25519 
SSH host public key(s): ...
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@         WARNING: UNPROTECTED PRIVATE KEY FILE!          @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Permissions 0640 for '/etc/ssh/ssh_host_rsa_key' are too open.
Copy link

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

@v4ld3r5
Copy link

v4ld3r5 commented Nov 30, 2024

Hi, I'm having the same issue, had to login and chmod 0400. In my case it complains about Permissions 0777.

Linuxserver.io version:- 9.7_p1-r4-ls178

@LinuxServer-CI
Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Issues
Development

No branches or pull requests

3 participants