On Tue, Oct 16, 2012 at 7:59 PM, Peter Stuge <[email protected]> wrote: > RjOllos wrote: >> > [...] >> > Well here's the twist, there's nothing *blocking* usernames from >> > being all-uppercase. It's just that parts of Trac *assume* that >> > any uppsercase username is a permission. >> >> That is very unfortunate. At least though, Steffen fixed this in >> AccountManager very recently, to prevent usernames with all >> uppercase from registering: >> http://trac-hacks.org/changeset/12083 > > Sweet indeed. Thanks Steffen!
Hmmm. Surely a lot of Trac installations are on Linux and use the system user name as the Trac user ID. In that case, http://www.linuxquestions.org/questions/linux-newbie-8/user-name-restrictions-312024/ applies: User/group names must match [a-z_][a-z0-9_-]* So just an underscore prefix should be at least fairly safe and unlikely to collide. http://technet.microsoft.com/en-us/library/bb726984.aspx says you can't use " / \ [ ] : ; | = , + * ? < > But we need pipe, equals, and comma in option settings (owner=foo|bar,status!=closed) and brackets are part of the macro invocation. So maybe a colon or semicolon would be safe on Windows and Linux? Or maybe something really odd like ">specialOwner<"? Do less than and greater than have some use in Trac I'm not thinking of? Chris -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
