On 28.04.2015 07:01 PM, Martyn Welch wrote:
> Found the issue.
>
> We run with numeric usernames (due to our corporate accounts having pure
> numeric usernames and a wish to use that for authentication).
> Historically this has been an issue with some old Unix/Linux tools (the
> username getting mistaken for a UID) however our usernames are
> sufficiently long that in practice this has never been an issue (and it
> possibly only affects really old versions of some tools...)
>
> The temporary fix for me is to modify line 67 of x2gosqlitewrapper.pl in
> sanitizer(). The line is currently:
>
> if ($string =~
> /^([a-zA-Z\_][a-zA-Z0-9\_\-\.\@]{0,47}[\$]?)\-([\d]{2,4})\-([\d]{9,12})\_[a-zA-Z0-9\_\-\.]*\_dp[\d]{1,2}$/)
>
> {
>
> I changed it to:
>
> if ($string =~
> /^([a-zA-Z0-9\_][a-zA-Z0-9\_\-\.\@]{0,47}[\$]?)\-([\d]{2,4})\-([\d]{9,12})\_[a-zA-Z0-9\_\-\.]*\_dp[\d]{1,2}$/)
>
> {
>
> Notice the addition of the "0-9" in the first part of the regex...Hm, I'm not sure I want to add that to our packages. That's non-standard-compliant and you're basically on your own when doing "funky stuff". I agree with Robert, a full numeric username is ambiguous, because it *could* be a UID. Mihai
signature.asc
Description: OpenPGP digital signature
_______________________________________________ x2go-user mailing list [email protected] http://lists.x2go.org/listinfo/x2go-user
