Re: Is getpass(3) really obsolete?

On Sat, 30 Oct 2021, Alejandro Colomar (man-pages) via Libc-alpha wrote: > > See the discussion of deprecation starting with > > (C2X > > has also deprecated those functions). The comments in that thread > > supported marking the

Re: Is getpass(3) really obsolete?

Hi Joseph, On 10/29/21 18:31, Joseph Myers wrote: On Fri, 29 Oct 2021, Alejandro Colomar (man-pages) via Libc-alpha wrote: 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.

Re: Is getpass(3) really obsolete?

On Fri, 29 Oct 2021, Alejandro Colomar (man-pages) via Libc-alpha wrote: > 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

Re: Is getpass(3) really obsolete?

On October 29, 2021 10:45 AM, Alejandro Colomar wrote: > On 10/29/21 16:33, rsbec...@nexbridge.com wrote: > > October 29, 2031 10:21 AM, Theo de Raadt will write: > >> wrote: > >> > > getpass() is obsolete in POSIX.2. However, some platforms still > > are on > >>> POSIX.1, > so

Re: Is getpass(3) really obsolete?

On Fri, Oct 29, 2021, at 9:55 AM, Theo de Raadt wrote: > wrote: >> On October 29, 2021 7:29 AM, Alejandro Colomar wrote: >> > 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

Re: Is getpass(3) really obsolete?

Hi Randall, Theo, On 10/29/21 16:33, rsbec...@nexbridge.com wrote: October 29, 2031 10:21 AM, Theo de Raadt will write: wrote: getpass() is obsolete in POSIX.2. However, some platforms still are on POSIX.1, so replacing it instead of providing a configure detection/switch for it might

Re: Is getpass(3) really obsolete?

On October 29, 2021 9:56 AM, Theo de Raadt wrote: > Subject: Re: Is getpass(3) really obsolete? > wrote: > > > On October 29, 2021 7:29 AM, Alejandro Colomar wrote: > > > On 10/29/21 13:15, Alejandro Colomar wrote: > > > > Hi, > > > > > > &

Re: Is getpass(3) really obsolete?

wrote: > > > getpass() is obsolete in POSIX.2. However, some platforms still are on > POSIX.1, > > so replacing it instead of providing a configure detection/switch for it > might > > cause issues. > > > > > > The community finally had the balls to get rid of gets(3). > > > > getpass(3)

Re: Is getpass(3) really obsolete?

On Fri, Oct 29, 2021 at 2:40 PM wrote: > getpass() is obsolete in POSIX.2. However, some platforms still are on > POSIX.1, so replacing it instead of providing a configure detection/switch > for it might cause issues. POSIX.2 is not a newer POSIX version, but rather a book (“Shell and

Re: Is getpass(3) really obsolete?

wrote: > On October 29, 2021 7:29 AM, Alejandro Colomar wrote: > > 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

Re: Is getpass(3) really obsolete?

On October 29, 2021 7:29 AM, Alejandro Colomar wrote: > 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

Re: Is getpass(3) really obsolete?

Hi Ævar, On 10/29/21 13:40, Ævar Arnfjörð Bjarmason wrote: 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

Re: Is getpass(3) really obsolete?

[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