Re: OpenSSH: spaces in user name

"Unruh" == Unruh <unruh-spam@xxxxxxxxxxxxxx> writes:

Unruh> "Nico Kadel-Garcia" <nkadel@xxxxxxxxxxx> writes:
>> "Chuck" <skilover_nospam@xxxxxxxxxxxxxx> wrote in message
>> news:PpGRf.16809$wH5.4757@xxxxxxxxxxx
>>> Michael Heiming wrote:
>>>> Shrug, spaces in username are one of the worst things I could
>>>> think of for a username, could well be a M$ "invention"?
>>>>
>>> It is.

>> It's tied to the "let the user name use anything they want, and
>> even encourage the use of their real names" approach to the world.

Unruh> So why can't I put carriage returns and backspaces and single
Unruh> quotes and double quotes into my name. Seesh, the unwarranted
Unruh> arrogant abridgement of my freedom to do anything I want! -:)

For the record, I completely disagree with all of you. The computer
exists to make work easier for people. If the natural name for a folder
sitting on my desktop is, "SSH Talk," I do not want to have to name it
"SSH_Talk", or "SSH-Talk," or "SSH+Talk," or some other awkward, unsightly
approximation just to satisfy the deficiencies of someone's software
design. Especially when the restrictions come from the impoverished
syntax of a decades-old command language that has exactly no relevance to
my life or work today.

Besides, on a practical level, I do not find it a problem. Bash
completion automatically escapes filename characters that are special to
it. I use "find -print0 | xargs -0" (which is the way it ought to work,
anyway). Etc.

Fix the software, don't "fix" the people.

--
Richard Silverman
res@xxxxxxxx

.

Relevant Pages

  • Re: managing partition labels
    ... Unruh wrote: ... >>to fix that. ... but it don't manage partition labels. ...
    (comp.os.linux.misc)
  • Re: ntpdate.c unsafe buffer write
    ... Unruh wrote: ... Where it met with the same reaction-- ntpdate is deprecated so why fix the ... bug. ... I'll prepare a patch to fix this. ...
    (comp.protocols.time.ntp)
Quantcast