Edit report at https://bugs.php.net/bug.php?id=64986&edit=1
ID: 64986
Updated by: a...@php.net
Reported by: mhhechanova at gmail dot com
Summary: is_readable cannot read UNC path
-Status: Assigned
+Status: Feedback
Type: Bug
Package: *Directory/Filesystem functions
Operating System: Windows 64 Bit
PHP Version: 5.3.26
Assigned To: ab
Block user comment: N
Private report: N
New Comment:
What happens if you try to access a share on \\127.0.0.1 ?
Previous Comments:
------------------------------------------------------------------------
[2013-06-11 11:10:42] mhhechanova at gmail dot com
Administrator account has full control.
------------------------------------------------------------------------
[2013-06-11 11:06:40] a...@php.net
Could you please check via the gui, properties->security->advanced, if the user
has the right to 'read attributes' and 'read extended attributes'? If it's not
set, please do set and try again. That permission must be set on every path
element.
------------------------------------------------------------------------
[2013-06-11 10:47:43] mhhechanova at gmail dot com
Administrator account has read, write and execute permission to the given path.
It
still does not work...
thanks
------------------------------------------------------------------------
[2013-06-11 10:46:09] a...@php.net
ping?
------------------------------------------------------------------------
[2013-06-10 07:53:45] a...@php.net
Ok, despite it's not the complete output, from what I see there is an
inheritance. That
means if there was a deny in any superior object, it will override any allow on
that file.
Please try the following:
icacls /inheritance:r <path to file>
icacls <path to file> /remove:d <my suer>
icacls <path to file> /grant <my user>:(F,M,R,RX,W)
This way you disable inheritance and ensure the user has all the ACLs set. You
can play
with setting removing various ACLs to see the effect. Please consult you
network admin.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
https://bugs.php.net/bug.php?id=64986
--
Edit this bug report at https://bugs.php.net/bug.php?id=64986&edit=1
