False positive "configuration file permissions are too permissive" warning on Windows
Maintainers usually reply within 1 day
@pypaut is already working on this.
Since Oct 20, 2026.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 74/100
Research direction
Find the configuration permission check used by scw config info and other commands that read the config file. Read how it uses os.Stat() and where the warning is emitted, then compare that behavior with the Windows ACL details in the issue. Done when a Windows config with restrictive ACLs no longer produces the false warning, while the permission check still works on supported platforms.
Written by the indexing model from the issue text.
Description
Command attempted
scw config info (any command reading the config file)
Expected behavior
No permission warning on Windows, or a check based on Windows ACLs.
Actual behavior
Every command prints (3 times):
WARNING: Scaleway configuration file permissions are too permissive. That is insecure.
You can fix it with the command 'chmod 0600 C:\Users<user>.config\scw\config.yaml'
The file is already restricted to the current user via NTFS ACLs
(icacls /inheritance:r + /grant:r ":F"). The warning persists.
Root cause: the check relies on Unix mode bits. On Windows, Go's os.Stat()
reports 0666 (or 0444 for read-only files) regardless of ACLs, so the check
always fails. The suggested fix (chmod) does not exist on Windows.
Suggested fix: skip the check when runtime.GOOS == "windows", or implement
an ACL-based check (see how GitLab CLI handled the same issue:
https://gitlab.com/gitlab-org/cli/-/merge_requests/1569).
Environment
scw 2.65.1 (go1.27.1, windows/amd64), installed via Scoop
Windows 11, PowerShell 7
- Dominant language
- Go
- Stars
- 1k
- Forks
- 175
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 141
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from scaleway/scaleway-cli
-
instance security-group create -o json wraps the resource in a `security_group` key, unlike `get` and `list`May be free again @Mia-Cross claimed this 39 days ago, and no pull request is open. Openinstance
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
scaleway/scaleway-cli#6153 · 1 comment · 1 reaction · 1 assignee ·
Maintainers usually reply within 1 day
-
Use lipgloss for tabwriterPossibly taken @remyleone claimed this 1 day ago. Openenhancement
scaleway/scaleway-cli#6608 · 1 assignee ·
Maintainers usually reply within 1 day
-
Add abstraction layer for colorsPossibly taken @remyleone claimed this 3 days ago. Openenhancement ux
scaleway/scaleway-cli#6572 · 1 assignee ·
Maintainers usually reply within 1 day
-
Add support for displaying the annotation of a resource in its getPossibly taken @estellesoulard claimed this 1 day ago. Openenhancement
Difficulty 3/5 1-2 days Newbie friendliness 45/100
scaleway/scaleway-cli#6570 · 1 assignee ·
Maintainers usually reply within 1 day
-
autocomplete script: default basename still uses full argv[0] path, Homebrew zsh/bash completion brokenPossibly taken @yfodil claimed this 3 days ago. Openautocomplete
scaleway/scaleway-cli#6567 · 1 assignee ·
Maintainers usually reply within 1 day
All issues in scaleway/scaleway-cli
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
cloudevents/sdk-go#1346 ·
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
kubernetes/cloud-provider-aws#1517 · 1 comment ·
Maintainers usually reply within 1 day
-
agent-butler-finding chore
Difficulty 1/5 Under an hour Newbie friendliness 88/100
jordansmall/spindrift#6221 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 3 days