Skip to content

Conversation

cmb69
Copy link
Member

@cmb69 cmb69 commented Oct 19, 2020

A recent bug fix regarding symlinks claimed:

After resolving reparse points, the path still may be a reparse
point; in that case we have to resolve that reparse point as well.

While that is basically correct, some reparse points may point to
inaccessible system folders (e.g. IO_REPARSE_TAG_DEDUP points to
"\System Volume Information"). Since we don't know details about
arbitrary reparse points, and are mainly interested in nested symlinks,
we take a step back, and only resolve IO_REPARSE_TAG_SYMLINK for now.

A recent bug fix regarding symlinks claimed:

> After resolving reparse points, the path still may be a reparse
> point; in that case we have to resolve that reparse point as well.

While that is basically correct, some reparse points may point to
inaccessible system folders (e.g. `IO_REPARSE_TAG_DEDUP` points to
"\System Volume Information").  Since we don't know details about
arbitrary reparse points, and are mainly interested in nested symlinks,
we take a step back, and only resolve `IO_REPARSE_TAG_SYMLINK` for now.
@cmb69 cmb69 added the Bug label Oct 19, 2020
@php-pulls php-pulls closed this in 848e24f Oct 26, 2020
@cmb69 cmb69 deleted the cmb/80258 branch October 26, 2020 10:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant