"Craig A. Berry" <[EMAIL PROTECTED]> writes:
> As I reported earlier, taint.t was failing at test 10. The reason
> has to do with how /tmp is now handled by the C RTL. The test would
> determine that /tmp is a world-writeable directory, which is true for
> recent versions of the C RTL that treat /tmp as sys$scratch.
Well, I don't know about you, but I *don't* have sys$scratch: pointing
to a "world" writable directory. That would be unusual on VMS.
Writable by the owner, yes. Writable by the world, no. Gets around
a lot of the "files in /tmp security holes" on Unix :)
And one result is that t/op/taint.t can't find a world-writable
directory and skips several tests...including the one that was
tripping you up (ignore its message: # all directories writable...
that's for PCs).
Looking a bit deeper, it seems that the problem with /sys$scratch
(as opposed to plain 'sys$scratch') is coming from some VMS-specific
code in mg.c ... it setting tainting on directories in DCL$PATH, but
is only parsing "VMS-style" directories.
(as a side note, why is it "tainting" directories with the S_IWUSR
bit set? I'd think it would be S_IWOTH...Is it okay for others to
write into the directory, but not you?)
It may make more sense to have t/op/taint.t "vmsify" directories
before putting them into DCL$PATH, and the list of directories to
try shouldn't need changing.
--
Drexel University \V --Chuck Lane
----------------->--------*------------<[EMAIL PROTECTED]
(215) 895-1545 / \ Particle Physics [EMAIL PROTECTED]
FAX: (215) 895-5934 /~~~~~~~~~~~ [EMAIL PROTECTED]
