On Tue, Jan 31, 2017 at 05:17:44PM +0100, Francesco Namuri wrote:
of course we can remove it only from the upcoming stable release,
and removing it from testing already done it. ftpmaster also removed
it from unstable.
We asked also the removal from unstable due the gravity of the bug.
I'd like to point that the problem only affects encrypted directories
made using cryptkeeper, and that the problems it's easily discovered
first time the user tries to mount the partition.
Yes, I agree that it's easily discoverable--which is why I'm concerned
that simply removing the entire functionality of the package without any kind
of notification to the user isn't the best way to address the problem.
Again: removing the package simply ensures that people upgrading to
stretch will either end up with a cryptkeeper package that exhibits this
bug, or will remove their cryptkeeper package and not know how to access
their stored data, right?
Mike Stone
