From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-x336.google.com (mail-wm1-x336.google.com [IPv6:2a00:1450:4864:20::336]) by sourceware.org (Postfix) with ESMTPS id AA99D3858C39 for ; Fri, 29 Oct 2021 11:28:58 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org AA99D3858C39 Received: by mail-wm1-x336.google.com with SMTP id a20-20020a1c7f14000000b003231d13ee3cso12254809wmd.3 for ; Fri, 29 Oct 2021 04:28:58 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:from:to:references:cc:in-reply-to :content-transfer-encoding; bh=3OtKDZH6u6meon+NIAzXtkJKHzFLB40f75M3A4SVnoQ=; b=Yq+ihnsT67R3YZpQIyOZsjyZIBAg/ZzMHn4uKxnuoONb7+vcvZVh7aw19HYJEwazQI XFxb2GPmzMq/ey+gr/sOCbsGC8t6pBow296dpPQOWJeodcg0JDo0SNP2uDw1iTeUsH57 niNYEGTY7sNcSvHOw5H6a+YlnK7JzmFU0p4Si7B+BDy0tiDiiG94RcmdJCcroPNh67JD ZocHfrT8u8wY6SDD2Rp5gKvQJn06OVnOPG4OJpW7Lc+TbB74dr6UD7NFTfsXHjjqQNFn bWBFCjOcpKPspXeajh0qrJlPrB3O524GVCU+YiulO48Uung5Eh+piIi2hfnZaAh6yBUt iXFw== X-Gm-Message-State: AOAM530UuXHOQK9g4I0V3P6TwVtlSU2pIvX+iAPZryi8V7eboV7TEEYi RC2csb8mbFcxb3hM7QTWHrhr17LPkMA= X-Google-Smtp-Source: ABdhPJyDPipSCgdKnazFNp9RAmjmx3v3lB1R0SKAnpklGZ3DKJr5RE1aP3ZcUAZGcruRp+oOBsMKnQ== X-Received: by 2002:a1c:3504:: with SMTP id c4mr7893077wma.160.1635506937856; Fri, 29 Oct 2021 04:28:57 -0700 (PDT) Received: from [10.168.10.11] ([170.253.36.171]) by smtp.gmail.com with ESMTPSA id p1sm8743041wmq.23.2021.10.29.04.28.57 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 29 Oct 2021 04:28:57 -0700 (PDT) Message-ID: <73ac38a2-c287-4cc1-4e9c-0f9766ac4c0c@gmail.com> Date: Fri, 29 Oct 2021 13:28:56 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.2.1 Subject: Re: Is getpass(3) really obsolete? Content-Language: en-US From: "Alejandro Colomar (man-pages)" To: Libc-alpha , linux-man References: Cc: git@vger.kernel.org, "tech@openbsd.org" In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-7.0 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, NICE_REPLY_A, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Oct 2021 11:29:00 -0000 [Add a few CCs, since I mentioned them.] On 10/29/21 13:15, Alejandro Colomar wrote: > Hi, > > As the manual pages says, SUSv2 marked it as LEGACY, and POSIX doesn't > have it at all.  The manual page goes further and says "This function is > obsolete. Do not use it." in its first lines. > > But, glibc doesn't seem to have deprecated this function at all.  And it > seems to be the most portable way to get a password, even if it's not in > POSIX. > > BSDs have readpassphrase(3), but glibc doesn't, so unless you recommend OpenBSD also marks getpass(3) as obsolete and recommends readpassphrase(3): > using readpassphrase(3) from libbsd, or plan to add it to glibc, I think > getpass(3) should be the recommended function in Linux, and therefore we > should remove the hard words against it. > > As a real example, git(1) uses getpass(3). > > > What are your thoughts? > > Thanks, > > Alex > > -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/