Skip to content
This repository has been archived by the owner on Jan 30, 2018. It is now read-only.

Using UID 499 causes unexpected behavior #32

Open
squidsoup opened this issue Jan 21, 2014 · 11 comments
Open

Using UID 499 causes unexpected behavior #32

squidsoup opened this issue Jan 21, 2014 · 11 comments
Assignees
Labels
Milestone

Comments

@squidsoup
Copy link

We've been using CreateUserPkg successfully for our custom OS X installs over the last year and a bit. Having odd issues in 10.9 however, such as the admin user not being available in the list of users to enable for Remote Login and Remote Management, yet the user exists within Users & Groups.

Am I right in thinking that something has changed in Mavericks?

@MagerValp
Copy link
Owner

I can't confirm those two specific issues. Our CreateUserPkg created admin is visible in System Preferences -> Sharing -> Remote Login/Management -> Allow access for -> Plus button.

Which version of CreateUserPkg was used to create the admin package, 1.2.4?

@chrisgrande
Copy link

CreateUserPkg on 10.9 creates a Home Directory that has incorrect permissions along with the issues @squidsoup mentioned.

@MagerValp
Copy link
Owner

Is this a package created with CreateUserPkg 1.2.4? And can you give me specific examples of what doesn't work? Which version and build of 10.9 are we talking about?

@chrisgrande
Copy link

It was created with 1.2.4. The home directory created for the user has all the wrong permissions, owner is system for example. Remote Management doesn't work for the user, has to be toggled on and off - which could be another issue all together. It was 10.9.1 and the currently released 10.9.2.

@MagerValp
Copy link
Owner

That sounds strange, since OS X creates the homedir on first login. Which UID did you use for the user?

@chrisgrande
Copy link

Ahha! I found the issue. A script during the imaging process creates a plist in the nonexistent home directory. This causes a home directory and library folder to be created as root before the initial login because those folders don't exist.

@chrisgrande
Copy link

And for @squidsoup I have found the ARD issue is caused by using the default UID of 499 - once changed to 501 all is well with the Remote Management Settings.

@MagerValp
Copy link
Owner

Interesting. @squidsoup were you using UID 499 as well?

@squidsoup
Copy link
Author

Hi. I'll have to wait until I'm back in the office on Monday, but I suspect
were are!

On 1 March 2014 20:43, MagerValp notifications@github.com wrote:

Interesting. @squidsoup https://github.com/squidsoup were you using UID
499 as well?


Reply to this email directly or view it on GitHubhttps://github.com//issues/32#issuecomment-36418862
.

@arubdesu
Copy link

arubdesu commented May 2, 2014

I'm chiming in regarding this, as @hjuutilainen pointed out on twitter this is a known issue to have sub-500 UIDs for non-system/apple accounts, as per the comments here (⬅️ devforum login required)
My suggestion is either 999 or something distinct and unlikely to cause collisions with regular, 500+ local users

@erikng
Copy link

erikng commented Nov 13, 2014

I would like to chime in here with a fix.

We should no longer be using 499 UID as default (as arubdesu) already explained.

In order to truly hide the account the following command needs to take place:

dscl . create /Users/%username% IsHidden 1

This is how you hide a 500+ account. 999 Should be the new default for CreateUserPKG.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

5 participants