PDA

View Full Version : File permissions set wrong on destination file (build 555)


stevehiner
03-10-2008, 04:56 PM
Over the weekend I batch processed a couple files on my Vista Home Basic machine. I found out last night that the target files have incorrect file permissions set.

Specifically, I can't delete the files. I'm logged in as an admin level account. I approved the delete when prompted by UAC but it told me it didn't have permission and to try again. Then I opened Windows Explorer with explicit Admin rights and I still can't delete the files. I tried forcing all files in that folder to be updated to inherit permissions from the containing folder and it worked fine until it got to those two files where I was informed that I didn't have the rights to change their permissions.

The other files in that folder can be deleted without even getting the UAC prompt. The source files I edited to create those files can be deleted without getting a UAC prompt. It appears that the files have some strange permissions set.

I have not yet tried loggin in as the true machine admin to find out what it will do. At this point I'd rather find out what went wrong so it can be changed in a future version of VRD.

I will try to do some testing tonight. I should be able to pull the ACLs off of some files on that system (the original source files were already deleted) and pull the ACLs from those files to find out what is different.

I would think the destination file should be set to be at least as permissive as the source file. I could see how you might not want to give them identical permissions since a user might be allowed to edit a file for which they have read-only access. You wouldn't want them to have read-only access to the target file. Alternatively, the target file should inherit it's permissions from the containing folder. Overall that might be the easiest and safest way to go anyway.

What do you think?

DanR
03-11-2008, 04:01 AM
Never heard of this before and there's nothing different, that I can thnk of, in 555 that should lead to this behavior. What kind of file are you saving? Did you ahve this problem with any previous versions?

stevehiner
03-11-2008, 09:43 PM
It was an mpg file recorded with my Hauppauge PVR-150. Same type of files I always edit and I've never had this problem before.

I haven't had time to dump the ACLs from the files to find out what's different. I suppose I'll have to figure out how to get the ACLs on the problem files since I might not even have permission to read the ACLs.

DanR
03-11-2008, 11:04 PM
Steve, Thanks for the feedback. I don't even know where to start looking. We don't do anything with ACLs, permissions, user accounts, etc. It just isn't in the code.

Dan203
03-12-2008, 11:09 PM
Might want to try some of the things in this thread...

http://www.videoredo.net/msgBoard/showthread.php?t=6327

Dan