为ssh连接创建别名

14

我想加快连接到特定服务器的速度。

我有说的服务器：

123.123.123.1
123.123.123.2
123.123.123.3

我通常连接以下内容：

ssh -p 12345 my_user@123.123.123.1

这很痛苦，因为服务器之间的唯一区别是ip的最后一个数字。

我尝试了以下代码：

alias ssht='{ ip=$(cat -); ssh -p 12345 my_user@"123.123.123.$ip"; }<<<'

但是我得到一个错误：

karl@karls-laptop ~/scripts $ ssht 1
Pseudo-terminal will not be allocated because stdin is not a terminal.

有没有办法让这个工作？

bash  ssh  alias 
— 卡尔·莫里森
source
— steeldriver '17
您还可以将IP地址和主机名添加到/ etc / hosts文件中，其格式如下，123.123.123.1 host1然后使用ssh myuser@host1 -p12345
— Arronical
4
将它们添加到〜/ .ssh / config
— Kevin Kevin
如果要管理一堆服务器，则可能应该使用Ansible之类的工具，而不是单独管理它们。
— Monica Cellio的抵制SE

Answers:

21

这需要一个功能-简单且健壮，而alias在这种情况下，则是脆弱的。

这样的事情应该做：

function ssht () {
    [[ $1 =~ ^(1|2|3)$ ]] || { echo 'Not a valid last octet value !!' && return ;}
    ip=123.123.123.$1
    ssh my_user@"$ip" -p 12345
}

该条件[[ $1 =~ ^(1|2|3)$ ]]确保您输入了1、2、3中的一个作为第一个参数（任何尾随的参数都将被忽略）。

现在，您可以将所需的最后一个八位位组作为第一个参数：

ssht 1
ssht 2
ssht 3

把这个在你~/.bashrc的有它在任何交互式会话使用。

— 血红素
source
非常好！然而，使其完整，替换exit用return的，包括用户my_user。：）
— 卡尔·莫里森
@KarlMorrison已批准。
— heemayl
2
“这需要一个函数”我使用相同的经验法则，如果涉及参数，请使用函数而不是别名。
— Lasse Meyer
我喜欢这个答案，我认为通过其他一些输入处理octet=$1; [[ $octet =~ ^[0-9]+$ ]] && [[ $octet -lt 255 ]] && [[ $octet -gt 0 ]] && ssh -p <portNumber> user@hostname
— 效果
1
尽管此方法有效，但它是多余的，不需要。只需使用内置~/.ssh/config文件
— ivanivan '17
55

使用预期的方式并将选项和别名写入~/.ssh/config：

Host 1
  Port 12345
  User my_user
  HostName 123.123.123.1

Host 2
  Port 12345
  User my_user
  HostName 123.123.123.2

等等...

然后使用

ssh 1
ssh 2
...
— 贾库耶
source
1
我认为OP正在尝试自动连接需要一个参数（最后一个八位位组）的东西，而不是静态地放置任何东西（这将是最好的方法）。
— heemayl
很难猜测是否需要动态或静态别名。但这是简化编写的标准方法，即使它是动态的，他也可以摆脱编写端口和用户的麻烦。其他答案已经讨论了如何通过bash函数实现自制方法。
— 雅库耶
1
@Jakuje heemayl是正确的。我需要能够通过一个论点。否则，将选择此方法作为答案：）
— Karl Morrison
2
您仍然可以提供ssh config行来Host 123.123.123.*指定端口和用户名！
— Riking
@Riking感谢您的评论。是。此外，IP将自动完成，因此您最终只会写出最后一个数字。
— 贾库耶
16

您可以在中使用模式~/.ssh/config。来自man ssh_config：

PATTERNS
     A pattern consists of zero or more non-whitespace characters, ‘*’ (a
     wildcard that matches zero or more characters), or ‘?’ (a wildcard that
     matches exactly one character).  For example, to specify a set of
     declarations for any host in the “.co.uk” set of domains, the following
     pattern could be used:

           Host *.co.uk

     The following pattern would match any host in the 192.168.0.[0-9] network
     range:

           Host 192.168.0.?

结合：

HostName
    Specifies the real host name to log into.  This can be used to
    specify nicknames or abbreviations for hosts.  If the hostname
    contains the character sequence ‘%h’, then this will be replaced
    with the host name specified on the command line (this is useful
    for manipulating unqualified names).  The character sequence ‘%%’
    will be replaced by a single ‘%’ character, which may be used
    when specifying IPv6 link-local addresses.

因此，在您的中~/.ssh/config，输入：

Host ?
    Hostname 123.123.123.%h
    Port 12345
    User my_user

然后：

$ ssh -v 1
OpenSSH_7.4p1, LibreSSL 2.5.0
debug1: Reading configuration data /home/muru/.ssh/config
debug1: /home/muru/.ssh/config line 41: Applying options for ?
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to 123.123.123.1 [123.123.123.1] port 12345.
debug1: connect to address 123.123.123.1 port 12345: Connection refused
ssh: connect to host 123.123.123.1 port 12345: Connection refused
— uru
source
最好的答案是您的，而不是我的那个高倍副本；）
— Ravexina
7

使用一个函数代替：

function ssht(){
 ssh -p 12345 my_user@123.123.123.$1
}
$ ssht 1
$ ssht 2
$ ...

更好的解决方案是使用ssh config文件：

touch ~/.ssh/config

有些行类似于：

Host some-name
    HostName 123.123.123.1
    User your_user
    Port 22

您还可以使用ssh键提高速度，最后只运行：

ssh some-name

并且您已连接到该服务器。

— 拉韦西纳
source
一个函数如何使用别名？我应该把它放在.bashrc中吗？
— 莫里森
是的，您必须将其放在类似的位置.bashrc，.bash_func然后将其存储在.bashrc文件中。
— Ravexina
3

您甚至不需要使用ssht之类的名称。名称以数字开头，即使只有数字也是ssh配置文件中的有效主机名。

下面对Xubuntu Xenial的作品

我的〜/ .ssh / config的一部分

Host 1
        Hostname bastion.example.me
        User said
        Port 22
        IdentityFile ~/.ssh/id_rsa
        ForwardAgent yes

我运行的命令（在默认情况下，我-vv为详细记录添加到STDOUT您的屏幕下方）

ssh -vv 1

输出量

OpenSSH_7.2p2 Ubuntu-4ubuntu2.2, OpenSSL 1.0.2g  1 Mar 2016
debug1: Reading configuration data /home/said/.ssh/config
debug1: /home/said/.ssh/config line 24: Applying options for 1
debug1: /home/said/.ssh/config line 540: Applying options for *
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug2: resolving "bastion.example.me" port 22
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to bastion.example.me [XXX.YYY.120.51] port 22.
debug1: Connection established.
debug1: identity file /home/said/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /home/said/.ssh/id_rsa-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.2
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.2p2 Ubuntu-4ubuntu2.2
debug1: match: OpenSSH_7.2p2 Ubuntu-4ubuntu2.2 pat OpenSSH* compat 0x04000000
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to bastion.example.me:22 as 'said'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug2: local client KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,ext-info-c
debug2: host key algorithms: ecdsa-sha2-nistp256-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,ssh-ed25519-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc
debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com,aes128-cbc,aes192-cbc,aes256-cbc,3des-cbc
debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zlib@openssh.com,zlib
debug2: compression stoc: none,zlib@openssh.com,zlib
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug2: peer server KEXINIT proposal
debug2: KEX algorithms: curve25519-sha256@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group14-sha1
debug2: host key algorithms: ssh-rsa,rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ssh-ed25519
debug2: ciphers ctos: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: ciphers stoc: chacha20-poly1305@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-gcm@openssh.com,aes256-gcm@openssh.com
debug2: MACs ctos: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: MACs stoc: umac-64-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-sha2-512-etm@openssh.com,hmac-sha1-etm@openssh.com,umac-64@openssh.com,umac-128@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1
debug2: compression ctos: none,zlib@openssh.com
debug2: compression stoc: none,zlib@openssh.com
debug2: languages ctos: 
debug2: languages stoc: 
debug2: first_kex_follows 0 
debug2: reserved 0 
debug1: kex: algorithm: curve25519-sha256@libssh.org
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:44tChrTUMwuRcOi6laiYlf6VM3qAD+PEn9EdNMribFw
debug1: Host 'bastion.example.me' is known and matches the ECDSA host key.
debug1: Found key in /home/said/.ssh/known_hosts:69
debug2: set_newkeys: mode 1
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug2: set_newkeys: mode 0
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS received
debug2: key: /home/said/.ssh/id_rsa (0x562c764294f0), explicit, agent
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_input_ext_info: server-sig-algs=<rsa-sha2-256,rsa-sha2-512>
debug2: service_accept: ssh-userauth
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/said/.ssh/id_rsa
debug2: we sent a publickey packet, wait for reply
debug1: Server accepts key: pkalg rsa-sha2-512 blen 279
debug2: input_userauth_pk_ok: fp SHA256:KQNLYiJICyNbKmIxVVgc67RF+qRKjNi3w+0iXz/YDyk
debug1: Authentication succeeded (publickey).
Authenticated to bastion.example.me ([XXX.YYY.120.51]:22).
debug1: channel 0: new [client-session]
debug2: channel 0: send open
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: pledge: network
debug1: client_input_global_request: rtype hostkeys-00@openssh.com want_reply 0
debug2: callback start
debug1: Requesting authentication agent forwarding.
debug2: channel 0: request auth-agent-req@openssh.com confirm 0
debug2: fd 3 setting TCP_NODELAY
debug2: client_session2_setup: id 0
debug2: channel 0: request pty-req confirm 1
debug2: channel 0: request shell confirm 1
debug2: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
debug2: channel_input_status_confirm: type 99 id 0
debug2: PTY allocation request accepted on channel 0
debug2: channel 0: rcvd adjust 2097152
debug2: channel_input_status_confirm: type 99 id 0
debug2: shell request accepted on channel 0
Welcome to Ubuntu 16.04.2 LTS (GNU/Linux 4.8.0-42-lowlatency x86_64)
<TRUNCATED CUSTOM MOTD>
$

更新-以下是一种骇人听闻的替代解决方案，仅用于基础训练，可能用于快速又脏的东西：

alias ssht='f(){ ssh -p 22 said@192.168.0.$@;unset -f f;}&&f'

它能做什么

  • 创建临时功能
  • 将所有参数传递给它
  • 进行SSH连接
  • 会话结束后，请取消设置该功能，这样它就不会继续存在
  • 它可以采取额外的参数，这意味着你可以额外链SSH选项，如隧道（-L，-R，-D），详细模式（-vv），没有TTY（ -T）等。

例如，我想启动一个没有终端的袜子代理

$ ssht 2 -vv -D 1080 -T
OpenSSH_7.2p2 Ubuntu-4ubuntu2.2, OpenSSL 1.0.2g  1 Mar 2016
debug1: Reading configuration data /home/said/.ssh/config
debug1: /home/said/.ssh/config line 540: Applying options for *
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Applying options for *
debug2: resolving "192.168.0.2" port 22
debug2: ssh_connect_direct: needpriv 0
debug1: Connecting to 192.168.0.2 [192.168.0.2] port 22.
debug1: Connection established.
<TRUNCATED>
Welcome to Linux Mint 18.1 Serena (GNU/Linux 4.4.0-81-generic x86_64)

 * Documentation:  https://www.linuxmint.com

98 packages can be updated.
0 updates are security updates.

正如你所看到的，没有命令提示符，它与执行-vv，-T，-D 1080论点。

我也可以在机器上验证隧道（基本上是SOCKS5代理）

$ ss -ltnp | grep 1080
LISTEN     0      128    127.0.0.1:1080                     *:*                   users:(("ssh",pid=17038,fd=6))
— sdkks
source
By using our site, you acknowledge that you have read and understand our Cookie Policy and Privacy Policy.
Licensed under cc by-sa 3.0 with attribution required.