stupid permissions

[Guest]

Just venting her

Why cant this "fabulous" OS allow the most basic of all permission configurations - full control except for delete? I want to be able to create write view edit rename and read but not be able to delete. Thats all. Just no delete. But I cannot!! WHY?? Because the OS "designers" didn't envision far enough ahead to see that people would want to do this most basic of all security setups. FULL MODIFY WITHOUT DELETE. Instead, these amateur "designers" decided that modify and delete were the SAME THING

If I were paid to program the OS security module, my design would have been ABLE to tell the difference between a person trying to rename a folder and when they are trying to physically DELETE IT

But NoooOOOOOoooo

The boneheaded RENAME permission is packaged with the DELETE permission

Just venting. Bye.

 

[Gerry Voras]

Isn't what you want an advanced NTFS permission?

Just venting here

Why cant this "fabulous" OS allow the most basic of all permission

configurations - full control except for delete? I want to be able to
create write view edit rename and read but not be able to delete. Thats
all. Just no delete. But I cannot!! WHY?? Because the OS "designers"
didn't envision far enough ahead to see that people would want to do this
most basic of all security setups. FULL MODIFY WITHOUT DELETE. Instead,
these amateur "designers" decided that modify and delete were the SAME
THING.

If I were paid to program the OS security module, my design would have

been ABLE to tell the difference between a person trying to rename a folder
and when they are trying to physically DELETE IT.

 

[*Vanguard*]

"Frustrated" said in

Just venting here

Why cant this "fabulous" OS allow the most basic of all permission
configurations - full control except for delete? I want to be able
to create write view edit rename and read but not be able to delete.
Thats all. Just no delete. But I cannot!! WHY?? Because the OS
"designers" didn't envision far enough ahead to see that people would
want to do this most basic of all security setups. FULL MODIFY
WITHOUT DELETE. Instead, these amateur "designers" decided that
modify and delete were the SAME THING.

If I were paid to program the OS security module, my design would
have been ABLE to tell the difference between a person trying to
rename a folder and when they are trying to physically DELETE IT.

But NoooOOOOOoooo.

The boneheaded RENAME permission is packaged with the DELETE
permission!

Just venting. Bye.

Dear Frustrated (aka Dumbass User):

And just what is so terribly scary about clicking the *Advanced* button
to get at _more_ detailed permission settings, and then clicking Edit to
configure each account as to what *specific* permissions you want allow
for each, including the *DELETE* permission? But NooooOOOOOOoooo,
you're too lazy to bother to even ask and would prefer to whine. If you
are too ignorant to use the Explorer GUI and its right-click context
menu on file and folder objects to go to Properties -> Security ->
Advanced and are only experienced in using a command line then use the
xcacls.exe command; see http://support.microsoft.com/?kbid=318754.

However, it is obvious that you really should NOT be touching the
security permissions. Apparently it is too much rocket science for
boneheads, like you, that are too lazy to do any research on their own
or just ask for help and instead post knee-jerk rants. After you take
your head out of your ass, we would appreciate that you shower and brush
your teeth - TWICE!

Hope you appreciated the same attitude you gave.

 

[John Herbster]

But you like whines, you have to admit that it was impressive!

 

[Guest]

..... . . ... hey um . .. . ...... vanny

so like .. ........ basically you're telling the whole world that there's an easy way to allow folder/file renaming but deny deleting

And this can be acheived by simply accessing the .. .....the... .. ....the "ADVANCED" button ????

okvanny look here

YOU go ahead and try setting those permmies as per *your* instructions. Let me know when you finished writing a fullblown patch to the Security Subsystem that will allow dumbass users to accomplish this because according to the design of the Security Reference Monitor in the Executive Services layer, the rename function is treated the same as a delete function. This has not been altered in any service pack or patch that I know of and I don't think it ever will be. Hence, the whining from King CheepCheep

Dunno bout you ole vanny-boy but in the "intuitive" world, renaming is not exactly the same thing as deleting

OhhhhhhhHHHHHhhhhhhhh but in the MS world, they ARE the same

So either I'M A BONEHEAD because I spent 4 hours finding this out the long way, or THEY ARE for making me spend 4 hours finding this out the long way. Since I'm the one writing this flame, THEY'RETHEBONEHEADS

On the positive side, it could be worse. It could be as bad as SAMBA

Cheer

~BluScara
CIO/CTO