diff options
| author | Giteabot <teabot@gitea.io> | 2023-07-06 11:02:56 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-07-06 11:02:56 -0400 |
| commit | 09668b2e2ebc5c5b0df92336d764ef878f8b65aa (patch) | |
| tree | 7f744c6292065f6cbe2e73c09d13d838d358628c /MAINTAINERS | |
| parent | 04eea29ecbfed76ae693dab441adf5415b2e2f64 (diff) | |
| download | gitea-09668b2e2ebc5c5b0df92336d764ef878f8b65aa.tar.gz gitea-09668b2e2ebc5c5b0df92336d764ef878f8b65aa.zip | |
Correct permissions for `.ssh` and `authorized_keys` (#25721) (#25730)
Backport #25721 by @wolfogre
Set the correct permissions on the .ssh directory and authorized_keys
file, or sshd will refuse to use them and lead to clone/push/pull
failures.
It could happen when users have copied their data to a new volume and
changed the file permission by accident, and it would be very hard to
troubleshoot unless users know how to check the logs of sshd which is
started by s6.
Co-authored-by: Jason Song <i@wolfogre.com>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions