Re: Reconsider password-cache policy

[Michael Albinus]

akater <nuclearspace@gmail.com> writes:

Hi,

> There is no point in allowing one library to use the cache but
> disallowing another to do it.  It does not help with security as any
> Elisp code can access that data anyway, any time, while added complexity
> is always bad for security.  In contrast, there certainly must be a
> clear way to turn caching off once and for all.  Given the current
> policy, it can not possibly exist.  Multiplying ~..-do-cache~ variables
> across elisp libraries will not do users any good.

Setting password-cache-expiry to 0 should do this?

> I also think that password caching should be turned off by default.

I disagree. There are cases you cannot work properly w/o password
caching. See for example the recent discussion about Tramp's sudoedit
method in bug#49724.

Best regards, Michael.