On 2019-02-20 23:09:11 [+0100], Moritz Mühlenhoff wrote: > On Wed, Feb 20, 2019 at 08:51:16AM +0100, Moritz Muehlenhoff wrote: > > On Wed, Feb 20, 2019 at 12:28:48AM +0100, Sebastian Andrzej Siewior wrote: > > > On 2017-10-12 23:44:37 [+0200], To 859...@bugs.debian.org wrote: > > > > this is a remainder about the openssl transition [0]. We really want to > > > > remove libssl1.0-dev from unstable for Buster. I will raise the severity > > > > of this bug to serious in a month. Please react before that happens. > > > > > > There has been no action on pidentd and it is out of testing during > > > soft-freeze. Should there be a RM bug filled? We do have alternative > > > ident daemons in the archive. This package is holding back the removal > > > of openssl 1.0.2 in the archive. > > > > Or alternatively we can simply drop the idecrypt binary package, and remove > > --with-des* from the configure (and the build dep). I doubt anyone really > > uses the DES feature of ident... > > Like the attached patch.
No, I don't think it makes sense. If I understand it correctly the DES part is used to hide the real user but the admin should still be able to decrypt/find out who was the orignal user. Therefore I would suggest to either RM this and switch over to oidentd with the spoof reply (and lookup in the user in the logfile) or fix this package and upload it. Its popcon is dropping. It will not be part of Buster. So either RM it or (if you decide against it) I can NMU it with fixed DES support. There is a patch in this bug report and it looks straight forward. > Cheers, > Moritz Sebastian
