For details on how to use
this window, see Chapter 8.
3. Click Advanced, and then click Add.
If the Add button is disabled (grayed out), you??™ll have to take
ownership of the key, close the Permissions window, and
then reopen it before you can make any changes to the permissions
of this object. See Chapter 8 for details.
4. In the Enter the object names to select field, type Everyone, and then
click OK. (The ???Everyone??? user encompasses all user accounts, including
those used by Windows processes and individual applications when
they access the Registry.)
5. In the next window, ???Permission Entry for...???, click the checkbox in
the Deny column, next to the actions you want to prohibit, as in
Figure 3-10. See below for examples.
6. When you??™re done, click OK in each of the three open dialog windows.
The change will take effect immediately.
Now, you may be tempted to remove Allow permissions for a particular
user (or even all users), rather than add the Deny entry shown here. The
problem is that doing so wouldn??™t prevent an application or Windows from
taking ownership or adding the necessary permissions and breaking your
lock. Furthermore, it would make it much more difficult to restore the old
permissions should you need to remove the lock; using this procedure, all
you need to do is remove the Deny rule and you??™re done.
This works because Windows gives Deny rules priority over Allow rules,
which means you can lock a key even if there??™s another Allow rule that
expressly gives a user permission to modify the item.
Pages:
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179