Config file permissions warning is spurious on Windows/NTFS

[DTTerastar]

On Windows (NTFS), splunk-cli emits this warning on every command:

Warning: config file C:\Users\DATURNER.config\splunk-cli\config.toml
has permissions 0666; expected 0600.
The file may contain credentials. Run: chmod 600
C:\Users\DATURNER.config\splunk-cli\config.toml

Running chmod 600 has no effect — NTFS does not support Unix file
permissions, so the reported mode is always 0666 regardless of ACLs.

Expected behavior:
The permissions check should be skipped on Windows (or on filesystems
that don't support Unix permission bits).

Environment:

• splunk-cli v2.0.2
• Windows 11 Enterprise (NTFS)
• Git Bash (MINGW64)

[magifd2]

Fixed in v2.0.3. The permission check is now skipped on Windows since NTFS always reports 0666 regardless of ACL settings.

To protect your config file on Windows, you can use NTFS ACLs:

$path = "$env:USERPROFILE\.config\splunk-cli\config.toml"
icacls $path /inheritance:r /grant:r "${env:USERNAME}:(R,W)"

Alternatively, use environment variables (SPLUNK_TOKEN, etc.) instead of storing credentials in the config file.

Release: https://github.com/nlink-jp/splunk-cli/releases/tag/v2.0.3