On Thu, Sep 15, 2011 at 6:19 AM, Altu Faltu <[email protected]> wrote:
> It would be simple to have one auth token for each login and purge stale > auth tokens regularly. Purging stale tokens should be a matter of few SQLs > for the current backend of fossil, sqlite. > In principal it's simple, yes, but the current code can't support it because the auth token is written into the user table (i.e. there's only one slot for it). This would require a new table to hold the data. It sounds reasonable, though, and i'll take a look at this. Then, we can enable multiple logins and also keep the current IP check as it > is. > Well "functionally as it" - some amount of code for this would have to be shifted around. :) -- ----- stephan beal http://wanderinghorse.net/home/stephan/
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
