username (login name) with 10 characters

[ssarmiento]

Hi,

How I do a username (login name) with 10/12
characters on hpux ( B.11.00) on untrusted mode

I modified the /etc/passwd but not it works!

Thanks

[Cheryl Griffin]

#man 4 passwd

The following fields have character limitations as noted:

+ Login name field can be no longer than 8 characters;


Cheryl Griffin

[steven Burgess_2]

Hi

Thats because as standard the maximum number of characters for a password is 8 characters

I think there are utilities that will allow you to change this though

Will have a look for you

HTH

Steve

[James R. Ferguson]

Hi:

Technical Knowledge Base document #KBRC00003778 offers a work-around with patch PHCO_21833 (now, PHCO_26089) for 11.0.

Regards!

...JRF...

[ssarmiento]

I downloaded this patch and when i try install, it send a message :

You do not have the required permissions to perform this SD operation. Please check to see that you have the required permissions using the "swacl" command or see your system administrator for assistance.

What happen ?

[Dave La Mar]

1. Check login to be root.
2. Check file permissions.

Best of luck.
dl

[Michael Tully · Accepted solution]

This document from the Technical Knowledge base should contain the information on your problem with 'swacl' permissions.

see KBRC00000273 as well : see below ...

These errors can be caused by confusion within the Software Distributor. There are different
sources of confusion are usually cleared up by following these instructions:

1.Login as root

2.Move the directory /var/adm/sw/security and its contents to /var/adm/sw/security.old

mv /var/adm/sw/security /var/adm/sw/security.old

3.Make an new /var/adm/sw/security directory

mkdir /var/adm/sw/security

4.Change the owner of the /var/adm/sw/security directory

chown bin:bin security
5.Change the mode of the /var/adm/sw/security directory

chmod 755 security

6.If installing from a cdrom unmount the cd.

umount /cdrom

7.Change the mode of the cdrom mount direcotry.

chmod 777 /cdrom

8.Stop the swagentd daemon.

/sbin/init.d/swagentd stop

NOTE: Execute this command on both local and remote machines, if applicable.

9.Register the source as a depot:
If the file is on the local machine:

swreg -l depot /tmp/PHxx_yyyy.depot

If the cdrom is on local machine:

swreg -l depot /cdrom
If the cdrom is on remote machine:

swreg -l depot @ "hostname":/cdrom

10.Restart the swagentd daemon.

/sbin/init.d/swagentd start

NOTE: Execute this command on both local and remote machines, if applicable.

11.If installing from a cdrom remount the cd.

mount /cdrom

12.Now re-install the software. swinstall

Of course, these errors may actually be a function of a non-root user attempting to execute
swinstall or some other Software Distributor function. To allow a non-root user to install patches
read the following.

Description

The swacl mechanism protects all the different objects and actions that Software Distributor
(SD) knows about. Note that this is not the same thing as the similarly named file system ACLs
(Access Control Lists).

The man page for swacl(1) is not particularly detailed but gives an overview. The full details are
described in the CDROM manual Managing Software with HP-UX (B2355-90054). Take a
look at Chapter 8 Controlling Access to Software Objects. There are so many options that you
really need to go through the section, but the specific area you will need is Root ACLs. This
object is the one on which you need to open permissions.

To avoid the error, insert the permissions on the host object (not root object).

For example:

1.Write the host level for swacl to a file.

# swacl -l host > swacl.host

2.Display the new file:

# cat swacl.host

#
# swacl Host Access Control List
#
# For host: hpchs9
#
# Date: Mon Dec 29 17:39:08 1997
#
# Object Ownership: User= root
# Group=sys
# Realm=hpchs9.cup.hp.com
#
# default_realm=hpchs9.cup.hp.com
group:swadm:crwit
any_other:-r--t


3.Edit the file swacl.host

4.Give permissions to the desired user.

user:desired_username:a

Note: The a gives the user all permissions. Refer to the swacl(1) man page for
details on the more specific permissions such as read/write/insert etc.

EXAMPLE: To give permissions to user max:

user:max:a

5.Now swacl.host looks like this without the comments being displayed:

user:max:crwit
group:swadm:crwit
any_other:-r--t

6.Write this new version back into the system with the swacl command.

swacl -l host -F swacl.host

7.Go back to users swinstall session and select Action->Change Target.

8.Change the target to /tmp, for example.

[T G Manikandan]

check this link for username length limitation

http://bizforums.itrc.hp.com/cm/QuestionAnswer/1,,0x70b8cf38d6bdd5118ff10090279cd0f9,00.html

[doug hosking]

Let me stress that the patch mentioned above is by no means a 'solution' for the 8 character limit. You can stick a penny under a fuse in a fuse box and 'appear' to solve a problem with electrical overload. All you have really done is bypass the safety mechanism, leaving you vulnerable to serious consequences later. Enabling the option provided by this patch is similar. As clearly stated in the patch documentation, HP does NOT recommend that you bypass the check in this way.
There are known negative consequences, both functional and security, in doing so. This is absolutely a 'use at your own risk' patch.
Unfortunately, removing this limit would require substantial changes throughout the system and would result in a number of compatibility issues. HP is very much aware of the desire to remove this limit and eager to do so when the changes can be done in a clean, supportable way, but the issue is much more complicated than it appears on the surface. It is not practical to fix this limit with patches. Please don't enable this option unless it is TRULY critical to your business and you understand the consequences of doing so.

[Frank Slootweg]

After all these (excellent) responses, I *have* to ask the obvious question(s):

*Why* do you want/need a user/login name greater than 8 characters?

Is it real a *user/login* name or do you want a longer name for the user part of an *email address*?

[ssarmiento]

I following to Michael Tully`s guide but it send la next message:

A Remote Procedure Call to a daemon has failed. Could not start a management session for "sgi_cor:". Make sure the host is accessible from the network, and that its daemon, swagentd, is running.

I know is other problem.
(yes , my swagentd is running)

**********
Frank Slootweg

Yes, I want a longer name for the user part of an email address .

I have sendmail and qpopper installed.

do you have other solution ?

[Frank Slootweg]

> Yes, I want a longer name for the user part of an email address .

I am not a e-mail specialist, but as far as I know, you can add the long name to your aliases. See aliases(5M). I don't know how the reverse (short name to long name) is done.

If you do not get sufficient answers in this thread, then it is probably best to repost your (properly described) question to the messaging Forum.

[ssarmiento]

Hi, again

The install was Ok.

Now, Can I do username with 10 characters or I need do anything more ?

Thanks