garys_2k
join:2004-05-07
Farmington, MI
 ·Future Nine Corpor..
·Vonage
| reply to redxii
Re: XP: Your Very own Low-Rights IE
said by redxii  :said by garys_2k :For one thing, secpol.msc doesn't exist on Home machines. I'm not sure if you import a copy from a Pro machine it would work, anyway. There's a SetSAFER.msi if you follow the first link. No, the first link didn't go to that page. It links to .../secure11152004.asp, where the one with the link is at .../secure01182005.asp -- but no matter, I found it. |
redxii
too big to fail
Premium,Mod
join:2001-02-26
Texas
Host:
/dev/null
Broadband Tweaks
Suddenlink
ISDN
Fiber Optic
1 edit | reply to garys_2k
said by garys_2k :For one thing, secpol.msc doesn't exist on Home machines. I'm not sure if you import a copy from a Pro machine it would work, anyway. There's a SetSAFER.msi if you follow the first link. Since Pro users do have secpol, there's no need to 1) download setSAFER and 2) install .NET to run setSAFER. Well, here's a tidbit for editing it manually, if someone with XP Home could try because I currently don't have Home installed:
The registry keys reside under HKLM\Software\Policies\Microsoft\Windows\Safer\CodeIdentifiers\131072. For each file or directory, add a new key named {GUID} where GUID is a random GUID in classic GUID format, such as {cc845d85-f38e-426a-8644-9d2f90c830d8}, and then add the following values:
Description (REG_SZ) A comment about the rule.
ItemData (REG_SZ) Directory or filename
SaferFlags (REG_DWORD) 0x0 Actually, a million ways are listed without using the secpol. Just that Pro users have the benefit of having the policy editor and someone to compile easy to use instructions.
--
Microsoft Windows 2000/XP Security: Some Assembly Required. |
