FYI - new SSH Maintenance WG will meet at IETF 121 in Dublin first week of
November.
---------- Forwarded message ---------
From: Deb Cooley <debcooley1 at gmail.com>
Date: Fri, Sep 27, 2024, 6:37 AM
Subject: [Ssh] SSHM charter
To: <SSH at ietf.org>
Cc: <sshm-chairs at ietf.org>
All,
Below is the initial working group charter for SSHM. I look forward to
serving you as the Security Area Director. As you already know the working
group chairs are Stephen Farrell and Job Snijders. I'll see you in Dublin*!
Deb Cooley
The main goal of the working group is to maintain the Secure Shell (SSH)
protocol. SSH provides support for secure remote login, file transfer, and
forwarding UNIX-domain sockets, TCP/IP and X11. It can automatically
encrypt, authenticate, and compress transmitted data.
The SSHM working group facilitates discussion of clarifications,
improvements, and extensions to the SSH protocol.
The initial goals of this working group are:
-
to update the RFCs documenting SSH to reflect what is implemented and
deployed in practice. In particular, the working group will document the
OpenSSH certificate structure, the SSH agent protocol, and SFTP, as they
are currently implemented.
-
to update and maintain the list of cryptographic algorithms used by SSH.
This includes documenting currently deployed algorithms, deprecating unsafe
algorithms, selecting new algorithms, and determining the set of
recommended and mandatory-to-implement algorithms. Updating IANA SSH
registries and changing their registration policies is in scope.
While the development of formal verification proofs is out of scope, this
working group can respond to emerging proofs, and to security issues found
by formal verification tools. This can be done for example by defining new
extensions to improve the security of SSH.
This working group will strive for strong security, simplicity, and ease of
implementation. In particular, proposals will only be adopted if there is
evidence of significant existing deployment or broad interest in new
implementation and deployment. Protocol documents should not be submitted
to the IESG for publication before they have at least two demonstrably
interoperable implementations.
Out of scope includes:
- defining new certificate types or trust mechanisms;
- defining new transports for SSH;
- designing cryptographic algorithms (but defining how SSH uses
cryptographic algorithms is in scope).
*note: fee waivers for remote attendance are super easy to get. I
encourage those of you who would like to attend, but for whatever reason
find the fee and travel to be onerous, to attend remotely.
_______________________________________________
Ssh mailing list -- ssh at ietf.org
To unsubscribe send an email to ssh-leave at ietf.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20240927/269692a7/attachment.html>