Fix InitWithTemplate mkdir permissions inconsistency (0o700 vs 0o777) #9

New issue

Closed

opened 2026-09-20 15:05:21 +00:00 by agent · 0 comments

agent commented

2026-09-20 15:05:21 +00:00

Member

Problem

core/load.go:75 uses 0o700 for os.MkdirAll in InitWithTemplate:

if err := os.MkdirAll(filepath.Dir(a.UserPath()), 0o700); err != nil {

But core/write.go:50 uses 0o777:

if err := os.MkdirAll(filepath.Dir(path), 0o777); err != nil {

The 0o700 in InitWithTemplate is overly restrictive — it creates directories that only the owner can access, which breaks scenarios where the config directory is shared (e.g. system-wide configs, Docker volumes, or shared dev environments). The 0o777 in WriteFile is correct — it respects the process umask.

Fix

Change core/load.go:75 from 0o700 to 0o777:

if err := os.MkdirAll(filepath.Dir(a.UserPath()), 0o777); err != nil {

Files

core/load.go — one-line change

Verification

Existing TestInitWithTemplate and TestInitWithTemplateReadOnlyDir tests should still pass.

## Problem `core/load.go:75` uses `0o700` for `os.MkdirAll` in `InitWithTemplate`: ```go if err := os.MkdirAll(filepath.Dir(a.UserPath()), 0o700); err != nil { ``` But `core/write.go:50` uses `0o777`: ```go if err := os.MkdirAll(filepath.Dir(path), 0o777); err != nil { ``` The `0o700` in `InitWithTemplate` is overly restrictive — it creates directories that only the owner can access, which breaks scenarios where the config directory is shared (e.g. system-wide configs, Docker volumes, or shared dev environments). The `0o777` in `WriteFile` is correct — it respects the process umask. ## Fix Change `core/load.go:75` from `0o700` to `0o777`: ```go if err := os.MkdirAll(filepath.Dir(a.UserPath()), 0o777); err != nil { ``` ## Files - `core/load.go` — one-line change ## Verification Existing `TestInitWithTemplate` and `TestInitWithTemplateReadOnlyDir` tests should still pass.

agent added the

proj-config-lib

tier-0-trivial

labels

2026-09-20 15:05:50 +00:00

agent referenced this issue

2026-09-20 15:06:03 +00:00

Plan: Fix config library issues (priority order) #3

agent referenced this issue

2026-09-20 15:33:52 +00:00

Plan: Production readiness — v0.1.0 release blockers #11

agent closed this issue