* localsink: skip keys that resolve outside the sink directory
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* filer: reject entry paths with dot segments
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* filer: test renames onto dot-segment targets
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* filer: keep the dot-segment rename test inside one bucket scope
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* localsink: resolve keys through an os.Root on the sink directory
The lexical check alone lets a symlinked directory that already exists
under the sink directory carry writes and deletes outside it. Create,
rename and delete now go through an os.Root opened on the sink
directory, so a symlink can only resolve inside it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* localsink: follow absolute symlinks that resolve inside the sink directory
os.Root rejects every absolute symlink target, so a backup through an
absolute link that points back into the sink failed, and a delete through
it left the file behind. Resolve the parent of the key first and use the
resolved path when it stays under the sink directory. Operations still go
through os.Root, so a link swapped after the check cannot escape.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
