Deprecating RC4 in Secure Shell (SSH)
RFC 8758
Yes
No Objection
Note: This ballot was opened for revision 16 and is now closed.
Roman Danyliw Yes
(1) Section 1. Per '[RFC4345] specifies and allocates the "arcfour-128" and "arcfour-256" ciphers for SSH', RFC4345 seems to call these allocations “arcfour128” and “arcfour256” (no hyphen). (2) Editorial -- Abstract. Editorial. s/Therefore, this document formally moves to Historic RFC4345/Therefore, this document formally moves to RFC4345 to Historic status/ -- Section 1. s/Historic/Historic status/ -- Section 2. s/The current document updates the status/This document updates the status/ -- Section 2. s/The current document updates [RFC4253] Section 6.3/This document updates [RFC4254 Section 6.3/ -- Section 2. Typo. s/weakenesses/weaknesses/
Warren Kumari (was Discuss) Yes
Thank you very much for writing this -- it's important, well written, etc. Also thanks to Fred for the OpsDir review.
Éric Vyncke (was No Objection) Yes
Alvaro Retana No Objection
(Adam Roach; former steering group member) Yes
(Alexey Melnikov; former steering group member) Yes
(Alissa Cooper; former steering group member) Yes
(Barry Leiba; former steering group member) Yes
Don’t forget to schedule a management item on the telechat for moving 4345 to Historic. (Never mind... I see the status-change doc now.)
(Benjamin Kaduk; former steering group member) Yes
(Ignas Bagdonas; former steering group member) Yes
(Deborah Brungard; former steering group member) No Objection
(Magnus Westerlund; former steering group member) No Objection
(Mirja Kühlewind; former steering group member) No Objection
(Suresh Krishnan; former steering group member) No Objection