SSH Authentication Refused: Bad Ownership or Modes for Directory

最新推荐文章于 2023-11-03 17:14:48 发布
最新推荐文章于 2023-11-03 17:14:48 发布
阅读量422 收藏 1
点赞数 1
本文介绍了解决SSH认证失败的问题，通常由于目录权限设置不当导致。文章提供了具体的命令来调整用户的家目录、.ssh目录及authorized_keys文件的权限，确保SSH连接的安全与稳定。

转载SSH Authentication Refused: Bad Ownership or Modes for Directory


SSH doesn’t like it if your home or ~/.ssh directories have group write permissions. Your home directory should be writable only by you, ~/.ssh should be 700, and authorized_keys should be 600 :

1
2
3

> chmod g-w /home/your_user
> chmod 700 /home/your_user/.ssh
> chmod 600 /home/your_user/.ssh/authorized_keys

You can also get around this by adding StrictModes off to your ssh_config file, but I’d advise against it - fixing permissions is the way to go.

lxf2017
关注
ssh 登录时常出现的几种错误以及解决方法（Linux）
a746742897的博客
03-12 1万+
ssh 登录时常出现的几种错误以及解决方法（Linux） 参考网址：https://blog.youkuaiyun.com/GX_1_11_real/article/details/80423409 前言 ssh是Linux系统中常用的远程登陆的命令，有的时候我们通过xshell等远程连接软件使用ssh去登陆远程的服务器的时候，会遇到一些问题。 下面是关于ss...
linux密钥链接失败的原因,linux中ssh密钥登录失败问题解决办法
weixin_29980355的博客
05-12 8044
搞一个ssh的密钥登录，结果发现就是无法使用密钥登录，非让我输入密码。苦恼。输入ssh连接代码ssh -i private.key -v user@host.com -p22从连接的信息中看不出有什么问题。debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,passworddebug1:...
使用SSH遇到Authentication Refused: Bad Ownership or Modes for Directory
xwv
07-02 476
      在使用SSH进行git的远程仓库操作时,远端服务器提示要求输入密码.这与之前的使用情况并不 相同.检查了服务器的ssh的日志文件/var/log/secure后,注意到类似下面的信息:       Authentication refused: bad ownership or modes for directory /home/git/.ssh         想来应该是文...
Authentication refused: bad ownership or modes for directory /root
Do
04-10 1867
背景： Centos7 成功配置免密登录，其它主机没有问题，有一台主机配置的公钥没有问题，但是登录还是需要输入密码， 查看日志（/var/log/secure），报错：Apr 10 15:49:39 node32 sshd[30988]: Authentication refused: bad ownership or modes for directory /root 解决： 是文件权...
ssh私钥无法连接 Authentication refused: bad ownership or modes for directory /root/.ssh
weixin_43376075的博客
11-03 738
Authentication refused: bad ownership or modes for directory /root/.ssh
ssh无密码登陆 Authentication refused: bad ownership or modes for directory /root
weixin_34124939的博客
11-27 588
利用脚本自动建立ssh无密码登陆，系统版本为centos6.5 tailf /var/log/secure Mar 18 15:35:05 a2 sshd[6521]: Authentication refused: bad ownership or modes for directory /root Mar 18 15:35:05 a2 sshd[...
【linux】非root用户ssh免密登录失败，Authentication refused: bad ownership or modes for directory /home/XXX
Dawson的博客
09-02 2447
在使用非root用户，配置集群免密登录时，发现配置完了免密登录仍然需要输入密码。 查看了系统安全日志后，发现报错。 # 查看系统安全日志命令 sudo cat /var/log/secure | grep sshd # 看时间范围内的错误的日志信息 Sep 1 17:25:53 node001 sshd[47211]: Authentication refused: bad ownership or modes for directory /home/dawson 0 首先先要配置好免密登录，即最少满
解压zabbix导致使用ssh免密登陆时出现：Authentication refused: bad ownership or modes for directory /root
david3ddafsd的博客
06-30 557
使用ssh免密登陆时出现：Authentication refused: bad ownership or modes for directory /root.ssh目录权限不对/root目录权限问题 前提条件（请仔细阅读！） 需要登陆到问题机器操作，请仔细阅读 如果机器没有其他用户，当前有终端连着该机器，请不要断开！请不要断开！请不要断开！否则就再也连不上了。 如果当前机器有其他用户（可以正常登陆并切换到root），那就通过该用户登陆机器，修改root目录权限 .ssh目录权限不对 /root/.
centos配置ssh免密码登录后仍要输入密码的解决方法
09-15
在日志文件`/var/log/secure`中查找错误信息，比如“Authentication refused: bad ownership or modes for file”。 解决这个问题，你需要检查并调整`.ssh`目录及其文件的权限。确保它们只对所有者有写权限： ```...
测试 SSH 基础连接 # 使用相同参数测试连接 ssh -v -p [端口] -i ~/.ssh/id_rsa [用户名]@[服务器IP] 观察 debug1: Authentications that can continue 后的错误提示： debug1: load_hostkeys: fopen /Users/jolinjiang/.ssh/known_hosts: No such file or directory debug1: load_hostkeys: fopen /Users/jolinjiang/.ssh/known_hosts2: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory debug1: checking without port identifier debug1: load_hostkeys: fopen /Users/jolinjiang/.ssh/known_hosts: No such file or directory debug1: load_hostkeys: fopen /Users/jolinjiang/.ssh/known_hosts2: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory debug1: hostkeys_find_by_key_hostfile: hostkeys file /Users/jolinjiang/.ssh/known_hosts does not exist debug1: hostkeys_find_by_key_hostfile: hostkeys file /Users/jolinjiang/.ssh/known_hosts2 does not exist debug1: hostkeys_find_by_key_hostfile: hostkeys file /etc/ssh/ssh_known_hosts does not exist debug1: hostkeys_find_by_key_hostfile: hostkeys file /etc/ssh/ssh_known_hosts2 does not exist The authenticity of host '[fox-telemarket.starklotus.com]:36000 ([149.129.235.174]:36000)' can't be established. ED25519 key fingerprint is SHA256:/g3xmRHaPBpl4W5WUIcgHNyzPKjt5gCadvKC/8hlTZY. This key is not known by any other names. Are you sure you want to continue connecting (yes/no/[fingerprint])? yes Warning: Permanently added '[fox-telemarket.starklotus.com]:36000' (ED25519) to the list of known hosts. debug1: rekey out after 4294967296 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey in after 4294967296 blocks debug1: SSH2_MSG_EXT_INFO received debug1: kex_ext_info_client_parse: server-sig-algs=<rsa-sha2-256,rsa-sha2-512> debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic debug1: Next authentication method: publickey debug1: get_agent_identities: bound agent to hostkey debug1: get_agent_identities: agent returned 1 keys debug1: Will attempt key: /Users/jolinjiang/.ssh/id_rsa RSA SHA256:HnRtogpLB7+VvzDy1C4Z/8RX5duqmYaBju7QMAC70hA explicit agent debug1: Will attempt key: /Users/jolinjiang/.ssh/id_rsa RSA SHA256:HnRtogpLB7+VvzDy1C4Z/8RX5duqmYaBju7QMAC70hA explicit debug1: Offering public key: /Users/jolinjiang/.ssh/id_rsa RSA SHA256:HnRtogpLB7+VvzDy1C4Z/8RX5duqmYaBju7QMAC70hA explicit agent debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic debug1: Offering public key: /Users/jolinjiang/.ssh/id_rsa RSA SHA256:HnRtogpLB7+VvzDy1C4Z/8RX5duqmYaBju7QMAC70hA explicit debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic debug1: No more authentication methods to try. jolinjiang@fox-telemarket.starklotus.com: Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
最新发布
08-27
Authentication refused: bad ownership or modes for directory /home/user ``` --- ### **5. 服务端SSH配置检查** 编辑 `/etc/ssh/sshd_config`： ```ini PubkeyAuthentication yes # 启用公钥认证 ...
ssh 之 bad ownership or modes for directory
weixin_33845881的博客
05-25 784
使用key登录远程服务器时，一直登录不进去，查看secure日志出现下面的日志信息： May 25 13:57:23 zhao-file sshd[881]: [ID 800047 auth.info] Authentication refused: bad ownership or modes for directory /home/ckl 这里主要是...
ssh免密登录无法生效：authentication refused:bad ownership or modes for directory /home/hadoop
lukabruce的博客
11-29 2127
原因是： /home/hadoop权限问题 解决办法： chmod 700 /home/hadoop      (权限千万不能赋予777，否则免密登录是无法生效的，因为authorized_keys默认是自己唯一写权限的)    ...
ssh免密码登陆设置时Authentication refused: bad ownership or modes错误解决方法
weixin_45034355的博客
12-08 5198
问题： 设置ssh免密码登陆的时候，发现有一些机器设置不生效。有一些机器正常。 跟踪： tail /var/log/secure -n 20 错误日志如下： Dec 8 09:25:22 hdp-2 sshd[5678]: Authentication refused: bad ownership or modes for directory /root 翻译：拒绝认证:目录/根目...
ssh免密登入失败（Authentication refused: bad ownership or modes for directory）
words8的博客
04-27 3279
现象：配置完免密登入后，部分机器仍需要输入密码才能登入 通过命令 /var/log/secure查看日志 出现问题的机器 Apr 26 22:58:47 hadoop102 sshd[58994]: Authentication refused: bad ownership or modes for directory /home/evil/.ssh Apr 26 22:58:52 hadoop102 sshd[58994]: Accepted password for evil from 192.1
Troubleshoot：SSH身份验证被拒绝 Authentication refused: bad ownership or modes for ...
jelatine的博客
11-07 1700
SSH免密码登陆失败的处理
SSH公钥免密登录失败
weixin_44105292的博客
10-30 2225
并且文件权限是777，原因是当时是直接拷贝过来的，按如下步骤解决。文件后，发现在ssh客户端还是不能实现公钥免密登录。我的ssh服务端是ubuntu系统，配置完。目录如果权限和所属权有问题也不能正常登录。然后就可以正常实现公钥免密登录了。目录，查看ssh log文件。文件的所有者和用户组都不是。命令查看目录下文件权限。
No supported authentication methods available (server sent:publickey)
07-09
Authentication refused: bad ownership or modes for directory /home/user/.ssh ``` #### 6. **测试 SSH 配置连通性** - 使用 `-v` 参数运行 SSH 命令以启用详细输出，便于排查问题： ```bash ssh -v -i ~/....
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值