Secure Shell (secsh)

NOTE: This charter is a snapshot of that in effect at the time of the 38th IETF Meeting in Memphis,Tennessee. It may now be out-of-date.

Chair(s): 

Perry Metzger <perry@piermont.com>

Security Area Director(s): 

Jeffrey Schiller <jis@mit.edu>

Mailing Lists: 

General Discussion:ietf-ssh@clinet.fi
To Subscribe: majordomo@clinet.fi
In Body: subscribe ietf-ssh@clinet.fi in body
Archive:

Description of Working Group: 

The goal of the working group is to update and standardize the popular SSH protocol. SSH provides support for secure remote login, secure file transfer, and secure TCP/IP and X11 forwardings. It can automatically encrypt, authenticate, and compress transmitted data. The working group will attempt to assure that the SSH protocol: 

·   Provides strong security against cryptanalysis and protocol attacks, 
·   Can work reasonably well without a global key management or certificate infrastructure, 
·   Can utilize existing certificate infrastructures (e.g., DNSSEC, SPKI, X.509) when available, 
·   Can be made easy to deploy and take into use, 
·   Requires minimum or no manual interaction from users, 
·   Is reasonably clean and simple to implement.

The resulting protocol will operate over TCP/IP or other reliable but insecure transport. It is intended to be implemented at the application level.

Goals and Milestones:

Feb 97 

Submit Internet-Draft on SSH-2.0 protocol

Apr 97 

Decide on Transport Layer protocol at Memphis IETF.

Aug 97 

Finalize upper level protocols at Munich IETF.

Sep 97 

Submit Internet-Drafts to IESG to consider for publication as RFCs.

Dec 97 

Meet at DC IETF meeting.
Internet-Drafts: 

· SSH Transport Layer Protocol 

· SSH Authentication Protocol 

· Connect

No Request For Comments 

Current Meeting Report

None Received 

Slides

None Received 

Attendees List

TOC