madshi.net

Oh, okay, that's right! I've changed this into a with-block. I'll let you know if the problem still exists...

thanks

But I think I'm doing something wrong with the parameters of the permission entries, because I had to experiment a lot with these to get it to work. Perhaps you can take a look at the two functions used to set the permissions... The following procedure add's the 'full control' permission to the obje...

Yes, you're right, this may not be a problem of the madsecurity lib. next time I experience the problem, I'll try to logoff and on again. I'm currently using WindowsXP SP2 with NTFS volumes.

Hi! This time I could reproduce the behaviour again: I changed the permissions of a directory (Let's call it root directory) and its subfolders and files from Everyone=Read+Execute to Everyone=Read+Execute and Me=FullControl. After that, I opened a programming project within this root directory and ...

Well, at the moment I am not able to reproduce the behaviour. But I encountered this problem several times. In the meantime, I had skipped using my ACL-Lock-Tool, but I'm going to use it again from now on, so I will be able to check if a reboot solves this...

Thanks for your reply,

ciao,
Rainer

hmm... I haven't tried this yet, I'm going to check it this afternoon.

Hi, i've got a strange problem: if i have a file with accessrights 'everyone=read&execute' and i add an entry with full access for my current user, and then remove the entry for my user, i can still modify and delete the file... why that? the windows permissions dialog then just shows 'everyone=...