Article View: comp.os.ms-windows.nt.admin.security
Article #20Re: Remote registry problems with Windows NT 4.00
From: David LeBlanc
Date: Sat, 07 Jun 1997 00:00
Date: Sat, 07 Jun 1997 00:00
20 lines
1657 bytes
1657 bytes
"Petter Enholm" <petter.enholm@winlink.no> wrote:
>But I don't
>understand why I can't grant access to users that I trust using the
>Security / Permissions ... menu item from regedt32.exe ! ?
You problem is the HKLM/CurrentControlSet/Control/SecurePipeServers/
winreg key. The permissions on that key sets who can access the
registry of that machine remotely. There is an AllowedPaths setting
under that which are exceptions. You can add where you want to allow
to that.
Be careful with this, as there are severe security implications.
David LeBlanc |Why would you want to have your desktop user,
dleblanc@mindspring.com |your mere mortals, messing around with a 32-bit
|minicomputer-class computing environment?
|Scott McNealy
Technical Details
Message-ID:
<339b928b.1218246065@news.mindspring.com>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<01bc7296$bef52910$265e47c1@peenpc>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 113dfb,ebc3871033cc15fa X-Google-Attributes: gid113dfb,public X-Google-Thread: f977f,ebc3871033cc15fa X-Google-Attributes: gidf977f,public X-Google-Thread: fccee,ebc3871033cc15fa X-Google-Attributes: gidfccee,public X-Google-Thread: fd2c4,ebc3871033cc15fa X-Google-Attributes: gidfd2c4,public From: dleblanc@mindspring.com.remove-this (David LeBlanc) Subject: Re: Remote registry problems with Windows NT 4.00 Date: 1997/06/07 Message-ID: <339b928b.1218246065@news.mindspring.com> X-Deja-AN: 246832389 References: <01bc7296$bef52910$265e47c1@peenpc> X-Server-Date: 7 Jun 1997 16:58:45 GMT Organization: MindSpring Enterprises Newsgroups: comp.os.ms-windows.nt.admin.security,comp.os.ms-windows.programmer.win32,fido.win32,microsoft.public.win32.programmer.kernel