Summary: | "Remember password permanently" option | ||
---|---|---|---|
Product: | Claws Mail (GTK 2) | Reporter: | Pierre Fortin <pf> |
Component: | UI | Assignee: | users |
Status: | REOPENED --- | ||
Severity: | enhancement | ||
Priority: | P3 | ||
Version: | 3.14.0 | ||
Hardware: | All | ||
OS: | All |
Description
Pierre Fortin
2016-06-16 15:22:18 UTC
If you wants passwords remembered forever wrote them on account configuration, is that simple. 'Remember password for this session' is for users which doesn't want to write passwords in the accountrc file, but don't want to be asked for account password on every retrieval while Claws Mail is running. And some users doesn't trust neither disk nor memory and want to be asked every time for the password. (In reply to comment #1) > If you wants passwords remembered forever wrote them on account > configuration, is that simple. That wasn't my point since I wrote: re-enter them via "Edit accounts..." > 'Remember password for this session' is for users which doesn't want to > write passwords in the accountrc file, but don't want to be asked for > account password on every retrieval while Claws Mail is running. But what about the users who've been happily relying on their passwords already existing in the accountrc file; but not being transferred to the new passwordstorerc? In fact, I was on git 141 which used passwordstorerc, yet when moving to git 153, even those were deleted... > And some users doesn't trust neither disk nor memory and want to be asked > every time for the password. I'd bet quite rare user(s) v. the typical user... :) (In reply to comment #2) > (In reply to comment #1) > > If you wants passwords remembered forever wrote them on account > > configuration, is that simple. > > That wasn't my point since I wrote: re-enter them via "Edit accounts..." Ok. > > 'Remember password for this session' is for users which doesn't want to > > write passwords in the accountrc file, but don't want to be asked for > > account password on every retrieval while Claws Mail is running. > > But what about the users who've been happily relying on their passwords > already existing in the accountrc file; but not being transferred to the new > passwordstorerc? In fact, I was on git 141 which used passwordstorerc, yet > when moving to git 153, even those were deleted... I think that change was announced by the developer: http://lists.claws-mail.org/pipermail/devel/2016-May/001698.html If you follow git you're exposed to this kind of things I'm afraid. > > And some users doesn't trust neither disk nor memory and want to be asked > > every time for the password. > > I'd bet quite rare user(s) v. the typical user... :) :-) (In reply to comment #3) > (In reply to comment #2) > > (In reply to comment #1) > If you follow git you're exposed to this kind of things I'm afraid. True; but doing so doesn't make the point of preserving passwords through a rework less valid. While Andrej did add the caveat: Also, your currently stored passwords are invalid, as of latest commit (54ce0e8). Sorry. :) surely he didn't intend for non-git users to lose all their passwords between 3.13.2 and the next release... or did he? My goal in this enhancement request was to point out that the new password system should not lose existing passwords if entered via the password request dialog. In my case, it meant locating my hint file to recall the FOURTEEN active and different account passwords; I should have cancelled all the POP fetches and cut my password entry to 14 instead of 28; but hey... :) Definitely won't be fun if this happens to everyone on the next release... Don't get me wrong... I love being on git to help test and provide feedback. :) No, the idea is indeed to provide a seamless move to passwordrc for users upgrading from previous version. But that will only apply for next release. It's not worth it writing a migration code between two git versions, since at that stage, we were still iterating on the format of the file (and nobody says the format is final even now :) ). |