RFC 8146 on Adding Support for Salted Password Databases to EAP-pwd

rfc-editor@rfc-editor.org Sat, 22 April 2017 00:00 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1BBD129564 for <ietf-announce@ietfa.amsl.com>; Fri, 21 Apr 2017 17:00:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pgB1hUMZwk4c for <ietf-announce@ietfa.amsl.com>; Fri, 21 Apr 2017 17:00:58 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EFD87127010 for <ietf-announce@ietf.org>; Fri, 21 Apr 2017 17:00:57 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C3E51B81C95; Fri, 21 Apr 2017 17:00:40 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8146 on Adding Support for Salted Password Databases to EAP-pwd
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Message-Id: <20170422000040.C3E51B81C95@rfc-editor.org>
Date: Fri, 21 Apr 2017 17:00:40 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/KV2hXE01Id8Str7iiPBysnrG8iU>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Apr 2017 00:01:00 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8146

        Title:      Adding Support for Salted Password 
                    Databases to EAP-pwd 
        Author:     D. Harkins
        Status:     Informational
        Stream:     IETF
        Date:       April 2017
        Mailbox:    dharkins@arubanetworks.com
        Pages:      11
        Characters: 22032
        Updates:    RFC 5931

        I-D Tag:    draft-harkins-salted-eap-pwd-08.txt

        URL:        https://www.rfc-editor.org/info/rfc8146

        DOI:        10.17487/RFC8146

EAP-pwd is an Extensible Authentication Protocol (EAP) method that
utilizes a shared password for authentication using a technique that
is resistant to dictionary attacks.  It includes support for raw keys
and double hashing of a password in the style of Microsoft Challenge
Handshake Authentication Protocol version 2 (MSCHAPv2), but it does
not include support for salted passwords.  There are many existing
databases of salted passwords, and it is desirable to allow their use
with EAP-pwd.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC