I don't think we need either, but at the very least, should be merged into (or the other way around).

| |
  • 3
    Personally I think [permissions] is fine to keep, but we should probably merge [file-permissions] and [effective-permissions] into that. – slhck Oct 28 '14 at 8:53
  • 2
    @slhck: Heh, and here I was thinking the more specific [file-permissions] is better. But, yeah, I'll take whatever merge I can get ;D – Der Hochstapler Oct 28 '14 at 8:57
  • 1
    I think [file-permissions] should be the top level as well, to stop it being used for login/active directory permissions etc – Robotnik Oct 28 '14 at 11:11
  • Create and symlink them all to [access-control] – Zoredache Oct 28 '14 at 17:25
  • 1
    I'd say no need for [privileges], [effective-permissions], [access-control]. [permissions] is a subsection of security, and it covers it all so keep [permissions], but since their are lots of [file-permission] questions might as well keep that tag too. – Robin Hood Oct 30 '14 at 6:46
  • Privileges in Windows are different from permissions. Permissions are rights to do things to specific objects (they appear in a "permissions list", or DACL, that's a property of an object). Privileges otoh are rights to do certain things that don't pertain to particular objects, like "set system time" or "take ownership of any object". They are also called "user rights". One uses the Group Policy Editor to grant them to accounts or groups. So if the terms are used correctly they very definitely provide useful information as to what is being talked about. – Jamie Hanrahan Nov 10 '14 at 23:24

You must log in to answer this question.

Browse other questions tagged .