In message <[EMAIL PROTECTED]>, Ken Wallis
<[EMAIL PROTECTED]> writes
UniData has a VOC_READONLY environment variable which can be set that allows
it to run successfully in a directory where the VOC has no write permission.
Perhaps UniVerse has the same or similar.
Bear in mind the OP of this particular thread said "If I can update the
VOC", then your comment is irrelevant, but from what Susan says, I
presume she has some magic way of dealing with that.
I can't conceive of a way to make this safe without setting suitable OS
level permissions. I can see how it could be made safe enough that you
couldn't get round it with normal verbs and editors, but I can't see how it
could be fixed so that a programmer couldn't get around it, or even a savvy
user setting up VOC pointers from another account.
Exactly. How on earth is Remote VOC going to prevent me from messing
about with the system if I have update capability and can recreate an
unprotected, vanilla, VOC entry for ED or COPY or whatever verb happens
to take my fancy ... ?
Cheers,
Wol
--
Anthony W. Youngman <[EMAIL PROTECTED]>
'Yings, yow graley yin! Suz ae rikt dheu,' said the blue man, taking the
thimble. 'What *is* he?' said Magrat. 'They're gnomes,' said Nanny. The man
lowered the thimble. 'Pictsies!' Carpe Jugulum, Terry Pratchett 1998
Visit the MaVerick web-site - <http://www.maverick-dbms.org> Open Source Pick
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
