Skip to content
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

V-221596 for Chrome #1215

Closed
kwygant opened this issue Apr 4, 2023 · 1 comment
Closed

V-221596 for Chrome #1215

kwygant opened this issue Apr 4, 2023 · 1 comment
Assignees
Labels
bug Something isn't working
Milestone

Comments

@kwygant
Copy link

kwygant commented Apr 4, 2023

The registry path for the setting is incorrect.

Current path: HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome
Current Value Name: AutoplayAllowlist

Correct Path: HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome\AutoplayAllowlist
Correct Value Name(s): 1,2, etc

If importing the Chrome admx files and setting the urls in the STIG checklist manually, the following keys values are created
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\AutoplayAllowlist]
"1"="[.]mil"
"2"="[
.]gov"

Once the reg path is fixed, there will still be the issue of the multiple string values getting created as a single multistring value. See #1214

@erjenkin erjenkin changed the title V-221597 for Chrome V-221596 for Chrome Sep 15, 2023
@erjenkin
Copy link
Contributor

In my testing, I think we should be able to leverage a single value name "1" and a comma separated list for this setting, I will have a PR in a bit to fix this issue. Thanks for finding.
image

Eric

@erjenkin erjenkin self-assigned this Sep 15, 2023
@erjenkin erjenkin added the bug Something isn't working label Sep 15, 2023
@erjenkin erjenkin added this to the 4.19.0 milestone Sep 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants