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

ConfigureRemotingForAnsible.ps1 LocalAccountTokenFilterPolicy #42978

Closed
jborean93 opened this Issue Jul 18, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@jborean93
Contributor

jborean93 commented Jul 18, 2018

SUMMARY

There are a few cases where LocalAccountTokenFilterPolicy needs to be set to 1 to enable WinRM to authenticate over NTLM. IIRC winrm quickconfig and Enable-PSRemoting should set this key by default but this seems to be not happening with some newer hosts. From what I can see, the registry key is not being set because

  • We don't have an explicit check on the key
  • We don't call winrm quickconfig
  • We call Enable-PSRemoting but due to PowerShell/PowerShell#4033, it won't configure the host if all other conditions meet the enabled criteria and this key is not 1

Without this key being set, then any authentication over NTLM will fail if not using the builtin Administrator account.

The question is whether we should be explicitly setting that key ourselves or leave it as is. This key does have some security implications and thought it best to discuss this first before I raise a PR to change it.

ISSUE TYPE
  • Bug Report
COMPONENT NAME

ConfigureRemotingForAnsible.ps1

@ansibot

This comment has been minimized.

Show comment
Hide comment
@ansibot

ansibot Jul 18, 2018

Contributor

Files identified in the description:
None

If these files are inaccurate, please update the component name section of the description or use the !component bot command.

click here for bot help

Contributor

ansibot commented Jul 18, 2018

Files identified in the description:
None

If these files are inaccurate, please update the component name section of the description or use the !component bot command.

click here for bot help

@ansibot

This comment has been minimized.

Show comment
Hide comment
@ansibot

ansibot Jul 18, 2018

Contributor

@jborean93 Greetings! Thanks for taking the time to open this issue. In order for the community to handle your issue effectively, we need a bit more information.

Here are the items we could not find in your description:

  • ansible version

Please set the description of this issue with this template:
https://raw.githubusercontent.com/ansible/ansible/devel/.github/ISSUE_TEMPLATE.md

click here for bot help

Contributor

ansibot commented Jul 18, 2018

@jborean93 Greetings! Thanks for taking the time to open this issue. In order for the community to handle your issue effectively, we need a bit more information.

Here are the items we could not find in your description:

  • ansible version

Please set the description of this issue with this template:
https://raw.githubusercontent.com/ansible/ansible/devel/.github/ISSUE_TEMPLATE.md

click here for bot help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment