On Mon, Aug 6, 2012 at 5:08 PM, Sergey Sfeli <sergey.sf...@gmail.com> wrote:
> Fossil should deny doing this (or at least warn when someone's trying to > rename the only "s" user in repository, like I did). > That can be fixed from the command line with something like: f user password user newpassword when writing the JSON API i came across that problem. i don't remember exactly how i handled it there except that changing a user's name forces an invalidation/removal of their login token (it is no longer valid because of the hash change). We cannot prohibit someone from renaming a user just because he's the last setup user (but only setup users can edit setup users). Granted, it's a nasty corner case, but workaround around it is relatively simple. If you can suggest how fossil might better handle this (aside from outright prohibiting it), i'm all ears. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
