大网数据广告活动
服务器运维问答

OpenSSH: allow users with writeable HOME to use public key authentication

· 52CE 我爱测

On a local workstation I need to have a handful of users to be able to freely write in each other $HOME. I KNOW this is a security breach and, in the specific situation, I do not care at all. I have another server (not local to L…

问题原文

原帖链接 · ZioByte · CC BY-SA 4.0

On a local workstation I need to have a handful of users to be able to freely write in each other $HOME.

I KNOW this is a security breach and, in the specific situation, I do not care at all.

I have another server (not local to LAN) used mainly as SCM repo. The above mentioned users access server via ssh.

Unfortunately OpenSSH server does not like writable $HOMEs and I found no way to circumvent it (I expected to have some server-side param).

Can someone suggest a workaround?

已采纳解答

原帖链接 · noitsbecky · CC BY-SA 3.0

My suggestion for a workaround: Put the authorized_keys file somewhere outside of the user's home directory, using the AuthorizedKeysFile directive in sshd's config file.

However, I'm a bit puzzled - the StrictModes directive should specifically do what you want. Does this not work as documented?

StrictModes

Specifies whether sshd should check file modes and ownership of the user's files and home directory before accepting login. This is normally desirable because novices sometimes accidentally leave their directory or files world-writable. The default is "yes".

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2015-07-03)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 4.0 / CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。