@robertgendler commented on GitHub:
Sonoma branch Updated for macOS 14.4.
@brodjieski commented on GitHub:
There seems to be something off here. The expected result in the [pwpolicy_account_lockout_enforce](https://github.com/usnistgov/macos_security/blob/sonoma/rules/p…
@robertgendler commented on GitHub:
We will be updating the location_services to use
pid=$(/bin/ps aux
@robertgendler commented on GitHub:
[rules/system_settings/system_settings_remote_management_disable.yaml]
This actually doesn't use launchctl kickstart.
@robertgendler commented on GitHub:
This seems like it'll be much easier to do in 2.0
@robertgendler commented on GitHub:
@brodjieski fixed it `/bin/ps xa
@stefanbenten commented on GitHub:
@wc7086 Could you elaborate the use case a little more? Transfer.sh original itention is not to be come an archival sharing service. There might be forks…
@paolafrancesca commented on GitHub:
actually it seems even simplier: we have to provide a param for the drive id to use, that could be a shared one. I have to check how client app can join a…
CheckMetadata locking: fatal error: concurrent map read and map write
CheckMetadata locking: fatal error: concurrent map read and map write
@robertgendler commented on GitHub:
Thanks for finding this! @brodjieski just fixed it and PR #367 should have fixed it and some other DISA STIG related issues.
@brodjieski commented on GitHub:
Thanks for bringing this up. Turns out that the check is a bit incorrect. It should be (note the missing .js):
/usr/bin/osascript -l JavaScript << EOS
…
@tcoliver commented on GitHub:
That's a good point, and I like the idea of reading the lastUserName value as a second try. Failing that, I think ideally the result of a failed check - where there…
@robertgendler commented on GitHub:
This makes sense potentially on the rules with $CURRENT_USER. But not other rules.
The potential issue that comes up, what if the first compliance scan is…
CheckMetadata locking: fatal error: concurrent map read and map write
@paolafrancesca commented on GitHub:
@JustAnotherArchivist makes sense, I will try to check in the weekend, probably need to change s.locks with https://golang.org/pkg/sync/#Map