[Date Prev][Date Next]
Re: (ITS#3639) Inconsistent access checking in back-shell?
I forget why this check was added, but (as I recall) it
was purposely added. The reasons to why likely can be
found in the commit log and/or -bugs/-devel list archives.
I'll try to dig about later...
At 03:25 PM 4/7/2005, email@example.com wrote:
>Full_Name: Pierangelo Masarati
>OS: Linux (whitebox)
>Submission from: (NULL) (220.127.116.11)
>There appears to be an inconsistency between the behavior of back-shell and that
>of all the remaining backends with respect to access checking for the modify
>operation; back-shell appears to check for write permission to the entry
>pseudo-attribute before attempting to send modifications to the underlying
>script. In general, access checking is pretty loose in preparing write
>operations for back-shell, but this may be regarded as necessary because of its
>intrinsic design limitations. However, the highlighted behavior appears to be
>more over-restrictiveand inconsistent.