You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
git.allow_any_sha1_in_want=false does not block arbitrary object wants #77
Setting git.allow_any_sha1_in_want = false does not prevent clients from requesting arbitrary object IDs.
Current behavior
The configuration field exists, but upload-pack is initialized with arbitrary SHA-1 wants enabled unconditionally. The gix fetch path also accepts arbitrary wants without consulting the setting. As a result, changing the option to false has no effect.
Expected behavior
When the option is disabled, upload-pack should only accept wants reachable from advertised refs. Both the stock Git and gix serving paths should enforce the same policy.
Suggested implementation
Thread the configured value through upload-pack setup and the gix want validation path, and add protocol tests covering allowed and rejected wants for both values. Since the project is pre-1.0, remove the option instead if unrestricted wants are the only supported design.
Activity
behinddwalls commentedon Sep 30, 2026
Draft fix: #85
This PR is part of the ordered draft stack #85 through #92.
Remove ineffective arbitrary-want setting