[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#855448: marked as done (unblock: encfs/1.9.1-4)

Your message dated Sat, 18 Feb 2017 12:49:00 +0000
with message-id <1ffcc79f-674d-173d-54a4-762e84f8afc0@thykier.net>
and subject line Re: Bug#855448: unblock: encfs/1.9.1-4
has caused the Debian Bug report #855448,
regarding unblock: encfs/1.9.1-4
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
855448: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855448
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
User: release.debian.org@packages.debian.org
Usertags: unblock
Severity: normal

Please unblock the package encfs. The testing version contains a change
that might trigger a security flaw, i.e. it changes the visible behavior
in a way not expected by "optimistically" written frontend programs,
leading to possibly incorrect input of wrong (identical) password, which
again might be not properly detected by badly written frontends either.

The new upstream patch reverts this and ensures a clean program exit on
such failure.

See #853916 for details.

Regards,
Eduard.

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- 
Eduard Bloch:
> Package: release.debian.org
> User: release.debian.org@packages.debian.org
> Usertags: unblock
> Severity: normal
> 
> Please unblock the package encfs. The testing version contains a change
> that might trigger a security flaw, i.e. it changes the visible behavior
> in a way not expected by "optimistically" written frontend programs,
> leading to possibly incorrect input of wrong (identical) password, which
> again might be not properly detected by badly written frontends either.
> 
> The new upstream patch reverts this and ensures a clean program exit on
> such failure.
> 
> See #853916 for details.
> 
> Regards,
> Eduard.
> 

Unblocked, thanks.

~Niels

--- End Message ---
Reply to: