Bug#924712: crypt() not available _XOPEN_SOURCE is defined

[Francesco Poli]

On Sat, 31 Aug 2019 15:04:06 +0200 Aurelien Jarno wrote:

> On 2019-08-25 15:51, Francesco Poli wrote:
> > On Sun, 25 Aug 2019 13:46:36 +0200 Florian Weimer wrote:
> > 
> > > * Francesco Poli:
> > > 
> > > > Hello everyone,
> > > > I am sorry to ask, but... I cannot understand what's the status of
> > > > [this bug report].
> > > >
> > > > [this bug report]: 
> > > >
> > > > A serious bug for libc6-dev without any apparent activity since last
> > > > March?  Sure there must have been some hidden progress that I cannot
> > > > see.
> > > 
> > > We provided a solution acceptable to the reporter.  I do not think
> > > further action is needed on the glibc side.  The manual page needs to
> > > be updated to reflect the change, but that's not part of glibc.
> > 
> > OK, good.
> > Thanks for your prompt reply!
> > 
> > Why is the bug report being kept open, though?
> > Should it be reassigned to package manpages-dev and fixed there?
> 
> manpages-dev doesn't provide the manpage for crypt(3) anymore.

Oops, I hadn't noticed that.
Thanks a lot for clarifying!

> It is now
> provided by libcrypt2-dev. The crypt functions are getting removed from
> the glibc and will be provided by this external library. I guess we'll
> do the transition after getting glibc 2.29 into unstable.
> 
> As the version provided by libcrypt2-dev doesn't have the reported
> issue, I am closing the bug.

Good, thanks for stepping in!

Bye.


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpJJ4HF3VsfR.pgp
Description: PGP signature

Bug#924712: crypt() not available _XOPEN_SOURCE is defined

[Francesco Poli]

On Sun, 25 Aug 2019 15:51:21 +0200 Francesco Poli wrote:

> On Sun, 25 Aug 2019 13:46:36 +0200 Florian Weimer wrote:
[...]
> > We provided a solution acceptable to the reporter.  I do not think
> > further action is needed on the glibc side.  The manual page needs to
> > be updated to reflect the change, but that's not part of glibc.
> 
> OK, good.
> Thanks for your prompt reply!
> 
> Why is the bug report being kept open, though?
> Should it be reassigned to package manpages-dev and fixed there?

If you do not object (by the end of August), I can reassign the bug
report to package manpages-dev.



-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpx9QUCGCKSs.pgp
Description: PGP signature

Bug#924712: crypt() not available _XOPEN_SOURCE is defined

[Francesco Poli]

On Sun, 25 Aug 2019 13:46:36 +0200 Florian Weimer wrote:

> * Francesco Poli:
> 
> > Hello everyone,
> > I am sorry to ask, but... I cannot understand what's the status of
> > [this bug report].
> >
> > [this bug report]: 
> >
> > A serious bug for libc6-dev without any apparent activity since last
> > March?  Sure there must have been some hidden progress that I cannot
> > see.
> 
> We provided a solution acceptable to the reporter.  I do not think
> further action is needed on the glibc side.  The manual page needs to
> be updated to reflect the change, but that's not part of glibc.

OK, good.
Thanks for your prompt reply!

Why is the bug report being kept open, though?
Should it be reassigned to package manpages-dev and fixed there?


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpy9wsedCAEs.pgp
Description: PGP signature

Bug#924712: crypt() not available _XOPEN_SOURCE is defined

[Florian Weimer]

* Francesco Poli:

> Hello everyone,
> I am sorry to ask, but... I cannot understand what's the status of
> [this bug report].
>
> [this bug report]: 
>
> A serious bug for libc6-dev without any apparent activity since last
> March?  Sure there must have been some hidden progress that I cannot
> see.

We provided a solution acceptable to the reporter.  I do not think
further action is needed on the glibc side.  The manual page needs to
be updated to reflect the change, but that's not part of glibc.

Bug#924712: crypt() not available _XOPEN_SOURCE is defined

[Francesco Poli]

Hello everyone,
I am sorry to ask, but... I cannot understand what's the status of
[this bug report].

[this bug report]: 

A serious bug for libc6-dev without any apparent activity since last
March?
Sure there must have been some hidden progress that I cannot see.


I probably do not fully understand the issue: there seems to be a
transition going on, from some deprecated crypt() implementation to
libxcrypt. And this transition requires some small changes (basically
different #include and #define directives) in C code using crypt(),
if this code has to be recompiled on buster or later.
But these different requirements are not yet documented in the
appropriate [man page].

[man page]: 

Is this a decent summary of the situation?

If this is the case, should this bug report be reassigned to package
manpages-dev and fixed there?


Please clarify, thanks for your time and patience!   :-)

-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgp5MDikA5Vhd.pgp
Description: PGP signature

Bug#924712: crypt() not available _XOPEN_SOURCE is defined

[Laurent Bigonville]

Le 21/03/19 à 09:32, Florian Weimer a écrit :

* Laurent Bigonville:


Le 19/03/19 à 19:43, Florian Weimer a écrit :

Can you compile the software using _DEFAULT_SOURCE (well, the default)
or _GNU_SOURCE instead?

Yes, the software can be compile when _XOPEN_SOURCE is not defined or
when _GNU_SOURCE is defined instead

Sorry, what I was trying to ask is whether this would be an acceptable
change for you.
Ah. For the specific case I ran across, yes. But I don't know if that 
change breaks other projects

Bug#924712: crypt() not available _XOPEN_SOURCE is defined

[Florian Weimer]

* Laurent Bigonville:

> Le 19/03/19 à 19:43, Florian Weimer a écrit :
>> * Laurent Bigonville:
>>
>>> Package: libc6-dev
>>> Version: 2.28-8
>>> Severity: serious
>>>
>>> Hi,
>>>
>>> The crypt.3 manpage, state that _XOPEN_SOURCE should be define for
>>> crypt() to be available.
>>>
>>> But it looks that it's currently the opposite, if _XOPEN_SOURCE is
>>> defined, the function cannot be found.

>> Can you compile the software using _DEFAULT_SOURCE (well, the default)
>> or _GNU_SOURCE instead?
>
> Yes, the software can be compile when _XOPEN_SOURCE is not defined or 
> when _GNU_SOURCE is defined instead

Sorry, what I was trying to ask is whether this would be an acceptable
change for you.

Bug#924712: crypt() not available _XOPEN_SOURCE is defined

[Laurent Bigonville]

Le 19/03/19 à 19:43, Florian Weimer a écrit :

* Laurent Bigonville:


Package: libc6-dev
Version: 2.28-8
Severity: serious

Hi,

The crypt.3 manpage, state that _XOPEN_SOURCE should be define for
crypt() to be available.

But it looks that it's currently the opposite, if _XOPEN_SOURCE is
defined, the function cannot be found.

Can you compile the software using _DEFAULT_SOURCE (well, the default)
or _GNU_SOURCE instead?


Yes, the software can be compile when _XOPEN_SOURCE is not defined or 
when _GNU_SOURCE is defined instead



We do not want to provide the CRYPT extension anymore because it
implies not just support for the crypt function, but also for the DES
encryption functions, which definitely do not want.  In _XOPEN_SOURCE
mode, it's either all of these functions or none of them (and we chose
the latter because of DES), otherwise glibc wouldn't conform to the
interface specification.

We definitely should update the manual page, though.

Bug#924712: crypt() not available _XOPEN_SOURCE is defined

[Florian Weimer]

* Laurent Bigonville:

> Package: libc6-dev
> Version: 2.28-8
> Severity: serious
>
> Hi,
>
> The crypt.3 manpage, state that _XOPEN_SOURCE should be define for
> crypt() to be available.
>
> But it looks that it's currently the opposite, if _XOPEN_SOURCE is
> defined, the function cannot be found.

Can you compile the software using _DEFAULT_SOURCE (well, the default)
or _GNU_SOURCE instead?

We do not want to provide the CRYPT extension anymore because it
implies not just support for the crypt function, but also for the DES
encryption functions, which definitely do not want.  In _XOPEN_SOURCE
mode, it's either all of these functions or none of them (and we chose
the latter because of DES), otherwise glibc wouldn't conform to the
interface specification.

We definitely should update the manual page, though.

Bug#924712: crypt() not available _XOPEN_SOURCE is defined

[Laurent Bigonville]

FTR: https://bugzilla.redhat.com/show_bug.cgi?id=1566464

Bug#924712: crypt() not available _XOPEN_SOURCE is defined

[Laurent Bigonville]

Package: libc6-dev
Version: 2.28-8
Severity: serious

Hi,

The crypt.3 manpage, state that _XOPEN_SOURCE should be define for
crypt() to be available.

But it looks that it's currently the opposite, if _XOPEN_SOURCE is
defined, the function cannot be found.

This actually looks like a regression compared to stretch.

Regards,
Laurent Bigonville

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages manpages-dev depends on:
ii  manpages  4.16-1

manpages-dev recommends no packages.

Versions of packages manpages-dev suggests:
ii  man-db [man-browser]  2.8.5-2

-- no debconf information