8/23/2023 0 Comments Autibon ssh bastion![]() ![]() protected and desktop are both using the fish bastion's ~/.ssh/config: Host * I can log in to the same user on protected from root on desktop.Īll three systems are running Arch Linux. emptying my ~/.config/fish/nfig made no difference, and 2. I have also tried, but I believe this doesn't apply for two reasons - 1. Ssh -vvv protected as user on desktop shows: OpenSSH_7.9p1, OpenSSL 1.1.1 ĭebug1: Reading configuration data /home/user/.ssh/configĭebug1: /home/user/.ssh/config line 1: Applying options for *ĭebug1: /home/user/.ssh/config line 10: Applying options for protectedĭebug1: Reading configuration data /etc/ssh/ssh_configĭebug1: Executing proxy command: exec ssh bastion -W protected:22ĭebug1: identity file /home/user/.ssh/id_protected type 0ĭebug1: identity file /home/user/.ssh/id_protected-cert type -1ĭebug1: Local version string SSH-2.0-OpenSSH_7.9ĭebug1: ssh_exchange_identification: \033[3g The second line does not display when connecting from user on desktop. ![]() Running the same on protected shows the same output until: debug1: SSH2_MSG_KEXINIT sent ĭebug1: SSH2_MSG_KEXINIT received The bastion host appears to be forwarding properly - running $(which sshd) -Ddp 10222 (per ) shows the same debug1: channel 0: connected to protected port 22 line on both. ssh directories ( #cp -r ~/.ssh /home/user chown -R user:user /home/user/.ssh). However, user can log in directly to the bastion host and from there to the protected host.īoth root and user have the same contents in their. When I run ssh protected as user on desktop, I get no output - just a blank line, like it's waiting for something. When run ssh protected as root on desktop, I connect fine. I have two users on desktop - root and user.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |