IETF Logo Mail Archive

[Isms] Comments on draft-ietf-isms-secshell-07.txt

"David B. Nelson" <d.b.nelson@comcast.net> Wed, 27 June 2007 21:58 UTC

Return-path: <isms-bounces@lists.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I3fXH-000256-RD; Wed, 27 Jun 2007 17:58:51 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I3fXH-000250-4Q for isms@ietf.org; Wed, 27 Jun 2007 17:58:51 -0400
Received: from sccrmhc12.comcast.net ([63.240.77.82]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1I3fXG-0006Fy-VK for isms@ietf.org; Wed, 27 Jun 2007 17:58:51 -0400
Received: from newton603 (c-24-61-11-96.hsd1.nh.comcast.net[24.61.11.96]) by comcast.net (sccrmhc12) with SMTP id <20070627215818012003l3c5e>; Wed, 27 Jun 2007 21:58:18 +0000
From: "David B. Nelson" <d.b.nelson@comcast.net>
To: isms@ietf.org
Date: Wed, 27 Jun 2007 17:58:44 -0400
Message-ID: <00ff01c7b906$548ce290$6401a8c0@NEWTON603>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
Thread-Index: Ace5BlRFGq4GH77dR7qBCJYvxLKkMA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Cc:
Subject: [Isms] Comments on draft-ietf-isms-secshell-07.txt
X-BeenThere: isms@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mailing list for the ISMS working group <isms.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/isms>
List-Post: <mailto:isms@lists.ietf.org>
List-Help: <mailto:isms-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isms>, <mailto:isms-request@lists.ietf.org?subject=subscribe>
Errors-To: isms-bounces@lists.ietf.org

In section 3.1.3:   

   It is also possible to use a different
   password validation protocol such as CHAP [RFC1994] or digest
   authentication [RFC 2617, draft-ietf-radext-digest-auth-04] to
   integrate with RADIUS or Diameter.  These mechanisms leave the
   password in the clear on the device that is authenticating the
   password which introduces threats to the authentication
   infrastructure.

Note that draft-ietf-radext-digest-auth-04 has been published as RFC 4590.
This is currently under revision, to fix a couple or errors, as
draft-ietf-radext-rfc4590bis-01.txt.

In the second sentence I would recommend changing "leave" to "require".




_______________________________________________
Isms mailing list
Isms@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/isms

v2.23.0 | Report a Bug | By Email