Re: Is getpass(3) really obsolete?
- From
- Alejandro Colomar (man-pages) <alx.manpages@gmail.com>
- Date
- Oct 29, 2021, 12:11 UTC
- Message-ID
- <865e5899-b991-918d-8bc6-ced65a67a566@gmail.com>
- In-Reply-To
- <211029.86r1c43uwj.gmgdl@evledraar.gmail.com>
Hi Ævar,
On 10/29/21 13:40, Ævar Arnfjörð Bjarmason wrote:
Show 7 quoted lines
> > On Fri, Oct 29 2021, Alejandro Colomar (man-pages) wrote: > >> [Add a few CCs, since I mentioned them.] > > [I'm not sure what the full context of this thread is, but just replying > from the POV of git@ being CC'd on this]
The first message on this thread was mine from '10/29/21 13:15', so you've read it all.
The broader context is that I was trying to make the deprecation notices more consistent in the Linux manpages, by using the [[deprecated]] attribute where appropriate. While doing that, I found a few cases where the deprecation/obsoletion is not so clear to me, such as this one ([as]ctime[_r](3) is another one, since it is deprecated by POSIX, but not by the C standard, but I'll start a different thread with that; and isascii(3) is another one, since the user of it should know if the character set he's using is compatible with ascii, and in that case it's perfectly valid, it's only a case of garbage in garbage out, IMO).
Show 11 quoted lines
> >> 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
[...]
Cheers,
Alex
-- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/