Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Directory Rights and Restrictions

Status
Not open for further replies.

rustylee

Programmer
Sep 11, 2001
59
US
We've recently had some problems with users creating their own folder structures in the Macola directory tree. Users are finding their own workgroup shares are full so, instead of archiving crap that hasn't been opened since 1997, they just find more space somewhere else. That's another issue we are working on.

In the meantime, users creating directories and creating files is not a problem with Macola, per se, but more of a nuisiance in terms of managing disk space and ensuring Macola data is not tampered with. If users are going to the Macola share to put stuff, they could be deleting stuff as well, and that's what concerns me, since this opens up the potential to accidentally delete something that shouldn't be deleted.


Has anybody got some suggestions for securing the data and directory structure that will not impede Macola's ability to function?

-Rusty
 
I should have mentioned that we use Macola for P.SQL. This means that we have to protect the actual Btrieve files as well.

-Rusty
 
Rusty,

Users must have full rights to the Macola data directories. Without it Macola will not function. The solution to your concerns about people messing with Macola data is to upgrade to the MS SQL platform.



Software Sales, Training, Implementation and Support for Exact Macola, eSynergy, and Crystal Reports
 
In my opinion, you can set up the rights below within the Macola directory structure:

_Update_ Not needed
Data_00 Full control
Data Full control
Default Read/List
Help Read/List
Install Read/List
Language Read/List
Media Read/List
PWE Full control
RPTS Read/List
Screens Read/List
Programs Read/List
Users Full control

The user does not need the ability to create folders within the Macola root structure and only needs Read/List rights on the files listed in the root folder.

Kevin Scheeler
 
There really is no solution to this problem. This is also the biggest reason to dump PSQL. Any user with Macola rights can delete your /data directory in a wink, even when you've taken whatever steps you can to work the user rights. I've spoken to Macola about some kind of fix for this obvious security flaw and their only solution is to go to MSSQL. Back in the old MSDOS/Novell days the users didn't even know what a directory was and systems generally had a more tightly controlled user interface that did not include an explorer type tool, so you could get away with leaving your butt hanging out of this particular window. Those days are over.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top