|author||Damien Miller <email@example.com>||2013-01-09 16:12:19 +1100|
|committer||Damien Miller <firstname.lastname@example.org>||2013-01-09 16:12:19 +1100|
- email@example.com 2013/01/08 18:49:04
[PROTOCOL authfile.c cipher.c cipher.h kex.c kex.h monitor_wrap.c] [myproposal.h packet.c ssh_config.5 sshd_config.5] support AES-GCM as defined in RFC 5647 (but with simpler KEX handling) ok and feedback djm@
Diffstat (limited to 'PROTOCOL')
1 files changed, 13 insertions, 1 deletions
@@ -79,6 +79,18 @@ contains:
byte[n1] payload; n1 = packet_length - padding_length - 1
byte[n2] random padding; n2 = padding_length
+1.6 transport: AES-GCM
+OpenSSH supports the AES-GCM algorithm as specified in RFC 5647.
+Because of problems with the specification of the key exchange
+the behaviour of OpenSSH differs from the RFC as follows:
+AES-GCM is only negotiated as the cipher algorithms
+"firstname.lastname@example.org" or "email@example.com" and never as
+an MAC algorithm. Additionally, if AES-GCM is selected as the cipher
+the exchanged MAC algorithms are ignored and there doesn't have to be
+a matching MAC.
2. Connection protocol changes
2.1. connection: Channel write close extension "firstname.lastname@example.org"
@@ -319,4 +331,4 @@ link(oldpath, newpath) and will respond with a SSH_FXP_STATUS message.
This extension is advertised in the SSH_FXP_VERSION hello with version
-$OpenBSD: PROTOCOL,v 1.19 2013/01/03 12:49:01 djm Exp $
+$OpenBSD: PROTOCOL,v 1.20 2013/01/08 18:49:04 markus Exp $