GNU bug report logs - #20030
plstore caches invalid passphrases

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Jonas Bernoulli <jonas <at> bernoul.li>
Subject: bug#20030: closed (Re: bug#20030: plstore caches invalid passphrases)
Date: Tue, 31 Mar 2015 01:18:02 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#20030: plstore caches invalid passphrases

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 20030 <at> debbugs.gnu.org.

-- 
20030: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=20030
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Daiki Ueno <ueno <at> gnu.org>
To: Jonas Bernoulli <jonas <at> bernoul.li>
Cc: 20030-done <at> debbugs.gnu.org
Subject: Re: bug#20030: plstore caches invalid passphrases
Date: Tue, 31 Mar 2015 10:17:49 +0900

Jonas Bernoulli <jonas <at> bernoul.li> writes:

> When using symmetric encryption and
> `plstore-cache-passphrase-for-symmetric-encryption' is non-nil,
> `plstore-passphrase-callback-function' stores the passphrase entered
> by the user in `plstore-passphrase-alist'.  This happens *before* the
> passphrase is used to decrypt, and if it turns out that it was wrong,
> then it is *not* removed from the cache.

Thanks, good catch.  I've installed a fix:
http://git.savannah.gnu.org/cgit/emacs.git/commit/?id=2e4b0c98

[Message part 3 (message/rfc822, inline)]

From: Jonas Bernoulli <jonas <at> bernoul.li>
To: <bug-gnu-emacs <at> gnu.org>
Subject: plstore caches invalid passphrases
Date: Sat, 07 Mar 2015 15:11:36 +0100

When using symmetric encryption and
`plstore-cache-passphrase-for-symmetric-encryption' is non-nil,
`plstore-passphrase-callback-function' stores the passphrase entered
by the user in `plstore-passphrase-alist'.  This happens *before* the
passphrase is used to decrypt, and if it turns out that it was wrong,
then it is *not* removed from the cache.

So if caching is turned on and the user enters the wrong passphrase,
subsequent attempts to decrypt the same information will always fail,
because the cached but invalid passphrase is used.  The user has to
manually remove the invalid entry from `plstore-passphrase-alist' to
get a second chance at entering the passphrase correctly.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.