summaryrefslogtreecommitdiff
path: root/PROTOCOL
diff options
context:
space:
mode:
authordjm@openbsd.org <djm@openbsd.org>2018-10-02 12:51:58 +0000
committerDamien Miller <djm@mindrot.org>2018-10-02 22:53:48 +1000
commita46ac4d86b25414d78b632e8173578b37e5f8a83 (patch)
tree17d930ead7b35a8bf8a30732f02163f423395ebb /PROTOCOL
parentff3a411cae0b484274b7900ef52ff4dad3e12876 (diff)
downloadopenssh-git-a46ac4d86b25414d78b632e8173578b37e5f8a83.tar.gz
upstream: mention INFO@openssh.com for sending SIGINFO
OpenBSD-Commit-ID: 132471eeb0df658210afd27852fe65131b26e900
Diffstat (limited to 'PROTOCOL')
-rw-r--r--PROTOCOL9
1 files changed, 8 insertions, 1 deletions
diff --git a/PROTOCOL b/PROTOCOL
index 010bec92..f75c1c0a 100644
--- a/PROTOCOL
+++ b/PROTOCOL
@@ -334,6 +334,13 @@ a server may offer multiple keys of the same type for a period (to
give clients an opportunity to learn them using this extension) before
removing the deprecated key from those offered.
+2.6. connection: SIGINFO support for "signal" channel request
+
+The SSH channels protocol (RFC4254 section 6.9) supports sending a
+signal to a session attached to a channel. OpenSSH supports one
+extension signal "INFO@openssh.com" that allows sending SIGINFO on
+BSD-derived systems.
+
3. SFTP protocol changes
3.1. sftp: Reversal of arguments to SSH_FXP_SYMLINK
@@ -489,4 +496,4 @@ OpenSSH's connection multiplexing uses messages as described in
PROTOCOL.mux over a Unix domain socket for communications between a
master instance and later clients.
-$OpenBSD: PROTOCOL,v 1.35 2018/08/10 00:44:01 djm Exp $
+$OpenBSD: PROTOCOL,v 1.36 2018/10/02 12:51:58 djm Exp $