Skip to content

os/user: allow nil values for user HomeDir field on windows platforms #37353

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

khyberspache
Copy link

@khyberspache khyberspache commented Feb 21, 2020

No description provided.

…not exist. A home directory not existing could be an administrative user running an executable from a non-interactive login (PSRemote, WMI, etc), where they might not have a home directory on that system. In the event a users executes a binary on a rremote system where they do not have a home directory, the HomeDir value will be nil.
@googlebot
Copy link

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.


What to do if you already signed the CLA

Individual signers
Corporate signers

ℹ️ Googlers: Go here for more info.

@googlebot googlebot added the cla: no Used by googlebot to label PRs as having an invalid CLA. The text of this label should not change. label Feb 21, 2020
@khyberspache khyberspache deleted the 37348-approach branch February 21, 2020 05:32
@khyberspache khyberspache restored the 37348-approach branch February 21, 2020 05:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: no Used by googlebot to label PRs as having an invalid CLA. The text of this label should not change.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants