attachment
<div dir="auto">FYI - new SSH Maintenance WG will meet at IETF 121 in Dublin first week of November.<div dir="auto"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">---------- Forwarded message ---------<br>From: <strong class="gmail_sendername" dir="auto">Deb Cooley</strong> <span dir="auto"><<a href="mailto:debcooley1@gmail.com">debcooley1@gmail.com</a>></span><br>Date: Fri, Sep 27, 2024, 6:37 AM<br>Subject: [Ssh] SSHM charter<br>To: <<a href="mailto:SSH@ietf.org">SSH@ietf.org</a>><br>Cc: <<a href="mailto:sshm-chairs@ietf.org">sshm-chairs@ietf.org</a>><br></div><br><br><div dir="ltr">
<div>
<p>All,<br></p><p>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*!</p><p>Deb Cooley</p><p><br></p><p><br></p><p>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.</p>
<p>The SSHM working group facilitates discussion of clarifications, improvements, and extensions to the SSH protocol.</p>
<p>The initial goals of this working group are:</p>
<ul><li>
<p>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.</p>
</li><li>
<p>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.</p>
</li></ul>
<p>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.</p>
<p>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.</p>
<p>Out of scope includes:</p>
<ul><li>defining new certificate types or trust mechanisms;</li><li>defining new transports for SSH;</li><li>designing cryptographic algorithms (but defining how SSH uses cryptographic algorithms is in scope).</li></ul><div><br></div><div><br></div><div><br></div><div><br></div><div>*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.<br></div>
</div>
</div>
_______________________________________________<br>
Ssh mailing list -- <a href="mailto:ssh@ietf.org" target="_blank" rel="noreferrer">ssh@ietf.org</a><br>
To unsubscribe send an email to <a href="mailto:ssh-leave@ietf.org" target="_blank" rel="noreferrer">ssh-leave@ietf.org</a><br>
</div>