Centos的SSH免密了，但是登录出现RSA1认证，还需要输入密码，解决办法如下

最新推荐文章于 2023-02-28 22:47:20 发布
最新推荐文章于 2023-02-28 22:47:20 发布
阅读量1.8k 收藏
点赞数 3
分类专栏： Linux 文章标签： ssh centos linux
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_44033210/article/details/122376834
版权
本文档描述了在CentOS上遇到SSH登录时需要输入密码，即使已经设置了RSA免密的情况。问题源于RSA1认证，解决方法是修改`/etc/ssh/sshd_config`文件，将`Protocol 1`改为`Protocol 2`，然后重启SSH服务。通过这个配置，可以消除RSA1认证错误并实现免密登录。
摘要由CSDN通过智能技术生成

Centos的SSH免密了，但是登录出现RSA1认证，还需要输入密码，解决办法如下

# 先删除.ssh文件
rm -rf ~/.ssh
# 重新免密
ssh-keygen -t rsa
# 一直回车
# 添加公钥（hadoop102是主机名）
ssh-copy-id hadoop102
# 输入密码
# 免密登录
ssh hadoop102
# 还需要输入密码

在这里插入图片描述

进行Debug

ssh -vvv hadoop102

出现一下情况Not a RSA1 key file /root/.ssh/id_rsa

debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to hadoop102 [x.x.x.x] port 22.
debug1: Connection established.
debug1: permanently_set_uid: 0/0
debug1: identity file /root/.ssh/identity type -1
debug1: identity file /root/.ssh/identity-cert type -1
debug3: Not a RSA1 key file /root/.ssh/id_rsa.
debug2: key_type_from_name: unknown key type ‘-----BEGIN’
debug3: key_read: missing keytype
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug3: key_read: missing whitespace
debug2: key_type_from_name: unknown key type ‘-----END’
debug3: key_read: missing keytype
debug1: identity file /root/.ssh/id_rsa type 1
debug1: identity file /root/.ssh/id_rsa-cert type -1
debug1: identity file /root/.ssh/id_dsa type -1
debug1: identity file /root/.ssh/id_dsa-cert type -1
debug1: identity file /root/.ssh/id_ecdsa type -1
debug1: identity file /root/.ssh/id_ecdsa-cert type -1
debug1: Remote protocol version 1.5, remote software version OpenSSH_5.3
debug1: match: OpenSSH_5.3 pat OpenSSH*
debug1: Local version string SSH-1.5-OpenSSH_5.3
debug2: fd 3 setting O_NONBLOCK
debug1: Waiting for server public key.
debug1: Received server public key (1024 bits) and host key (2048 bits).
debug3: check_host_in_hostfile: host hadoop102 filename /root/.ssh/known_hosts
debug3: check_host_in_hostfile: host hadoop102 filename /root/.ssh/known_hosts
debug3: check_host_in_hostfile: match line 1
debug3: check_host_in_hostfile: host x.x.x.x filename /root/.ssh/known_hosts
debug3: check_host_in_hostfile: host x.x.x.x filename /root/.ssh/known_hosts
debug3: check_host_in_hostfile: match line 1
debug1: Host ‘hadoop102’ is known and matches the RSA1 host key.
debug1: Found key in /root/.ssh/known_hosts:1
debug1: Encryption type: 3des
debug3: Wrote 284 bytes for a total of 304
debug1: Sent encrypted session key.
debug2: cipher_init: set keylen (16 -> 32)
debug2: cipher_init: set keylen (16 -> 32)
debug1: Installing crc compensation attack detector.
debug1: Received encrypted confirmation.
debug3: Wrote 20 bytes for a total of 324
debug1: Doing password authentication.
root@hadoop102’s password:
debug3: Wrote 52 bytes for a total of 376
Connection closed by x.x.x.x

出现这个Not a RSA1 key file /root/.ssh/id_rsa

修改/etc/ssh/sshd_config文件，将Protocol 1改为 Protocol 2

Protocol 2

sshd_config的实例如下


#       $OpenBSD: sshd_config,v 1.80 2008/07/02 02:24:18 djm Exp $

# This is the sshd server system-wide configuration file.  See
# sshd_config(5) for more information.

# This sshd was compiled with PATH=/usr/local/bin:/bin:/usr/bin

# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented.  Uncommented options change a
# default value.

#Port 22
#AddressFamily any
#ListenAddress x.x.x.x
#ListenAddress x.x.x.x

# Disable legacy (protocol version 1) support in the server for new
# installations. In future the default will change to require explicit
# activation of protocol 1
Protocol 2

# HostKey for protocol version 1
#HostKey /etc/ssh/ssh_host_key
# HostKeys for protocol version 2
#HostKey /etc/ssh/ssh_host_rsa_key
#HostKey /etc/ssh/ssh_host_dsa_key

# Lifetime and size of ephemeral version 1 server key
#KeyRegenerationInterval 1h
#ServerKeyBits 1024

# Logging
# obsoletes QuietMode and FascistLogging
#SyslogFacility AUTH
SyslogFacility AUTHPRIV
#LogLevel INFO

# Authentication:

#LoginGraceTime 2m
#PermitRootLogin yes
#StrictModes yes
#MaxAuthTries 6
#MaxSessions 10

RSAAuthentication yes
PubkeyAuthentication yes
AuthorizedKeysFile      .ssh/authorized_keys
AuthorizedKeysCommand none
AuthorizedKeysCommandRunAs nobody

# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
#RhostsRSAAuthentication no
# similar for protocol version 2
#HostbasedAuthentication no
# Change to yes if you don't trust ~/.ssh/known_hosts for
# RhostsRSAAuthentication and HostbasedAuthentication
#IgnoreUserKnownHosts no
# Don't read the user's ~/.rhosts and ~/.shosts files
#IgnoreRhosts yes

# To disable tunneled clear text passwords, change to no here!
#PasswordAuthentication yes
#PermitEmptyPasswords no
PasswordAuthentication yes

# Change to no to disable s/key passwords
#ChallengeResponseAuthentication yes
ChallengeResponseAuthentication no

# Kerberos options
#KerberosAuthentication no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
#KerberosGetAFSToken no
#KerberosUseKuserok yes

# GSSAPI options
#GSSAPIAuthentication no
GSSAPIAuthentication yes
#GSSAPICleanupCredentials yes
GSSAPICleanupCredentials yes
#GSSAPIStrictAcceptorCheck yes
#GSSAPIKeyExchange no

# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication.  Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
#UsePAM no
UsePAM yes

# Accept locale-related environment variables
AcceptEnv LANG LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES
AcceptEnv LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT
AcceptEnv LC_IDENTIFICATION LC_ALL LANGUAGE
AcceptEnv XMODIFIERS

#AllowAgentForwarding yes
#AllowTcpForwarding yes
#GatewayPorts no
#X11Forwarding no
X11Forwarding yes
#X11DisplayOffset 10
#X11UseLocalhost yes
#PrintMotd yes
#PrintLastLog yes
#TCPKeepAlive yes
#UseLogin no
#UsePrivilegeSeparation yes
#       $OpenBSD: sshd_config,v 1.80 2008/07/02 02:24:18 djm Exp $

# This is the sshd server system-wide configuration file.  See
# sshd_config(5) for more information.

# This sshd was compiled with PATH=/usr/local/bin:/bin:/usr/bin

# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented.  Uncommented options change a
# default value.

#Port 22
#AddressFamily any
#ListenAddress x.x.x.x
#ListenAddress x.x.x.x

# Disable legacy (protocol version 1) support in the server for new
# installations. In future the default will change to require explicit
# activation of protocol 1
Protocol 2

# HostKey for protocol version 1
#HostKey /etc/ssh/ssh_host_key
# HostKeys for protocol version 2
#HostKey /etc/ssh/ssh_host_rsa_key
#HostKey /etc/ssh/ssh_host_dsa_key

# Lifetime and size of ephemeral version 1 server key
#KeyRegenerationInterval 1h
#ServerKeyBits 1024

# Logging
# obsoletes QuietMode and FascistLogging
#SyslogFacility AUTH
SyslogFacility AUTHPRIV
#LogLevel INFO

# Authentication:

#LoginGraceTime 2m
#PermitRootLogin yes
#StrictModes yes
#MaxAuthTries 6
#MaxSessions 10

RSAAuthentication yes
PubkeyAuthentication yes
AuthorizedKeysFile      .ssh/authorized_keys
AuthorizedKeysCommand none
AuthorizedKeysCommandRunAs nobody

# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
#RhostsRSAAuthentication no
# similar for protocol version 2
#HostbasedAuthentication no
# Change to yes if you don't trust ~/.ssh/known_hosts for
# RhostsRSAAuthentication and HostbasedAuthentication
#IgnoreUserKnownHosts no
# Don't read the user's ~/.rhosts and ~/.shosts files
#IgnoreRhosts yes

# To disable tunneled clear text passwords, change to no here!
#PasswordAuthentication yes
#PermitEmptyPasswords no
PasswordAuthentication yes

# Change to no to disable s/key passwords
#ChallengeResponseAuthentication yes
ChallengeResponseAuthentication no

# Kerberos options
#KerberosAuthentication no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
#KerberosGetAFSToken no
#KerberosUseKuserok yes

# GSSAPI options
#GSSAPIAuthentication no
GSSAPIAuthentication yes
#GSSAPICleanupCredentials yes
GSSAPICleanupCredentials yes
#GSSAPIStrictAcceptorCheck yes
#GSSAPIKeyExchange no

# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication.  Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
#UsePAM no
UsePAM yes

# Accept locale-related environment variables
AcceptEnv LANG LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES
AcceptEnv LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT
AcceptEnv LC_IDENTIFICATION LC_ALL LANGUAGE
AcceptEnv XMODIFIERS

#AllowAgentForwarding yes
#AllowTcpForwarding yes
#GatewayPorts no
#X11Forwarding no
X11Forwarding yes
#X11DisplayOffset 10
#X11UseLocalhost yes
#PrintMotd yes
#PrintLastLog yes
#TCPKeepAlive yes
#UseLogin no
#UsePrivilegeSeparation yes
#       $OpenBSD: sshd_config,v 1.80 2008/07/02 02:24:18 djm Exp $

# This is the sshd server system-wide configuration file.  See
# sshd_config(5) for more information.

# This sshd was compiled with PATH=/usr/local/bin:/bin:/usr/bin

# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented.  Uncommented options change a
# default value.

#Port 22
#AddressFamily any
#ListenAddress x.x.x.x
#ListenAddress x.x.x.x

# Disable legacy (protocol version 1) support in the server for new
# installations. In future the default will change to require explicit
# activation of protocol 1
Protocol 2

# HostKey for protocol version 1
#HostKey /etc/ssh/ssh_host_key
# HostKeys for protocol version 2
#HostKey /etc/ssh/ssh_host_rsa_key
#HostKey /etc/ssh/ssh_host_dsa_key

# Lifetime and size of ephemeral version 1 server key
#KeyRegenerationInterval 1h
#ServerKeyBits 1024

# Logging
# obsoletes QuietMode and FascistLogging
#SyslogFacility AUTH
SyslogFacility AUTHPRIV
#LogLevel INFO

# Authentication:

#LoginGraceTime 2m
#PermitRootLogin yes
#StrictModes yes
#MaxAuthTries 6
#MaxSessions 10

RSAAuthentication yes
PubkeyAuthentication yes
AuthorizedKeysFile      .ssh/authorized_keys
AuthorizedKeysCommand none
AuthorizedKeysCommandRunAs nobody

# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
#RhostsRSAAuthentication no
# similar for protocol version 2
#HostbasedAuthentication no
# Change to yes if you don't trust ~/.ssh/known_hosts for
# RhostsRSAAuthentication and HostbasedAuthentication
#IgnoreUserKnownHosts no
# Don't read the user's ~/.rhosts and ~/.shosts files
#IgnoreRhosts yes

# To disable tunneled clear text passwords, change to no here!
#PasswordAuthentication yes
#PermitEmptyPasswords no
PasswordAuthentication yes

# Change to no to disable s/key passwords
#ChallengeResponseAuthentication yes
ChallengeResponseAuthentication no

# Kerberos options
#KerberosAuthentication no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
#KerberosGetAFSToken no
#KerberosUseKuserok yes

# GSSAPI options
#GSSAPIAuthentication no
GSSAPIAuthentication yes
#GSSAPICleanupCredentials yes
GSSAPICleanupCredentials yes
#GSSAPIStrictAcceptorCheck yes
#GSSAPIKeyExchange no

# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication.  Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
#UsePAM no
UsePAM yes

# Accept locale-related environment variables
AcceptEnv LANG LC_CTYPE LC_NUMERIC LC_TIME LC_COLLATE LC_MONETARY LC_MESSAGES
AcceptEnv LC_PAPER LC_NAME LC_ADDRESS LC_TELEPHONE LC_MEASUREMENT
AcceptEnv LC_IDENTIFICATION LC_ALL LANGUAGE
AcceptEnv XMODIFIERS

#AllowAgentForwarding yes
#AllowTcpForwarding yes
#GatewayPorts no
#X11Forwarding no
X11Forwarding yes
#X11DisplayOffset 10
#X11UseLocalhost yes
#PrintMotd yes
#PrintLastLog yes
#TCPKeepAlive yes
#UseLogin no
#UsePrivilegeSeparation yes
#PermitUserEnvironment no
#Compression delayed
#ClientAliveInterval 0
#ClientAliveCountMax 3
#ShowPatchLevel no
UseDNS no
#PidFile /var/run/sshd.pid
#MaxStartups 10:30:100
#PermitTunnel no
#ChrootDirectory none

# no default banner path
#Banner none

# override default of no subsystems
Subsystem sftp  /usr/libexec/openssh/sftp-server

# Example of overriding settings on a per-user basis
#Match User anoncvs
#       X11Forwarding no
#       AllowTcpForwarding no
#       ForceCommand cvs server
AddressFamily inet
Ciphers aes128-ctr,aes192-ctr,aes256-ctr
MACs hmac-sha1,umac-64@openssh.com,hmac-ripemd160
坤坤不爱吃鱼
关注
专栏目录
aws的Linux云主机手动添加秘钥
qq_39579242的博客
08-17 1207
login as: ec2-user Authenticating with public key "imported-openssh-key" Last login: Wed Sep 13 07:55:10 2017 from ec2-52-80-79-217.cn-north-1.compute.amazonaws.com.cn [ec2-user@ip-10-0-0-102 ~]$ ...
CentOS8—ssh免密登录
CringS__________的博客
05-12 2115
！！一学就会！！ CentOS8—ssh：7台客户端互相免密登录 ！纯干货！
ssh免密设置后，仍提示输入密码，报错如下：
u012026446的专栏
07-31 1万+
[root@localhost ~]# ssh -vvv XXX.XX.X.XXX OpenSSH_6.4, OpenSSL 1.0.1e-fips 11 Feb 2013 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 51: Applying options for ...
免匙SSH登录失败问题（非常规）
踏云追月
05-31 4509
问题描述： 上周给公司搭建大数据平台，选取三台机器，安装配置一切顺利。后来发现/home目录的挂载盘容量不够用，所以就扩容了，在扩容之前将/home/hadoop文件夹复制到其他地方，扩容后再复制回来，现在问题来了，hadoop文件夹迁移回来后，发现免匙SSH无用了。 问题排查： 1.检测权限 chmod 600 ~/.ssh/authorized_keys chmod 70
centos配置ssh免密钥登录但是仍提示需要输入密码的解决办法
Emotionameng的博客
09-27 2320
centos配置ssh免密钥登录但是仍提示需要输入密码的解决办法 参考 http://www.cnblogs.com/qcly/archive/2013/07/27/3219535.html https://segmentfault.com/q/1010000000445726 完美解决
scp 免密码传输
知非
09-14 1662
项目的自动打版工具需要用到scp，想要不输入密码，就在两个机器上建立了信任关系 A机器  1、#  ssh-keygen -b 1024 -t rsa Generating public/private rsa key pair. Enter file in which to save the key (/root/.ssh/id_rsa):  Enter passphrase
centos配置ssh免密码登录后仍要输入密码的解决方法
09-15
以下是一个详细的解决方法，专门针对CentOS系统中SSH免密码登录后仍需输入密码的问题。 首先，我们来看如何在本地生成SSH密钥对。SSH密钥对包括一个私钥（id_rsa）和一个公钥（id_rsa.pub）。在CentOS中，你可以...
centos7 ssh免密登录自动化配置脚本(ps:已测试过)
02-01
本文将详细介绍如何使用shell和expect脚本在CentOS7系统上实现SSH免密登录的自动化配置。 首先，我们需要理解SSH免密登录的基本原理。SSH免密登录依赖于公钥认证机制。每个SSH用户都有一个密钥对，包括公钥和私钥。...
Centos SSH免密登录
04-03
### Centos SSH免密登录知识点解析 #### 一、实验背景与目的 在现代网络系统管理竞赛或实际运维工作中，实现高效、安全的远程管理是关键能力之一。本实验通过模拟一个具体的网络环境，旨在训练参赛者掌握如何配置...
ssh配置远程免密登录以及遇到的各种问题解决方法
on the way . . .
03-04 4363
Background 首先说下，为什么网上相关经验已经多如牛毛，我还要自己再写呢？ 起因是自己配置的时候，去网上找了好多篇经验，很多基本都是一个思路，只是贴步骤，只知其然，不知其所以然。自己总结下，以后自己使用方便。 1、实现目标 当我们需要远程登录一台linux服务器时，通常使用ssh（基于openssh），一般都默认装的有吧，没有先安装这个服务，这个就像向日葵一样。 使用ssh一般默认需要输入密码 我们就是为了实现免密登录，即ssh远程登录某台服务器时不再输入密码。所以我们需要事先和这台服务器配
./.ssh目录下的authorized_keys, id_rsa, id_rsa.pub, known_hosts使用方法解读
qq_33163046的博客
01-22 1万+
1.id_rsa, id_rsa.pub 与 authorized_keys 假设 A （10.235.##.A）为客户机器，B（10.235.##.B）为目标机； 要达到的目的： A机器ssh登录B机器无需输入密码（加密方式选 rsa|dsa均可以我这里选rsa） 步骤 1、登录A机器，尝试ssh登陆B机器，需要输入密码 [root@AP ~]# ssh root@10.235.##.B CGS Linux Authorized uses only. All activity may be monito.
linux 登录后 显示密码,CentOS配置SSH免密码登录后,仍提示输入密码
weixin_39760434的博客
05-09 142
CentOS配置SSH无密码登录需要3步：生成公钥和私钥导入公钥到认证文件,更改权限测试1.生成公钥和私钥ssh-keygen -t dsa -P '' -f ~/.ssh/id_dsa默认在 ~/.ssh目录生成两个文件：id_rsa ：私钥id_rsa.pub ：公钥2.导入公钥到认证文件2.1 导入本机cat ~/.ssh/id_rsa.pub >> ~/.ssh/a...
SSH使用备忘
Skycat
08-31 513
文章目录自动登录端口映射 自动登录 端口映射
linux|奇怪的知识---账号安全加固，ssh安全加固
zsk_john的技术分享专用博客
02-28 3466
一般情况下，我们对于账号的安全是比较随意的，因为在生产环境里，基本都是使用堡垒机这样的带有安全审计功能的工具对各个主机进行监控，管理，并且结合prometheus，zabbix等等其它监控软件，会对主机的一个整体概况有一个直观的感受。 OK，如果堡垒机什么的任意一个点被持有恶意的人攻破，那么，无疑是会引发数据泄露的，因此，我们需要从根源上对主机做安全加固，比如， 操作系统内的所有用户的密码设定复杂度，例如，密码长度不低于8位，必须带有大小写和特殊符号至少一个，密码不得设定为常用字，例如，不得设置syst
ssh连接失败，排错经验
weixin_33752045的博客
08-07 9026
一、场景描述 ssh连接服务器，发现连接失败，但是对应服务器的ip能够ping通。 场景： [root@yl-web ~]# ssh root@10.1.101.35 ssh_exchange_identification: read: Connection reset by peer [root@yl-web ~]# ping 10.1.101.35 PING 10.1.101....
Centos 5.4下使用ssh key 远程登陆
weixin_34248487的博客
03-10 175
2010-3-8 12:41 大致步骤：在服务器端生成一对密钥，然后公钥保存在服务器用户目录.ssh下的authorized_keys2，是个隐藏的目录。私钥必须将id_dsa下载到客户端，然后通过puttygen.exe生成.ppk文件。当用户登录时，服务器会根据公钥来比较私钥，如果相符就允许登陆，否则拒绝。私钥只保存在客户端中，及时有人知道root密码，没有私钥也不能远...
Paramiko: “not a valid RSA private key file”
jaket5219999的博客
06-17 1561
https://stackoverflow.com/questions/54612609/paramiko-not-a-valid-rsa-private-key-file
由chmod改系统文件权限引ssh登录报ssh_exchange_identification: read: Connection reset by peer无法登陆问题
热门推荐
贤时间
11-23 6万+
root用户下在给某个文件夹下的所有文件改权限的时候，用了chmod -R 命令，咋一看这个命令没啥很正常，也能执行，但是后面的提示让人感觉很不对劲，因为yang下文件没这么多，怎么不相关目录的权限也改了呢，感觉ctrl+c终止，仔细一看原来yang 有一个/，这是个很危险的命令，有点常识的人都知道，根目录下的文件权限不可以乱动啊，当时吓了一跳，于是另开一个终端怎么也连接不上，但是用secureC
centos7操作系统配置免密登录之后ssh免密登录时还需要输入密码
最新发布
10-10
CentOS 7操作系统配置了SSH免密登录后，理论上应该不再需要每次连接时输入密码。如果你仍然遇到这种情况，可能是以下几个原因： 1. **配置错误**：检查`~/.ssh/authorized_keys`文件是否包含了正确的公钥信息，以及...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值