mirror of
https://github.com/opensolutions/ViMbAdmin.git
synced 2026-04-26 00:36:00 +03:00
[PR #43] [CLOSED] Add a password_scheme field in mailbox table. #262
Labels
No labels
bug
feature
feature
improvement
improvement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ViMbAdmin-opensolutions#262
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/opensolutions/ViMbAdmin/pull/43
Author: @madmatah
Created: 6/9/2013
Status: ❌ Closed
Base:
master← Head:store-password-scheme📝 Commits (1)
661e450Add a password_scheme field in mailbox table.📊 Changes
4 files changed (+38 additions, -0 deletions)
View changed files
📝
application/models/Mailbox.php(+8 -0)📝
application/models/generated/BaseMailbox.php(+7 -0)➕
doctrine/migrations/1370787572_version3.php(+19 -0)📝
doctrine/schema/ViMbAdmin.yml(+4 -0)📄 Description
Add a password_scheme field in mailbox table.
This is useful if you want to deal with multiple password scheme. The
one you use today might be too weak in the future and you should have
the possibility to change it.
The password scheme names stored in this new field are the one
described here : http://wiki2.dovecot.org/Authentication/PasswordSchemes
To use it with Dovecot, you just have to do a query like :
The password_scheme field will contain an empty string for password
which have been set before this change.
( this is also related to issue #32 )
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.