Changes

Microsoft Windows Registry Security

976 bytes added, 21:08, 23 December 2014
The following lines were added (+) and removed (-):
Using a Windows native API, registry keys can be created by software as the programmers intention, to hide or obfuscate data using embedded nulls in the key names.  In this way, even if the registry key name is known, it does not appear in the Windows registry editor and cannot be easily removed by the user.Using a Windows native API, registry keys can be created by software as the programmers intention, to hide or obfuscate data using embedded nulls in the key names.  In this way, even if the registry key name is known, it does not appear in the Windows registry editor and cannot be easily removed by the user.  All Registry keys may be restricted by access control lists (ACLs), depending on user privileges, or on security tokens acquired by applications, or on system security policies. == Microsoft Windows Predefined Root Keys == In a typical Windows XP/2000 machine.*HKEY_CLASSES_ROOT*HKEY_CURRENT_USER*KEY_LOCAL_MACHINE*KEY_USERS*HKEY_CURRENT_CONFIG These keys remain fairly consistent in versions since XP - 2007.  The keys at the root level of the hierarchical database are generally named by their Windows API definitions, which all begin "HKEY".  The HKEY_LOCAL_MACHINE and HKEY_CURRENT_USER hives have a similar structure to each other.   Even though the Registry presents itself as an integrated hierarchical database, branches of the Registry are actually stored in a number of disk files called hives.  Some hives are volatile and are not stored on disk at all.  Individual settings for users on a system is stored in a hive as a file on the drive, one per user.
Bureaucrat, administrator
16,192
edits