starred/cypht

Fork 0

mirror of https://github.com/cypht-org/cypht.git synced 2026-04-25 13:05:53 +03:00

[GH-ISSUE #217] Save settings without password auth #180

New issue

Closed

opened 2026-02-25 21:34:21 +03:00 by kerem · 6 comments

kerem commented

2026-02-25 21:34:21 +03:00

Owner

Originally created by @Yamakasi on GitHub (Aug 15, 2017).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/217

Originally assigned to: @jasonmunro on GitHub.

It would be nice when we can save settings without the extra password Auth.

This auth is nice when you edit settings for external mailproviders like gmail and such but unneeded for local IMAP.

Originally created by @Yamakasi on GitHub (Aug 15, 2017). Original GitHub issue: https://github.com/cypht-org/cypht/issues/217 Originally assigned to: @jasonmunro on GitHub. It would be nice when we can save settings without the extra password Auth. This auth is nice when you edit settings for external mailproviders like gmail and such but unneeded for local IMAP.

kerem

2026-02-25 21:34:21 +03:00

closed this issue
added the
enhancement

core

framework
labels

kerem commented

2026-02-25 21:34:22 +03:00

Author

Owner

@dumblob commented on GitHub (Aug 15, 2017):

but unneeded for local IMAP.

I hope you mean just for the address localhost, but no other address (disregarding whether on the same LAN segment or whatever).

@dumblob commented on GitHub (Aug 15, 2017): > but unneeded for local IMAP. I hope you mean just for the address `localhost`, but no other address (disregarding whether on the same LAN segment or whatever).

kerem commented

2026-02-25 21:34:22 +03:00

Author

Owner

@jasonmunro commented on GitHub (Aug 15, 2017):

@dumblob this request centers around a very specific case. We currently encrypt all user data stored between logins, as that could contain sensitive information. However, if you use IMAP authentication, and don't allow users to add additional E-mail accounts or profiles, no sensitive data will be stored outside the login session, meaning it would be possible to save the user settings without encrypting it, which would allow a user to save the data without re-entering their password. I'm not saying this is a good idea, but that is the background behind the request :)

@jasonmunro commented on GitHub (Aug 15, 2017): @dumblob this request centers around a very specific case. We currently encrypt all user data stored between logins, as that could contain sensitive information. However, if you use IMAP authentication, and don't allow users to add additional E-mail accounts or profiles, no sensitive data will be stored outside the login session, meaning it would be possible to save the user settings without encrypting it, which would allow a user to save the data without re-entering their password. I'm not saying this is a good idea, but that is the background behind the request :)

kerem commented

2026-02-25 21:34:22 +03:00

Author

Owner

@dumblob commented on GitHub (Aug 17, 2017):

All right, this reasoning didn't appear to me. Then sorry for the fuss.

@dumblob commented on GitHub (Aug 17, 2017): All right, this reasoning didn't appear to me. Then sorry for the fuss.

kerem commented

2026-02-25 21:34:22 +03:00

Author

Owner

@Yamakasi commented on GitHub (Sep 10, 2017):

I was thinking about that it might be nice that you can set in the config if people are able to select themself if they want to have multiple mailboxes, and if they can't it's IMAP only which will remove the password auth for storing.

How is this going so far ?

@Yamakasi commented on GitHub (Sep 10, 2017): I was thinking about that it might be nice that you can set in the config if people are able to select themself if they want to have multiple mailboxes, and if they can't it's IMAP only which will remove the password auth for storing. How is this going so far ?

kerem commented

2026-02-25 21:34:22 +03:00

Author

Owner

@jasonmunro commented on GitHub (Sep 25, 2017):

Initial version is committed. here is the sample ini entry and description: github.com/jasonmunro/cypht@d6bb8164ac

@jasonmunro commented on GitHub (Sep 25, 2017): Initial version is committed. here is the sample ini entry and description: https://github.com/jasonmunro/cypht/commit/d6bb8164ac480b088736006c58adfc9c0eed64bf

kerem commented

2026-02-25 21:34:22 +03:00

Author

Owner

@jasonmunro commented on GitHub (Nov 29, 2017):

I'm going to close this out since it's done - if you find any bugs please re-open a new issue. Thanks!

@jasonmunro commented on GitHub (Nov 29, 2017): I'm going to close this out since it's done - if you find any bugs please re-open a new issue. Thanks!

kerem referenced this issue

2026-02-25 21:36:46 +03:00

[PR #648] [CLOSED] improve compatibility with stalwart-jmap #955