From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16053 invoked by alias); 28 Jun 2018 16:01:33 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 16040 invoked by uid 89); 28 Jun 2018 16:01:32 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS,URIBL_RED autolearn=ham version=3.3.2 spammy= X-HELO: relay1.mentorg.com Date: Thu, 28 Jun 2018 16:01:00 -0000 From: Joseph Myers To: Florian Weimer CC: Subject: Re: [PATCH] Disallow use of DES encryption functions in new programs. In-Reply-To: <3a52c33f-32af-b30c-4a1e-19cf65be5aac@redhat.com> Message-ID: References: <20180625134328.642DC43994575@oldenburg.str.redhat.com> <3a52c33f-32af-b30c-4a1e-19cf65be5aac@redhat.com> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-SW-Source: 2018-06/txt/msg00903.txt.bz2 On Thu, 28 Jun 2018, Florian Weimer wrote: > Joseph, do you think the above changes are correct? Or was crypt a > non-optional part of any of the standards at one point? As far as I can tell it's always been in an optional CRYPT group. It's less clear whether in the absence of support for that group some standards might have expected the interfaces to be present as ENOSYS stubs. We don't have a well-defined way of handling optional feature groups in the conform/ tests (i.e. a way of saying "this is part of group X" and the tests verifying consistency with whether group X is declared to be supported). Sometimes we just list them in the expectations as required (if glibc supports that group), sometimes as optional-* (which is more or less equivalent to not listing them), sometimes don't list them at all. -- Joseph S. Myers joseph@codesourcery.com