-
Notifications
You must be signed in to change notification settings - Fork 236
Cookies seem to contain successive registration emails. #28
Comments
I dont see anything in that log message that indicates a security problem. |
Weird I don't know how I posted that. Here's the correct info. Session: |
It looks like Github is removing the info from my post becauise it contains email addresses. I have put it here on SO instead. http://stackoverflow.com/questions/25089438/overholt-successive-login-addresses-in-cookie |
I had a look in the Flask-Login source but could not see where this is being written into the cookie but it doesn't seem ideal from a security perspective.
<SecureCookieSession {'_id': '6948290bcaabea200d00961712d41d83', 'user_id': '64', '_fresh': True, '_flashes': [('success', 'Thank you. Confirmation instructions have been sent to [email protected].'), ('success', 'Thank you. Confirmation instructions have been sent to [email protected].'), ('success', 'Thank you. Confirmation instructions have been sent to [email protected].'), ('success', 'Thank you. Confirmation instructions have been sent to [email protected].'), ('success', 'Thank you. Confirmation instructions have been sent to [email protected].'), ('success', 'Thank you. Confirmation instructions have been sent to [email protected].'), ('success', 'Thank you. Confirmation instructions have been sent to [email protected].'), ('success', 'Thank you. Confirmation instructions have been sent to [email protected].'), ('success', 'Thank you. Confirmation instructions have been sent to [email protected].'), ('success', 'Thank you. Confirmation instructions have been sent to [email protected].'), ('success', 'Thank you. Confirmation instructions have been sent to [email protected].'), ('success', 'Thank you. Confirmation instructions have been sent to [email protected].'), ('success', 'Thank you. Confirmation instructions have been sent to [email protected].'), ('success', 'Thank you. Confirmation instructions have been sent to [email protected].')], 'csrf_token': 'b345ae0a9bef46fdb0954abc191c71933d802a27'}>
[pid: 5020|app: 0|req: 12/12] 120.148.164.173 () {76 vars in 1822 bytes} [Wed Jul 30 21:37:00 2014] POST /app/api/pages/savepage/128 => generated 16 bytes in 64 msecs (HTTP/1.1 200) 3 headers in 550 bytes (1 switches on core 0)
Loads user from session or remember_me cookie as applicable
The text was updated successfully, but these errors were encountered: