Changes between Initial Version and Version 1 of Ticket #27518, comment 3


Ignore:
Timestamp:
Nov 21, 2016, 9:16:10 AM (8 years ago)
Author:
Romain Garrigues

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #27518, comment 3

    initial v1  
    1 I also tried the second approach proposed in the article:
     1I also tried the approach proposed in the article as solution 1 in "Plugging The Leak" section:
    221/ check the token,
    332/ generate a new one by changing the user password, making the old one invalid (as the token is based mainly on user password and last_joined fields),
Back to Top