-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 22.11.2014 11:21, Gert Doering wrote: > Hi, > > On Sat, Nov 22, 2014 at 10:43:00AM +0100, Steffan Karger wrote: >> On 21-11-14 20:43, Yegor Yefremov wrote: >>> This patch is a result of our IRC discussion with Arne. Alternative >>> approach were to always build with password-save functionality without >>> configure option at all. >> >> Thanks for the patch. But this explanation doesn't help me much in >> understanding why this feature needs to be enabled by default. Could you >> please explain? >> >> (My first thought would be that locally storing a password defeats the >> purpose of the password, so it is a good thing this is disabled by >> default. But good arguments might change my view.) > > My thoughts are along the line - yes, there seems to be a discrepancy > between what configure claims to be the default and "the real default", > but should we change the actual default here, or the configure help > message? > > Given the previous discussions, there seems to be belief that this is > a "dangerous feature" that should be "turned off by default" - so I tend > to, for the sake of consistency, not change the default but change the > configure help output instead. > > ... which makes this a feature-NAK. > > Almost anybody always turns this feature on, at least all distribution have it on.
Arne -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iEYEARECAAYFAlRwaakACgkQe8+cMNS4zRfeUACdG+bFWRPy0WuekfdRSxzZAtJ6 DhQAoOit70W8Z/M72vCqkOq4bsLJPfVZ =uCYv -----END PGP SIGNATURE-----
