Re: libsafe not in release ready state
Yes, I agree. I'll upgrade 233996 to make it release-critical, and
request that it be removed from Sarge; should probably have done that
long ago. (I'm the maintainer, but will gladly give it to anyone who
wants it.)
On 5/5/05, Moritz Muehlenhoff <jmm@inutil.org> wrote:
> Hi,
> I've had a look the libsafe package and I think it should be removed
> from Sarge:
>
> - It does not protect against at least two exploit classes (173227),
> it's not thread safe (305070) and given that the last upload was
> nearly two years ago there are probably some other uncovered areas
> as well. This renders the package's more or less useless and gives
> a false sense of security.
> - It has several problems with a modern toolchain (233996)
>
> In the 233996 buglog the maintainer confirms that it's useless nowadays.
>
> Cheers,
> Moritz
>
> --
> To UNSUBSCRIBE, email to debian-release-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
>
Reply to: