UX: useradd: gaadddaadmin name too long.
64 blocks
Should I leave this as it is or go back to the customer who reauested it and
ask him to choose a shorter username.
Will this cause any problems ??
George
> Should I leave this as it is or go back to the customer who
> reauested it and ask him to choose a shorter username.
> Will this cause any problems ??
>
Let him choose a shorter name. Though useradd added the user- it will
only recognize the user with the first 8 characters, the rest is
ignored (same as with good ole' DES passwords).
Winni
G
"Winfried Neessen" <do...@pebcak.de> wrote in message
news:2008-02-1...@mail.neessen.net...
> I hae logged in using ssh with this user and it seemed to work and
> the entry in password file looks fine. I have su'ed to this user and
> it seems to work file.
>
Well, try loggin in using SSH and only the first 8 chars of the
username. I bet this will work as well- and this is where the problem
is.
Winni
George
"Winfried Neessen" <do...@pebcak.de> wrote in message
news:2008-02-1...@mail.neessen.net...
There are a number of commands which don't work correctly with
usernames longer than 8 characters. These tend to be commands
off the beaten track. Many people do use usernames longer than
8 characters and never see any problems at all.
You might take the view that you'll try it, and if it causes
you or him any problems, you'll require it to be changed.
--
Andrew Gabriel
[email address is not usable -- followup in the newsgroup]
>* george2 <geo...@twig.tk>:
No it won't; there's little which will truncate usernames at 8 bytes.
Casper
--
Expressed in this posting are my opinions. They are in no way related
to opinions held by my employer, Sun Microsystems.
Statements on Sun products included here are not gospel and may
be fiction rather than truth.
George
"Casper H.S. Dik" <Caspe...@Sun.COM> wrote in message
news:47b43df1$0$85781$e4fe...@news.xs4all.nl...
There are many threads about this subject in the past in c.u.s.
Basically, there's no testing that anything over 8 works, and the
problems are likely to arise at the interaction between programs.
Imagine a utility that is checking on processes and uses 'ps -ef'.
Well, that format only prints the first 8 characters of a username. If
it summarizes the output, it will likely be incorrect for users with
long names.
Some other utility may print the full name properly, but shift the rest
of the data down. Now that output goes to some other program that
didn't think usernames could be more than 8 characters, so it gets
confused that the other data has shifted.
So the core things like logging in will work just fine. Other things
may not.
--
Darren Dunham ddu...@taos.com
Senior Technical Consultant TAOS http://www.taos.com/
Got some Dr Pepper? San Francisco, CA bay area
< This line left intentionally blank to confuse you. >
Solaris 9 supports longer MD5 and Blowfish passwords.
See policy.conf(4) and friends.
John
groe...@acm.org
Thanks
George
"Darren Dunham" <ddu...@taos.com> wrote in message
news:Im_sj.388$tW....@nlpi070.nbdc.sbc.com...
I can't think of any bugs but there are some gotchas with commands
that truncate user names to eight characters. This is Solaris 8:
# useradd longname1
UX: useradd: longname1 name too long.
# useradd longname2
UX: useradd: longname2 name too long.
# useradd longname3
UX: useradd: longname3 name too long.
# su longname1 -c 'sleep 1111 &'
# su longname2 -c 'sleep 2222 &'
# su longname3 -c 'sleep 3333 &'
# grep longname /etc/passwd
longname1:x:100:1::/home/longname1:/bin/sh
longname2:x:101:1::/home/longname2:/bin/sh
longname3:x:102:1::/home/longname3:/bin/sh
# ps -ef |grep sleep
longname 471 1 0 18:56:35 pts/1 0:00 sleep 1111
longname 473 1 0 18:56:40 pts/1 0:00 sleep 2222
longname 475 1 0 18:56:48 pts/1 0:00 sleep 3333
It's awkward but not a showstopper (until you accidentally
kill the wrong user's rogue tomcat server or whatever).
Ah, but you'll use ps -u <user> to identify the right process:
# useradd verylongname1
UX: useradd: verylongname1 name too long.
# grep long /etc/passwd
verylongname1:x:100:1::/home/verylongname1:/bin/sh
# ps -fu verylongname1
ps: unknown user verylongna
#
And even if these anomalies have been fixed in Solaris 9, 10 or 11,
doubtless there will be more lurking deep in the undergrowth.
--
John.
>What little witch, I have tried loggin in with ssh and no problems. Can you
>be more specific, cos I'm doing a lot of work on the assumption that this is
>ok. I dont want to end up in a cauldron !!
"ps", I think, will fail in some cases.
This discussion reminds me of when we were using either 7th Edition
UNIX or Perkin Elmer's Sys V (Xelos?). Our student numbers were 7
digits so we stuck an "s" on the front to give a valid UNIX username.
It was amazing how many commands broke - they treated the username as
a string and didn't handle the lack of NUL termination when 8 char
buffers were used.
ps -fu <username>
only works up to 10 characters.
--
Daniel
> Winfried Neessen <do...@pebcak.de> writes:
> >* george2 <geo...@twig.tk>:
> >> I hae logged in using ssh with this user and it seemed to work and
> >> the entry in password file looks fine. I have su'ed to this user and
> >> it seems to work file.
> >>
> >Well, try loggin in using SSH and only the first 8 chars of the
> >username. I bet this will work as well- and this is where the problem
> >is.
> No it won't; there's little which will truncate usernames at 8 bytes.
what's with maildelivery?
--
Fußgänger sind wie das ideale Gas: Sie nehmen jeden zu Vergügung gestellten
Verkehrsraum vollständig ein, notfalls durch intensives Torkeln.