On 03/31/2018 11:52 AM, Björn 'besser82' Esser wrote:
Am Dienstag, den 13.03.2018, 10:11 +0100 schrieb Nikos
Mavrogiannopoulos:
On Wed, 2017-11-08 at 18:08 +0100, Björn 'besser82' Esser wrote:
Anyways, before this can happen, there is still some work to be done
with libxcrypt, like adding a
Am Dienstag, den 13.03.2018, 10:11 +0100 schrieb Nikos
Mavrogiannopoulos:
> On Wed, 2017-11-08 at 18:08 +0100, Björn 'besser82' Esser wrote:
> > Hello everyone,
> >
> > since there has been some discussion in the last time about removing
> > libcrypt from glibc in some time [1,2,3,4] and
On Wed, 2017-11-08 at 18:08 +0100, Björn 'besser82' Esser wrote:
> Hello everyone,
>
> since there has been some discussion in the last time about removing
> libcrypt from glibc in some time [1,2,3,4] and splitting it out into
> a
> separate project which can evolve quicker, I'd like to hear your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2017-11-10 at 14:39 +0100, Florian Weimer wrote:
> On 11/08/2017 06:08 PM, Björn 'besser82' Esser wrote:
> > Hello everyone,
> >
> > since there has been some discussion in the last time about
> > removing
> > libcrypt from glibc in some
On 11/10/2017 02:21 PM, Kevin Kofler wrote:
Björn 'besser82' Esser wrote:
libxcrypt will be fully binary compatible with software linked against
glibc's libcrypt and does not require any rebuilds. However, the
converse is not true: programs linked against libxcrypt will not work
with glibc's
On 11/09/2017 02:26 AM, Yaakov Selkowitz wrote:
On 2017-11-08 11:08, Björn 'besser82' Esser wrote:
since there has been some discussion in the last time about removing
libcrypt from glibc in some time [1,2,3,4] and splitting it out into a
separate project which can evolve quicker, I'd like to
On 11/08/2017 06:08 PM, Björn 'besser82' Esser wrote:
Hello everyone,
since there has been some discussion in the last time about removing
libcrypt from glibc in some time [1,2,3,4] and splitting it out into a
separate project which can evolve quicker, I'd like to hear your
oppinion about
Björn 'besser82' Esser wrote:
> libxcrypt will be fully binary compatible with software linked against
> glibc's libcrypt and does not require any rebuilds. However, the
> converse is not true: programs linked against libxcrypt will not work
> with glibc's libcrypt. It comes with a set of
On 2017-11-08 11:08, Björn 'besser82' Esser wrote:
> since there has been some discussion in the last time about removing
> libcrypt from glibc in some time [1,2,3,4] and splitting it out into a
> separate project which can evolve quicker, I'd like to hear your
> oppinion about replacing glibc's
I forgot to mention: There's already a COPR [1] for sneak-peak testing
of the current pre-release libxcrypt.
[1] https://copr.fedorainfracloud.org/coprs/besser82/libxcrypt/
signature.asc
Description: This is a digitally signed message part
___
Hello everyone,
since there has been some discussion in the last time about removing
libcrypt from glibc in some time [1,2,3,4] and splitting it out into a
separate project which can evolve quicker, I'd like to hear your
oppinion about replacing glibc's libcrypt with libxcrypt [5] for Fedora
29
11 matches
Mail list logo
