Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#3678 - freenx: conflicting uid in the install script

Attached to Project: Arch Linux
Opened by Rafal Szczepaniak (lanrat) - Friday, 30 December 2005, 22:10 GMT
Last edited by Dale Blount (dale) - Saturday, 31 December 2005, 03:48 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture not specified
Severity Medium
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

In the install script for freenx package there is this command:

echo 'Generating keys ...'
/opt/NX/bin/nxsetup --install --uid 81 2>&1 >/dev/null

however uid 81 is already used for "dbus" user (according to /etc/passwd).

Installation of freenx partialy fails with the message:
Generating keys ...
useradd: UID 81 is not unique
This task depends upon

Closed by  James Rayner (iphitus)
Sunday, 15 October 2006, 11:35 GMT
Reason for closing:  Fixed
Additional comments about closing:  original bug fixed, and latter bugs dont exist now.
Comment by Rafal Szczepaniak (lanrat) - Saturday, 31 December 2005, 02:41 GMT
There is another problem which is not really a bug but IMHO could be mentioned in the install message.

Depending on the ssh daemon configuration it might be impossible to log into "nx" user account from nxclient
due to sshd security rules. By default "nx" account created by nxsetup is locked (passwd -S nx shows locked
status).
Ssh can forbid any logins for this user even with valid keys. In this case a message is logged into
/var/log/auth.log. After unlocking the account with passwd -u nx it should work fine. This also sets an empty
password for "nx" user which is not a very good idea. One can set any password (even completly random)
for "nx" account as it won't be ever used (nxclient uses keys only).
Comment by Tobias Powalowski (tpowa) - Saturday, 31 December 2005, 08:00 GMT
i don't understand your second point,
that's the default could you tell me what you wanna hear in install message then?

the uid is now changed to 85, thanks for mentioning this.
Comment by Jan de Groot (JGC) - Saturday, 31 December 2005, 10:43 GMT
Be sure to register it in the devwiki, in case someone thinks he should use UID 85 for a new daemon ;)
Comment by Rafal Szczepaniak (lanrat) - Saturday, 31 December 2005, 15:13 GMT
@tpowa:
I mean that the install script runs:
/opt/NX/bin/nxsetup --install --uid 85
which creates "nx" account in /etc/passwd with the status "locked".

Then there is only after installation message saying that clients
will not be able to login to the server (nxserver via ssh) if you don't
copy the keys. But the problem is it is not enough. sshd will refuse
any login to "nx" account even with a valid key because the account has
status "locked" (I'm not 100% sure sshd will _always_ do that or if it depends
on some confg options combination). The only place where you can see the sshd error
is /var/log/auth.log (on the server side) - nxclient doesn't return
this information.

So I thought it would be a good idea to mention this potential problem in freenx/nxclient
postinstall message. That's all. If you think it's too much information and users can deal with
this easly without the message that's fine.

What i propose is to add something like this:

If you still can't login with nxclient and valid key try unlocking the nx account
on the server side by running as root: passwd -u nx

@JGC: I was wandering is there any official list of UIDs already reserved or something like this ?

Loading...