security fix for changed email confirmation #565
Conversation
|
Coverage increased (+0.01%) to 94.298% when pulling ab4c4e4017c35791aed38c379f276f6c72337799 on slint:email_fix into e6cddc6 on mattupstate:develop. |
slint
force-pushed
the
email_fix
branch
2 times, most recently
from
b43bc43
to
0bf9311
Compare
|
Coverage increased (+0.06%) to 94.344% when pulling 0bf9311ff8111b6fb7ec6af626a801bea0376816 on slint:email_fix into e6cddc6 on mattupstate:develop. |
|
Coverage increased (+0.03%) to 94.312% when pulling 0bf9311ff8111b6fb7ec6af626a801bea0376816 on slint:email_fix into e6cddc6 on mattupstate:develop. |
|
Coverage increased (+0.03%) to 94.312% when pulling 57e5dbb0985f04b8214093bf68acef9a40280ea0 on slint:email_fix into e6cddc6 on mattupstate:develop. |
When validating a confirmation token, also checks if the email that the token was created with matches the user's current email.
|
Coverage increased (+0.02%) to 94.302% when pulling ddc09c51dde6c48fc455892e7dad30738768f9db on slint:email_fix into e6cddc6 on mattupstate:develop. |
|
It was released in Flask-Security-Fork v1.8.1 on November 15th, 2016. |
When validating a confirmation token, also checks if the email that
the token was created with matches the user's current email.