刚怀孕吃什么对胎儿好| 什么的仪式| 牙龈肿痛用什么药| 利有攸往是什么意思| 多多益善的意思是什么| lily是什么花| 家里有蚂蚁是什么原因| 煮茶叶蛋用什么茶| 吃什么可以丰胸| 肉质瘤是什么东西| 长方脸适合什么样的发型| 为什么会得心脏病| 拉肚子是什么原因| 梦见相亲是什么意思| 孩子脚后跟疼是什么原因| 梦见什么是怀孕的征兆| 做梦梦见自己生孩子是什么意思| 相机hdr功能是什么意思| 法益是什么意思| dan是什么意思| 儿童嗓子哑了什么原因| 一岁宝宝吃什么| c2m模式是什么意思| 弱碱性水是什么水| 前列腺炎吃什么中药| cm是什么意思| 来苏水又叫什么名字| 浅表性胃炎吃什么中成药最好| 膝关节退行性改变是什么意思| 白芷是什么| 慎重的意思是什么| 吃秋葵有什么禁忌| 神的国和神的义指的是什么| 白天不咳嗽晚上咳嗽吃什么药| 国粹是什么| 下水是什么意思| rian是什么意思| 疝气什么症状| bpd是什么| 水泡型脚气用什么药好| 什么石穿| 香蕉有什么作用与功效| 乳腺导管扩张吃什么药| 收悉是什么意思| 柜姐是什么意思| 显妣是什么意思| 四月23日是什么星座| 什么是用神| 金达克宁和达克宁有什么区别| uranus是什么星球| 艾灸后放屁多是什么原因| 五常法指的是什么| 呵呵什么意思| 骨髓瘤是什么原因引起的| 洋葱配什么菜炒好吃| 藏红花适合什么样的人喝| 什么药止咳最好| mj是什么单位| 过山风是什么蛇| 下乡插队是什么意思| 扁桃是什么水果| 杯葛是什么意思| 缺蛋白质吃什么补得快| 天天睡觉做梦是什么原因| 猪咳嗽用什么药效果好| 海水什么颜色| 微信被拉黑后显示什么| 月经不正常去医院检查什么项目| 像狐狸的狗是什么狗| 什么叫卒中| 什么鱼不能吃脑筋急转弯| 金木水火土代表什么| 百雀羚适合什么年龄段| 无动于衷什么意思| 男人鼻头有痣代表什么| 龙井是什么茶| 梦见掉头发是什么意思| cl是什么单位| 彩色相片什么时候出现| 印堂发亮预兆着什么| b是什么元素| 当兵有什么要求| 什么生辉| 满天星是什么意思| 保家仙是什么| 禅茶一味什么意思| 看见蛇有什么预兆| 一人一口是什么字| 隅读什么| s是什么意思| 玉米什么时候成熟| 大姨妈发黑是什么原因| 双肺纹理增多增粗是什么病| 老本行是什么意思| 心肌梗塞吃什么药| 眼压高用什么眼药水| 阴道瘙痒是什么原因| 武将是什么生肖| 输尿管不扩张什么意思| 草木灰是什么| 今年什么时候暑伏| 释放是什么意思| 湿热便秘吃什么中成药| 伏脉常见于什么病| 郡主是什么意思| 九孔藕和七孔藕有什么区别| bkg是什么意思| 男生下巴长痘痘是什么原因| 节节草有什么作用| 没有什么过不去| 蚊香灰有什么作用| 三月份生日是什么星座| 梦见做手术是什么意思| 玛卡和什么搭配壮阳效果最佳| 高血糖能吃什么水果| 圣诞节在什么时候| 锦鲤什么意思| 摩羯座什么性格| 吃什么养脾胃| 蚂蚱吃什么食物| 文字属于五行属什么| 狗狗流眼泪是什么原因| c1开什么车| 一什么杯子| 脚后跟干裂起硬皮用什么药| 咳嗽有痰是什么原因| 为什么感冒喝白酒好了| 向日葵是什么意思| 紧急避孕药什么时候吃最有效| 什么人什么目| 眼睛突然红了是什么原因| 低密度脂蛋白高有什么症状| 痤疮吃什么药| 静脉曲张挂号挂什么科| 茶壶里煮饺子的歇后语是什么| 右肺中叶少许纤维灶是什么意思| 薄姬为什么讨厌窦漪房| 男科什么医院好| 什么对眼睛好| 狗尾续貂是什么意思| 1992年五行属什么| 鹅蛋炒香菜治什么病| 为什么老是说梦话| 把头是什么意思| 牵牛花是什么颜色的| 什么水果解酒| cm是什么| 为什么人不会飞| 戒定真香是什么意思| 脚肿是什么病的前兆| 白细胞高吃什么药| 美女是什么生肖| 接触是什么意思| 手臂长斑是什么原因| 什么叫越位| 胸部dr是什么| 梦见双头蛇是什么征兆| 党工委书记是什么级别| 什么是泥炭土| 鸡蛋液是什么| 对酒当歌是什么生肖| 6月23号是什么日子| 大便隐血弱阳性是什么意思| 介入医学科是什么科室| 看结石挂什么科室| 羊肉炖什么补肾壮阳| 东北大拉皮是什么做的| 吃肝补什么| 什么是自限性疾病| 撮鸟是什么意思| 长史相当于现在什么官| 后壁和前壁有什么区别| 猪笼入水是什么意思| 晚上一点多是什么时辰| 白细胞低是什么意思| 穿刺检查是什么意思| 无奇不有是什么意思| 9.10是什么星座| 凶猛的动物是什么生肖| 男生的蛋蛋长什么样| 淑女气质给人什么感觉| siri是什么| 真菌阳性是什么意思| 天麻不能和什么一起吃| 金字塔里面有什么| 大学团委书记什么级别| 什么是心悸| 明媚是什么意思| 属马是什么命| 格斗和散打有什么区别| 咽喉充血是什么原因| 早晨起来口干口苦是什么原因| 柬埔寨为什么叫柬埔寨| 神隐是什么意思| 尿结石是什么引起的| 有什么神话故事| 维生素c对身体有什么好处| 蜘蛛的血是什么颜色的| 三颗星是什么军衔| 梦见水是什么征兆| 早上右眼跳是什么预兆| 昆虫记是什么类型的书| 紧急避孕药什么时候吃最好| 冰心原名是什么| 7.14什么情人节| 青少年手抖是什么原因| 突然流鼻血是什么征兆| 解脲脲原体阳性是什么意思| 绝经什么意思| 马踏飞燕什么意思| 脂血是什么意思| 肝结节是什么病严重吗| 宋江是什么生肖| 喝什么茶养肝护肝排毒| 突然眩晕是什么原因| 住院医师是什么级别| 裸花紫珠是主治什么病| 大腿根部内侧瘙痒用什么药膏| 斩衰是什么意思| 腿弯处的筋痛是什么原因| 手足口病是什么症状| 睡觉食管反流什么原因| 1217是什么星座| 肚子一直响是什么原因| 肝阳性是什么意思| 传播什么| 920是什么意思| 奔走相告的走是什么意思| 吃什么能增强免疫力| 牙疼吃什么药效果最好| 是什么为什么怎么办| 狗取什么名字好| 心跳太快吃什么药| 右肾错构瘤是什么病| 慈禧为什么要毒死光绪| 肠胃炎喝什么药| 浅表性胃炎什么症状| 为什么会血热| 身上长白色的斑点是什么原因| 胆固醇高对身体有什么危害| 鸡胸挂什么科| 1月3号是什么星座| 斥巨资是什么意思| ig是什么意思| 光纤和宽带有什么区别| 梅花是什么颜色| AT代表什么| 鸟大了什么林子都有| 1218是什么意思| 博文是什么意思| 白头发有什么方法变黑| 农历五月是什么月| 什么叫肠上皮化生| 将军是什么军衔| 汗手适合盘什么手串| 酸汤鱼用什么鱼| 肌膜炎是什么原因造成的| 经信局是干什么的| 女人脚心发热吃什么药| 氯化镁是什么| 高字是什么结构| 送对象什么礼物好| 基数是什么意思| 农历7月是什么星座| 百度Jump to content

桂圆有什么功效

From Wikipedia, the free encyclopedia
Secure Shell
Protocol stack
Purposesecure connection, remote access
Developer(s)Tatu Yl?nen, Internet Engineering Task Force (IETF)
Introduction1995
OSI layerTransport layer through application layer
Port(s)22
RFC(s)RFC 4250, RFC 4251, RFC 4252, RFC 4253, RFC 4254
百度 总统府官员称,我们已经接到报告,救援行动正在进行中。

The Secure Shell Protocol (SSH Protocol) is a cryptographic network protocol for operating network services securely over an unsecured network.[1] Its most notable applications are remote login and command-line execution.

SSH was designed for Unix-like operating systems as a replacement for Telnet and unsecured remote Unix shell protocols, such as the Berkeley Remote Shell (rsh) and the related rlogin and rexec protocols, which all use insecure, plaintext methods of authentication, such as passwords.

Since mechanisms like Telnet and Remote Shell are designed to access and operate remote computers, sending the authentication tokens (e.g. username and password) for this access to these computers across a public network in an unsecured way poses a great risk of third parties obtaining the password and achieving the same level of access to the remote system as the telnet user. Secure Shell mitigates this risk through the use of encryption mechanisms that are intended to hide the contents of the transmission from an observer, even if the observer has access to the entire data stream.[2]

Finnish computer scientist Tatu Yl?nen designed SSH in 1995 and provided an implementation in the form of two commands, ssh and slogin, as secure replacements for rsh and rlogin, respectively. Subsequent development of the protocol suite proceeded in several developer groups, producing several variants of implementation. The protocol specification distinguishes two major versions, referred to as SSH-1 and SSH-2. The most commonly implemented software stack is OpenSSH, released in 1999 as open-source software by the OpenBSD developers. Implementations are distributed for all types of operating systems in common use, including embedded systems.

SSH applications are based on a client–server architecture, connecting an SSH client instance with an SSH server.[3] SSH operates as a layered protocol suite comprising three principal hierarchical components: the transport layer provides server authentication, confidentiality, and integrity; the user authentication protocol validates the user to the server; and the connection protocol multiplexes the encrypted tunnel into multiple logical communication channels.[1]

Definition

[edit]

SSH uses public-key cryptography to authenticate the remote computer and allow it to authenticate the user, if necessary.[3]

SSH may be used in several methodologies. In the simplest manner, both ends of a communication channel use automatically generated public-private key pairs to encrypt a network connection, and then use a password to authenticate the user.

When the public-private key pair is generated by the user manually, the authentication is essentially performed when the key pair is created, and a session may then be opened automatically without a password prompt. In this scenario, the public key is placed on all computers that must allow access to the owner of the matching private key, which the owner keeps private. While authentication is based on the private key, the key is never transferred through the network during authentication. SSH only verifies that the same person offering the public key also owns the matching private key.

In all versions of SSH it is important to verify unknown public keys, i.e. associate the public keys with identities, before accepting them as valid. Accepting an attacker's public key without validation will authorize an unauthorized attacker as a valid user.

Authentication: OpenSSH key management

[edit]

On Unix-like systems, the list of authorized public keys is typically stored in the home directory of the user that is allowed to log in remotely, in the file ~/.ssh/authorized_keys.[4] This file is respected by SSH only if it is not writable by anything apart from the owner and root. When the public key is present on the remote end and the matching private key is present on the local end, typing in the password is no longer required. However, for additional security the private key itself can be locked with a passphrase.

The private key can also be looked for in standard places, and its full path can be specified as a command line setting (the option -i for ssh). The ssh-keygen utility produces the public and private keys, always in pairs.

Use

[edit]

SSH is typically used to log into a remote computer's shell or command-line interface (CLI) and to execute commands on a remote server. It also supports mechanisms for tunneling, forwarding of TCP ports and X11 connections and it can be used to transfer files using the associated SSH File Transfer Protocol (SFTP) or Secure Copy Protocol (SCP).[3]

SSH uses the client–server model. An SSH client program is typically used for establishing connections to an SSH daemon, such as sshd, accepting remote connections. Both are commonly present on most modern operating systems, including macOS, most distributions of Linux, OpenBSD, FreeBSD, NetBSD, Solaris and OpenVMS. Notably, versions of Windows prior to Windows 10 version 1709 do not include SSH by default, but proprietary, freeware and open source versions of various levels of complexity and completeness did and do exist (see Comparison of SSH clients). In 2018 Microsoft began porting the OpenSSH source code to Windows[5] and in Windows 10 version 1709, an official Win32 port of OpenSSH is now available.

File managers for UNIX-like systems (e.g. Konqueror) can use the FISH protocol to provide a split-pane GUI with drag-and-drop. The open source Windows program WinSCP[6] provides similar file management (synchronization, copy, remote delete) capability using PuTTY as a back-end. Both WinSCP[7] and PuTTY[8] are available packaged to run directly off a USB drive, without requiring installation on the client machine. Crostini on ChromeOS comes with OpenSSH by default. Setting up an SSH server in Windows typically involves enabling a feature in the Settings app.

SSH is important in cloud computing to solve connectivity problems, avoiding the security issues of exposing a cloud-based virtual machine directly on the Internet. An SSH tunnel can provide a secure path over the Internet, through a firewall to a virtual machine.[9]

The IANA has assigned TCP port 22, UDP port 22 and SCTP port 22 for this protocol.[10] IANA had listed the standard TCP port 22 for SSH servers as one of the well-known ports as early as 2001.[11] SSH can also be run using SCTP rather than TCP as the connection oriented transport layer protocol.[12]

Historical development

[edit]

Version 1

[edit]

In 1995, Tatu Yl?nen, a researcher at Helsinki University of Technology in Finland designed the first version of the protocol (now called SSH-1) prompted by a password-sniffing attack at his university network.[13] The goal of SSH was to replace the earlier rlogin, TELNET, FTP[14] and rsh protocols, which did not provide strong authentication nor guarantee confidentiality. He chose the port number 22 because it is between telnet (port 23) and ftp (port 21).[15]

Yl?nen released his implementation as freeware in July 1995, and the tool quickly gained in popularity. Towards the end of 1995, the SSH user base had grown to 20,000 users in fifty countries.[16]

In December 1995, Yl?nen founded SSH Communications Security to market and develop SSH. The original version of the SSH software used various pieces of free software, such as GNU libgmp, but later versions released by SSH Communications Security evolved into increasingly proprietary software.

It was estimated that by 2000 the number of users had grown to 2 million.[17]

Version 2

[edit]

In 2006, after being discussed in a working group named "secsh",[18] a revised version of the SSH protocol, SSH-2 was adopted as a standard.[19] This version offers improved security and new features, but is not compatible with SSH-1. For example, it introduces new key-exchange mechanisms like Diffie–Hellman key exchange, improved data integrity checking via message authentication codes like MD5 or SHA-1, which can be negotiated between client and server. SSH-2 also adds stronger encryption methods like AES which eventually replaced weaker and compromised ciphers from the previous standard like 3DES.[20][21][19] New features of SSH-2 include the ability to run any number of shell sessions over a single SSH connection.[22] Due to SSH-2's superiority and popularity over SSH-1, some implementations such as libssh (v0.8.0+),[23] Lsh[24] and Dropbear[25] eventually supported only the SSH-2 protocol.

Version 1.99

[edit]

In January 2006, well after version 2.1 was established, RFC 4253 specified that an SSH server supporting 2.0 as well as prior versions should identify its protocol version as 1.99.[26] This version number does not reflect a historical software revision, but a method to identify backward compatibility.

OSSH and OpenSSH

[edit]

In 1999, developers, desiring availability of a free software version, restarted software development from the 1.2.12 release of the original SSH program, which was the last released under an open source license.[27] This served as a code base for Bj?rn Gr?nvall's OSSH software.[28] Shortly thereafter, OpenBSD developers forked Gr?nvall's code and created OpenSSH, which shipped with Release 2.6 of OpenBSD. From this version, a "portability" branch was formed to port OpenSSH to other operating systems.[29]

As of 2005, OpenSSH was the single most popular SSH implementation, being the default version in a large number of operating system distributions. OSSH meanwhile has become obsolete.[30] OpenSSH continues to be maintained and supports the SSH-2 protocol, having expunged SSH-1 support from the codebase in the OpenSSH 7.6 release.

Future

[edit]

In 2023, an alternative to traditional SSH was proposed under the name SSH3[31][32][33] by PhD student Fran?ois Michel and Professor Olivier Bonaventure and its code has been made open source.[34] This new version implements the original SSH Connection Protocol but operates on top of HTTP/3, which runs on QUIC. It offers multiple features such as:

  • Faster session establishment, reducing the number of Round-trip delays from 5-7 to 3.
  • High security: while SSHv2 relies on its own protocols, SSH3 leverages TLS 1.3, QUIC, and HTTP.
  • UDP port forwarding
  • X.509 certificates
  • OpenID Connect

However, the name SSH3 is under discussion, and the project aims to rename itself to a more suitable name.[35] The discussion stems from the fact that this new implementation significantly revises the SSH protocol, suggesting it should not be called SSH3.

Uses

[edit]
Example of tunneling an X11 application over SSH: the user 'josh' has "SSHed" from the local machine 'foofighter' to the remote machine 'tengwar' to run xeyes.
Logging into OpenWrt via SSH using PuTTY running on Windows.

SSH is a protocol that can be used for many applications across many platforms including most Unix variants (Linux, the BSDs including Apple's macOS, and Solaris), as well as Microsoft Windows. Some of the applications below may require features that are only available or compatible with specific SSH clients or servers. For example, using the SSH protocol to implement a VPN is possible, but presently only with the OpenSSH server and client implementation.

  • For login to a shell on a remote host (replacing Telnet and rlogin)
  • For executing a single command on a remote host (replacing rsh)
  • For setting up automatic (passwordless) login to a remote server (for example, using OpenSSH[36])
  • In combination with rsync to back up, copy and mirror files efficiently and securely
  • For forwarding a port
  • For tunneling (not to be confused with a VPN, which routes packets between different networks, or bridges two broadcast domains into one).
  • For using as a full-fledged encrypted VPN. Note that only OpenSSH server and client supports this feature.
  • For forwarding X from a remote host (possible through multiple intermediate hosts)
  • For browsing the web through an encrypted proxy connection with SSH clients that support the SOCKS protocol.
  • For securely mounting a directory on a remote server as a filesystem on a local computer using SSHFS.
  • For automated remote monitoring and management of servers through one or more of the mechanisms discussed above.
  • For development on a mobile or embedded device that supports SSH.
  • For securing file transfer protocols.

File transfer protocols

[edit]

The Secure Shell protocols are used in several file transfer mechanisms.

Architecture

[edit]
Diagram of the SSH-2 binary packet.

The SSH protocol has a layered architecture with three separate components:

  • The transport layer (RFC 4253) typically uses the Transmission Control Protocol (TCP) of TCP/IP, reserving port number 22 as a server listening port. This layer handles initial key exchange as well as server authentication, and sets up encryption, compression, and integrity verification. It exposes to the upper layer an interface for sending and receiving plaintext packets with a size of up to 32,768 bytes each, but more can be allowed by each implementation. The transport layer also arranges for key re-exchange, usually after 1 GB of data has been transferred or after one hour has passed, whichever occurs first.
  • The user authentication layer (RFC 4252) handles client authentication, and provides a suite of authentication algorithms. Authentication is client-driven: when one is prompted for a password, it may be the SSH client prompting, not the server. The server merely responds to the client's authentication requests. Widely used user-authentication methods include the following:
    • password: a method for straightforward password authentication, including a facility allowing a password to be changed. Not all programs implement this method.
    • publickey: a method for public-key-based authentication, usually supporting at least DSA, ECDSA or RSA keypairs, with other implementations also supporting X.509 certificates.
    • keyboard-interactive (RFC 4256): a versatile method where the server sends one or more prompts to enter information and the client displays them and sends back responses keyed-in by the user. Used to provide one-time password authentication such as S/Key or SecurID. Used by some OpenSSH configurations when PAM is the underlying host-authentication provider to effectively provide password authentication, sometimes leading to inability to log in with a client that supports just the plain password authentication method.
    • GSSAPI authentication methods which provide an extensible scheme to perform SSH authentication using external mechanisms such as Kerberos 5 or NTLM, providing single sign-on capability to SSH sessions. These methods are usually implemented by commercial SSH implementations for use in organizations, though OpenSSH does have a working GSSAPI implementation.
  • The connection layer (RFC 4254) defines the concept of channels, channel requests, and global requests, which define the SSH services provided. A single SSH connection can be multiplexed into multiple logical channels simultaneously, each transferring data bidirectionally. Channel requests are used to relay out-of-band channel-specific data, such as the changed size of a terminal window, or the exit code of a server-side process. Additionally, each channel performs its own flow control using the receive window size. The SSH client requests a server-side port to be forwarded using a global request. Standard channel types include:
    • shell for terminal shells, SFTP and exec requests (including SCP transfers)
    • direct-tcpip for client-to-server forwarded connections
    • forwarded-tcpip for server-to-client forwarded connections
  • The SSHFP DNS record (RFC 4255) provides the public host key fingerprints in order to aid in verifying the authenticity of the host.

This open architecture provides considerable flexibility, allowing the use of SSH for a variety of purposes beyond a secure shell. The functionality of the transport layer alone is comparable to Transport Layer Security (TLS); the user-authentication layer is highly extensible with custom authentication methods; and the connection layer provides the ability to multiplex many secondary sessions into a single SSH connection, a feature comparable to BEEP and not available in TLS.

Algorithms

[edit]

Vulnerabilities

[edit]

SSH-1

[edit]

In 1998, a vulnerability was described in SSH 1.5 which allowed the unauthorized insertion of content into an encrypted SSH stream due to insufficient data integrity protection from CRC-32 used in this version of the protocol.[42][43] A fix known as SSH Compensation Attack Detector[44] was introduced into most implementations. Many of these updated implementations contained a new integer overflow vulnerability[45] that allowed attackers to execute arbitrary code with the privileges of the SSH daemon, typically root.

In January 2001 a vulnerability was discovered that allows attackers to modify the last block of an IDEA-encrypted session.[46] The same month, another vulnerability was discovered that allowed a malicious server to forward a client authentication to another server.[47]

Since SSH-1 has inherent design flaws which make it vulnerable, it is now generally considered obsolete and should be avoided by explicitly disabling fallback to SSH-1.[47] Most modern servers and clients support SSH-2.[48]

CBC plaintext recovery

[edit]

In November 2008, a theoretical vulnerability was discovered for all versions of SSH which allowed recovery of up to 32 bits of plaintext from a block of ciphertext that was encrypted using what was then the standard default encryption mode, CBC.[49] The most straightforward solution is to use CTR, counter mode, instead of CBC mode, since this renders SSH resistant to the attack.[49]

Suspected decryption by NSA

[edit]

On December 28, 2014 Der Spiegel published classified information[50] leaked by whistleblower Edward Snowden which suggests that the National Security Agency may be able to decrypt some SSH traffic. The technical details associated with such a process were not disclosed. A 2017 analysis of the CIA hacking tools BothanSpy and Gyrfalcon suggested that the SSH protocol was not compromised.[51]

Terrapin attack

[edit]

A novel man-in-the-middle attack against most current ssh implementations was discovered in 2023. It was named the Terrapin attack by its discoverers.[52][53] However, the risk is mitigated by the requirement to intercept a genuine ssh session, and that the attack is restricted in its scope, fortuitously resulting mostly in failed connections.[54][55] The ssh developers have stated that the major impact of the attack is to degrade the keystroke timing obfuscation features of ssh.[55] The vulnerability was fixed in OpenSSH 9.6, but requires both client and server to be upgraded for the fix to be fully effective.

Standards documentation

[edit]

The following RFC publications by the IETF "secsh" working group document SSH-2 as a proposed Internet standard.

  • RFC 4250The Secure Shell (SSH) Protocol Assigned Numbers
  • RFC 4251The Secure Shell (SSH) Protocol Architecture
  • RFC 4252The Secure Shell (SSH) Authentication Protocol
  • RFC 4253The Secure Shell (SSH) Transport Layer Protocol
  • RFC 4254The Secure Shell (SSH) Connection Protocol
  • RFC 4255Using DNS to Securely Publish Secure Shell (SSH) Key Fingerprints
  • RFC 4256Generic Message Exchange Authentication for the Secure Shell Protocol (SSH)
  • RFC 4335The Secure Shell (SSH) Session Channel Break Extension
  • RFC 4344The Secure Shell (SSH) Transport Layer Encryption Modes
  • RFC 4345Improved Arcfour Modes for the Secure Shell (SSH) Transport Layer Protocol

The protocol specifications were later updated by the following publications:

  • RFC 4419Diffie-Hellman Group Exchange for the Secure Shell (SSH) Transport Layer Protocol (March 2006)
  • RFC 4432RSA Key Exchange for the Secure Shell (SSH) Transport Layer Protocol (March 2006)
  • RFC 4462Generic Security Service Application Program Interface (GSS-API) Authentication and Key Exchange for the Secure Shell (SSH) Protocol (May 2006)
  • RFC 4716The Secure Shell (SSH) Public Key File Format (November 2006)
  • RFC 4819Secure Shell Public Key Subsystem (March 2007)
  • RFC 5647AES Galois Counter Mode for the Secure Shell Transport Layer Protocol (August 2009)
  • RFC 5656Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer (December 2009)
  • RFC 6187X.509v3 Certificates for Secure Shell Authentication (March 2011)
  • RFC 6239Suite B Cryptographic Suites for Secure Shell (SSH) (May 2011)
  • RFC 6594Use of the SHA-256 Algorithm with RSA, Digital Signature Algorithm (DSA), and Elliptic Curve DSA (ECDSA) in SSHFP Resource Records (April 2012)
  • RFC 6668SHA-2 Data Integrity Verification for the Secure Shell (SSH) Transport Layer Protocol (July 2012)
  • RFC 7479Ed25519 SSHFP Resource Records (March 2015)
  • RFC 5592Secure Shell Transport Model for the Simple Network Management Protocol (SNMP) (June 2009)
  • RFC 6242Using the NETCONF Protocol over Secure Shell (SSH) (June 2011)
  • RFC 8332Use of RSA Keys with SHA-256 and SHA-512 in the Secure Shell (SSH) Protocol (March 2018)
  • RFC 8709Ed25519 and Ed448 Public Key Algorithms for the Secure Shell (SSH) Protocol (February 2020)
  • draft-gerhards-syslog-transport-sshSSH transport mapping for SYSLOG (July 2006)
  • draft-ietf-secsh-filexferSSH File Transfer Protocol (July 2006)
  • draft-ietf-sshm-ssh-agent - SSH Agent Protocol (March 2025)

In addition, the OpenSSH project includes several vendor protocol specifications/extensions:

See also

[edit]

References

[edit]
  1. ^ a b T. Ylonen; C. Lonvick (January 2006). The Secure Shell (SSH) Protocol Architecture. IETF Trust. doi:10.17487/RFC4251. RFC 4251.
  2. ^ "Missouri University S&T: Secure Telnet".
  3. ^ a b c T. Ylonen; C. Lonvick (January 2006). The Secure Shell (SSH) Authentication Protocol. IETF Trust. doi:10.17487/RFC4252. RFC 4252.
  4. ^ "How To Set Up Authorized Keys". Archived from the original on 2025-08-05.
  5. ^ Win-32 OpenSSH
  6. ^ "WinSCP home page". Archived from the original on 2025-08-05.
  7. ^ "WinSCP page for PortableApps.com". Archived from the original on 2025-08-05.
  8. ^ "PuTTY page for PortableApps.com". Archived from the original on 2025-08-05.
  9. ^ Amies, A; Wu, C F; Wang, G C; Criveti, M (2012). "Networking on the cloud". IBM developerWorks. Archived from the original on 2025-08-05.
  10. ^ "Service Name and Transport Protocol Port Number Registry".
  11. ^ "Service Name and Transport Protocol Port Number Registry". iana.org. Archived from the original on 2025-08-05.
  12. ^ Seggelmann, R.; Tuxen, M.; Rathgeb, E.P. (18–20 July 2012). SSH over SCTP — Optimizing a multi-channel protocol by adapting it to SCTP. 8th International Symposium on Communication Systems, Networks & Digital Signal Processing (CSNDSP). pp. 1–6. doi:10.1109/CSNDSP.2012.6292659. ISBN 978-1-4577-1473-3. S2CID 8415240.
  13. ^ Tatu Yl?nen. "The new skeleton key: changing the locks in your network environment". Archived from the original on 2025-08-05.
  14. ^ Tatu Yl?nen. "SSH Port". Archived from the original on 2025-08-05.
  15. ^ Yl?nen, Tatu. "The story of the SSH port is 22". www.ssh.com. Retrieved 2025-08-05.
  16. ^ Barrett, Daniel J.; Silverman, Richard E. (2001). SSH, the secure shell: the definitive guide (1st ed.). Cambridge [Mass.]: O'Reilly. p. 11. ISBN 978-0-596-00011-0.
  17. ^ Nicholas Rosasco and David Larochelle. "How and Why More Secure Technologies Succeed in Legacy Markets: Lessons from the Success of SSH" (PDF). Quoting Barrett and Silverman, SSH, the Secure Shell: The Definitive Guide, O'Reilly & Associates (2001). Dept. of Computer Science, Univ. of Virginia. Archived (PDF) from the original on 2025-08-05. Retrieved 2025-08-05.
  18. ^ IETF (Internet Engineering Task Force): datatracker for secsh
  19. ^ a b RFC4252: The Secure Shell (SSH) Authentication Protocol, Jan 2006
  20. ^ O'Reily: Secure Shell, The Definitive Guide
  21. ^ RFC4250: The Secure Shell (SSH) Protocol: Assigned names, Jan 2006, page 16
  22. ^ "SSH Frequently Asked Questions". Archived from the original on 2025-08-05.
  23. ^ "libssh".
  24. ^ "A GNU implementation of the Secure Shell protocols". Archived from the original on 2025-08-05.
  25. ^ "Dropbear SSH". Archived from the original on 2025-08-05.
  26. ^ Ylonen, T.; Lonvick, C. "Old Client, New Server". The Secure Shell (SSH) Transport Layer Protocol. IETF. sec. 5.1. doi:10.17487/RFC4253. RFC 4253.
  27. ^ ssh-1.2.13 now available: copying policy changed (permission now required to sell ssh commercially, use is still permitted for any purpose)
  28. ^ OSSH sources
  29. ^ "OpenSSH: Project History and Credits". openssh.com. 2025-08-05. Archived from the original on 2025-08-05. Retrieved 2025-08-05.
  30. ^ "OSSH Information for VU#419241". CERT Coordination Center. 2025-08-05. Archived from the original on 2025-08-05. Either way ossh is old and obsolete and I don't recommend its use.
  31. ^ "Remote terminal over HTTP/3 connections". datatracker.ietf.org. 2025-08-05.
  32. ^ "Secure shell over HTTP/3 connections". www.ietf.org. 2025-08-05.
  33. ^ Michel, Fran?ois; Bonaventure, Olivier (2025-08-05). "Towards SSH3: how HTTP/3 improves secure shells". arXiv:2312.08396 [cs.NI].
  34. ^ "ssh3". github.com. 2025-08-05.
  35. ^ "Secure shell over HTTP/3 connections". datatracker.ietf.org. 2025-08-05.
  36. ^ Sobell, Mark (2012). A Practical Guide to Linux Commands, Editors, and Shell Programming (3rd ed.). Upper Saddle River, NJ: Prentice Hall. pp. 702–704. ISBN 978-0133085044.
  37. ^ Harris, B.; Velvindron, L. (February 2020). Ed25519 and Ed448 Public Key Algorithms for the Secure Shell (SSH) Protocol. doi:10.17487/RFC8709. RFC 8709.
  38. ^ a b Stebila, D.; Green, J. (December 2009). Elliptic Curve Algorithm Integration in the Secure Shell Transport Layer. doi:10.17487/RFC5656. RFC 5656. Retrieved 12 November 2012.
  39. ^ Miller, D.; Valchev, P. (September 3, 2007). The use of UMAC in the SSH Transport Layer Protocol. I-D draft-miller-secsh-umac-00.
  40. ^ Ylonen, T.; Lonvick, C. The Secure Shell (SSH) Transport Layer Protocol. IETF. doi:10.17487/RFC4253. RFC 4253.
  41. ^ Igoe, K.; Solinas, J. (August 2009). AES Galois Counter Mode for the Secure Shell Transport Layer Protocol. doi:10.17487/RFC5647. RFC 5647.
  42. ^ "SSH Insertion Attack". Core Security Technologies. Archived from the original on 2025-08-05.
  43. ^ "Vulnerability Note VU#13877 - Weak CRC allows packet injection into SSH sessions encrypted with block ciphers". US CERT. Archived from the original on 2025-08-05.
  44. ^ "SSH CRC-32 Compensation Attack Detector Vulnerability". SecurityFocus. Archived from the original on 2025-08-05.
  45. ^ "Vulnerability Note VU#945216 - SSH CRC32 attack detection code contains remote integer overflow". US CERT. Archived from the original on 2025-08-05.
  46. ^ "Vulnerability Note VU#315308 - Weak CRC allows last block of IDEA-encrypted SSH packet to be changed without notice". US CERT. Archived from the original on 2025-08-05.
  47. ^ a b "Vulnerability Note VU#684820 - SSH-1 allows client authentication to be forwarded by a malicious server to another server". US CERT. Archived from the original on 2025-08-05.
  48. ^ "How to use SSH keys for authentication". Up Cloud. 17 September 2015. Retrieved 29 November 2019.
  49. ^ a b "Vulnerability Note VU#958563 - SSH CBC vulnerability". US CERT. Archived from the original on 2025-08-05.
  50. ^ "Prying Eyes: Inside the NSA's War on Internet Security". Spiegel Online. December 28, 2014. Archived from the original on January 24, 2015.
  51. ^ Ylonen, Tatu (3 August 2017). "BothanSpy & Gyrfalcon - Analysis of CIA hacking tools for SSH". ssh.com. Retrieved 15 July 2018.
  52. ^ "Terrapin Attack". terrapin-attack.com. Retrieved 2025-08-05.
  53. ^ Jones, Connor. "SSH shaken, not stirred by Terrapin downgrade vulnerability". www.theregister.com. Retrieved 2025-08-05.
  54. ^ Jones, Connor. "SSH shaken, not stirred by Terrapin downgrade vulnerability". www.theregister.com. Retrieved 2025-08-05.
  55. ^ a b "OpenSSH 9.6 release notes". openssh.com. 2025-08-05.

Further reading

[edit]
[edit]
调经吃什么药效果最好 百合有什么功效 以示是什么意思 五脏六腑是指什么 藿香正气胶囊治什么病
所剩无几是什么意思 伤口不愈合用什么药 小叶增生吃什么药好 猥琐什么意思 维生素b12是什么
柿子什么季节成熟 诙谐幽默是什么意思 血压高查什么项目 医者仁心什么意思 脂肪肝吃什么药效果好
耳鸣和脑鸣有什么区别 感冒为什么会打喷嚏 宫腔镜检查主要查什么 一花一草一世界的下一句是什么 传奇是什么意思
吃什么长胎快hcv8jop7ns4r.cn 类风湿性关节炎吃什么药hcv7jop6ns9r.cn 什么人不能吃西洋参hcv8jop1ns0r.cn 骑马标志是什么牌子hcv8jop2ns4r.cn 太阳代表什么数字naasee.com
更年期有什么症状hcv9jop6ns4r.cn 血小板低会引发什么病hcv9jop4ns1r.cn 什么是可支配收入hcv7jop5ns3r.cn 吃什么提高免疫力最快baiqunet.com 例假少吃什么能让量多hcv7jop6ns3r.cn
为什么暑假比寒假长hcv9jop6ns5r.cn 试管婴儿什么价格hcv7jop6ns3r.cn 脾胃虚寒吃什么食物好hcv7jop6ns8r.cn 关节炎吃什么药hcv9jop3ns2r.cn 鲁迅是什么样的人hcv9jop7ns4r.cn
长春都有什么大学imcecn.com 李逵的绰号是什么hcv8jop8ns4r.cn 象牙有什么作用与功效hcv7jop6ns0r.cn 刘邦是汉什么帝hcv8jop5ns3r.cn 月经期间不能吃什么水果hcv9jop1ns5r.cn
百度