NETWORK DISTRIBUTED SYSTEM FOR UPDATING LOCALLY SECURED OBJECTS IN CLIENT MACHINES

Abstract: Technique for allowing real time centralized administration of protected objects on client computer systems. When a user logs on to a centrally administered clients machine on a computer network, an intermediary object modification process starts in the background with administrator account permissions. Thereafter, whenever the administrative agent on the client computer system unsucessfully attempts to perform an operation on a protected object for which the logon user lacks sufficient permission to perform (218, 220), the agent passes a request (226, 312) to the intermediary process to perform the operation. The intermediary process is able to perform the desired operation because it has sufficient permission to do so even if the administrative agent does not.

Description: NET ORK DISTRIBUTED SYSTEM FOR UPDATING LOCALLY SECURED OBJECTS IN CLIENT MACHINES COPYRIGHT DISCLAIMER A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure as it appears in the U.S. Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever. BACKGROUND 1. Field of the Invention The invention relates to techniques for centralized administration of networked computers, and more particularly, to techniques for such centralized administration where administered objects on client machines require security permissions before they can be modified. 2. Description of Related Art Many modern computer systems and computer operating systems incorporate security measures which operate to protect the various components in the computer - hardware, software and data - from unauthorized use, theft, and intended or unintended damage. The Microsoft ® WindowsNT ® operating system, for example, provides a number of such security features. The WindowsNT security model is described in Chap. 6 of "Microsoft WindowsNT Workstation Resource Kit", Microsoft Press (1996) . This entire book is incorporated herein by reference. In the WindowsNT security model, the operating system maintains security information about each user, group and object. As used herein, an object is anything in the system for which permissions are checked before an operation on it is allowed. In WindowsNT, objects include, but are not limited to, directory objects, object-type objects, symbolic link objects, semaphore and event objects, process and thread objects, section and segment objects, port objects, file objects, the WindowsNT registry, the various nodes within the WindowsNT registry, and the various key names and values in the WindowsNT registry. Users and groups are assigned specific "permissions" which grant or deny access to particular objects. When a user logs on to a WindowsNT network, the operating system creates a security access token for the user, which includes all of the permissions for the user and for the groups to which the user belongs. Every process that runs on behalf of the user is then given a copy of the user's security access token. Whenever a process attempts to access an object, the operating system compares the permissions listed in the security access token for the process with the list of access permissions for the object to ensure that the process has sufficient permission to access the object. One objective of the security model used in WindowsNT is to ensure that the programs which a user runs do not have greater access to objects than the user does. In WindowsNT, the types of permission that can be granted or denied for a particular object are dictated by the type of the object. For example, for a printer queue object, permissions that can be specified include whether a user or group can manage documents and/or can print documents. For a registry entry, permissions include whether a user or a group can read, write, modify, rename, and so on. Objects for which access is to be controlled are assigned an access control list (ACL) , made up of access control entries (ACEs) . Each ACE specifies a particular user or group and indicates what type of access (i.e. which operations) that user, or members of that group, are permitted to perform on the object. For registry nodes and registry entries, the following types of access can be specified in an ACE: Query Value Set Value Create Subkey Enumerate Subkeys Notify Create Link Delete Write DAC Write Owner Read Control The WindowsNT registry and registry administration are described in Chap. 24 of the above- incorporated WindowsNT Workstation Resource Kit book. The WindowsNT object and user permissions mechanism is not to be confused with the distinction between kernel mode and user mode of the central processing unit. Kernel mode is also known as privileged mode, supervisor mode, protected mode or Ring 0. The WindowsNT 4.0 Workstation architecture, including a description of portions of the operating system that operate in user or kernel mode, is described in Chap. 5 of the above-incorporated WindowsNT Workstation Resource Kit book. Protected modes are also described in "Pentium Architecture and Programming Manual" (1995) , incorporated herein by reference. In a default installation of WindowsNT, a number accounts are predefined. These include a system account as well as an administrator account. The owner of an object has complete discretion to grant or deny permissions to any account, including the administrator; but the administrator always retains the ability to take ownership of an object and thereby increase the permissions granted to the administrator. In a default installation of WindowsNT, permissions are automatically set on certain components of the registry that allow work to be done while providing a standard level of security. For example, the registry nodes containing configuration information for application software usually grant "Full Control" permission to the creator/owner, to the system account, and to the administrator account. But the registry nodes containing configuration information about local machine hardware components usually grant "Full Control" permission only to the system account and the administrator account. The group "Everyone" is often granted only "Read" permission. In most cases, where access to a registry entry by ordinary users is controlled, the administrator by default is nevertheless given full access. Numerous business and academic settings today deploy a large number of computer systems all connected together via a computer network. For large computer networks, the administration costs can become extremely burdensome unless all of the computers can be administered from one or a few central locations. Responding to this need, a number of centralized network administration products have been developed. Two such products are the Norton Administrator for Networks (NAN) and the Norton Desktop Administrator (NDA) , both available from Symantec Corporation, Cupertino, California. Both of these products provide a wide variety of centralized administration functions. Many of these functions involve updating the registry on various client computers around the network. The Norton Administrator for Networks, for example, contains a registry modification feature that allows the network administrator to modify registry entries on client machines without having to be physically present at their machines . The Norton Desktop Administrator allows the network administrator to set policies on client machines, which also involves modifying certain registry keys. The latter product allows the network administrator from a central machine to set certain policies on client machines to prohibit them from doing certain tasks, such as by turning off the "run" option on the start menu, removing the ability to get a DOS prompt, and so on. These policies are all defined in registry settings on the client machine. In order to minimize network traffic and also minimize the load on the central administrative server, the above two products follow a model under which a database is maintained on a central administrative server (not necessarily the same server which is running the network administration software) , which indicates all the various updates that need to be made on each particular machine on the network. For example, if an administrator using NDA specifies that the value of a particular registry entry on machine X needs to be updated to a value Y, then NDA will enter that command into the centralized administrative database. (As used herein, the terms "command", "instruction" and "request", and similar terms, are used interchangeably.) An agent process runs on each of the computers on the network, and periodically, for example every 15 minutes, the agent process queries the centralized administrative database to determine whether any new instructions have been entered for that particular computer. If so, then the instruction is downloaded and executed by the agent process. For example, if the agent running on machine X queries the database, it will learn that it is being instructed to modify the value of the particular registry entry to the value Y. The agent performs the specified operation on the local registry in machine X. When administrative agents start up on client machines, they start up in the same security context as the user's logon account. A problem arises because with the security features of Microsoft WindowsNT 3.5.1 and 4.0, the default permissions on certain registry entries do not permit ordinary users to modify such entries. That is, the user's logon account, and hence the administrative agent running on the user's computer system, lacks sufficient permission to modify certain registry entries. Accordingly, if the agent is instructed by the centralized administrative database to update one of these protected registry entries, the operation will fail. Conventional centralized network administration products, therefore, are not able to centrally administer all objects on WindowsNT 3.5.1 and higher client machines. Two conventional techniques exist for overcoming this problem. First, the Microsoft WindowsNT operating system comes with a tool, REGEDT32.EXE which the administrator can use from the administrator's central machine, to perform remote registry modifications on client computers. Because the administrator is logged on under the administrator account, the REGEDT32 program has sufficient permission to make the modifications desired even in highly protected registry entries on client machines. However, use of REGEDT32 is quite cumbersome. It is also quite impractical for large networks having thousands of client computer systems, because the registry entry modifications require the central administrative computer system to connect to each client computer individually and sequentially, make the required modification, and then disconnect. Even if the process could be automated, it is still quite slow to connect, modify and disconnect to each machine in sequence. Furthermore, such a technique runs counter to the overall model of network administration products such as NAN and NDA, in which most of the administrative work is offloaded to the client machines . A second conventional technique for centrally administering protected registry entries on client machines involves the use of the WindowsNT system policy downloader. The operation of the system policy downloader is described in "Simple Network Management Protocol (SNMP)", MSDN Library (October 1996) (CD-ROM) , incorporated herein by reference. When using the system policy downloader, the administrator creates a system policy file either on the client machines or in a central network location, indicating policies that are to be enforced, deleted, or left to the individual client user's discretion. Whenever a user logs on to a client machine on the network, the client automatically looks for a system policy file and, if detected, merges the policies specified therein into the client machine's registry. This too is not a viable solution for the problem of centralized administration of protected objects, because it will operate only to update registry policies. The WindowsNT registry also contains many other entries, other than policies, which may be protected and which need to be centrally administered. In addition, policy modifications specified using a system policy file do not take effect until client users log out and log back in. The actual registry updates therefore do not necessarily take place for hours or days, a situation which is unacceptable for many networks . Accordingly, there is a significant need for a new mechanism which will allow for centralized administration of protected objects on client computer systems. SUMMARY OF THE INVENTION According to the invention, roughly described, an intermediary process is installed on each client machine. Typically the intermediary process is installed as an NT service. When the client machine boots up, the intermediary service automatically starts up with the administrator name and password. The service thus carries administrator permissions. Thereafter, whenever the administrative agent on the client computer system unsuccessfully attempts to modify a registry entry in response to a command from the centralized administrative server, the agent passes a request to the intermediary service to perform the modification. The intermediary service is able to perform the desired operation because it has sufficient permission to do so even if the administrative agent does not. BRIEF DESCRIPTION OF THE DRAWINGS The invention will be described with respect to particular embodiments thereof, and reference will be made to the drawings, in which: Fig.l is a symbolic block diagram of a computer network incorporating the invention. Fig. 2 is a symbolic flow chart of the administrative agent process flow in an embodiment of the invention. Fig. 3 is a symbolic flow chart of the intermediary registry modification service process flow in an embodiment of the invention. Fig. 4 is a symbolic flow chart of an example series of steps that take place on a client machine. DETAILED DESCRIPTION Fig. 1 is a symbolic block diagram of a computer network 100 incorporating the invention. It includes client computer systems 110, 112, 114, 116, 118, 120, 122 and 124, all running WindowsNT Workstation 4.0, for example. Also connected to the network 100 is a centralized administration server 126, running WindowsNT Server 4.0. The network topology of Fig. 1 includes two subnets 128 and 130 connected together via a router 132, but the invention can be used with any network topology including local area networks (LANs) and wide area networks (WANs) . The central administration server 126 runs various conventional network administration programs, including one which is able to distribute software and install it remotely on the various client machines. This tool is used to install two programs on each client machine. The first is an administrative agent which periodically queries the administrative database on the central administrative server 126 and attempts to execute instructions specified for the client machine. The second is an intermediary process, called a registry modification service, which runs as an NT background service with administrator permissions on the client machine. As used herein, the term "process" refers to executing programs, parts of executing programs, NT "services", and so on. Fig. 2 is a symbolic flow chart illustrating the steps performed by the administrative agent running on the client machine. In a step 210, the agent performs its initialization functions. Among other things, step 210 includes locating the shared data directory which contains the database of administrative instructions. The agent enumerates all waiting job activity that matches the local machine's current logon user name and builds a list of things to be modified by the agent. These are essentially the instructions or commands from the centralized administrative server to the local client machine. In step 212, the agent determines whether there are any instructions pending in the administrative database for the local machine's current logon user name. If not, then the agent process goes to sleep for a fixed period of time, for example 15 minutes. When it awakes, it returns to step 212 to check for any new instructions. If there are instructions in the administrative database for the local machine's user name, then in step 214, an instruction is retrieved from the database. Part of the instruction includes an operation code, which indicates the type of operation which the agent is to perform. Not all operations relate to the registry, but those that do generally call for either adding, modifying, renaming or deleting a registry key or registry value. In step 216, in response to the instruction, the agent process switches on the operation code. For simplicity of illustration, only one branch of the switch is shown in Fig. 2, but it will be understood that each operation code or group of similar operation codes has its own branch. In step 218, the agent process attempts to perform the specified operation on the registry, using the standard WindowsNT application program interface (API) calls for registry modification. In a step 220, it is determined whether the operation has failed for insufficient permission. If the operation succeeded, then the end of the switch statement is reached in step 222 and the agent process returns to step 212 to determine whether there are any further instructions pending for the local client machine. The operation will not fail for insufficient permission, for example, if the target registry entry is not protected. If the target registry entry is protected, such that the agent process (running with the user's permissions) does not have sufficient permission to perform the operation specified on the registry entry, then the agent process makes a request to the intermediary registry modification service to perform the operation. Specifically, in step 224, the agent process fills in a data structure in a shared memory map shared with the registry modification service, with information about the desired operation and the desired object. Whereas the present embodiment uses a shared memory region for interprocess communication, it will be understood that other embodiments can use other forms of interprocess communication. In step 226, the agent process signals the registry modification service that a request is waiting. The agent process then enters a waiting state (step 228) until a return signal is received from the registry modification service, at which point control returns to the End Switch statement 222. The registry modification service is able to perform the requested operation on the specified object even if the administrative agent process is not, because the registry modification service is running with administrator permissions. The steps 218, 220, 224, 226 and 228 in Fig. 2 set forth the import, but necessarily the exact sequence of steps which the agent process performs with respect to each registry operation that can be specified in the administrative database. Appendix A hereto sets forth in C++ the actual steps which the agent performs. Table I lists the registry operations to which the agent process will respond. TABLE I The data structure which the agent process prepares in the memory map in step 224 in Fig. 2, for communication with the registry modification service, is as follows: typedef struct { // [Communication direc mt nAction; // [in] predefined action long IRe urn; // [out] return code WPARAM wParam; //[ιn]wparam info LPARAM lParam; // [in] lpara UINT Message ; // [m]message type HKEY hKey; //[m/out] registry key TCHAR szSubKey [0x800] ; //[in] sub key, 2k TCHAR szClass [MAX PATH] ; //[in] key class DWORD dwValue; // [m] value type, mSDK TCHAR szValue [ 0x800 ] ; //[m]value name, 2k DWORD cbData; //[in] data size BYTE bData [ 0x8000 ] ; //[in] data buffer, 32k J NDASRV DATA; The agent process specifies the particular operation which the registry modification service is to perform, in the field nAction in the above data structure. nAction can take on any of the values in the following Table II. TABLE II As mentioned, when the user boots up the client machine, the registry modification service starts with administrator permissions. The C++ language code that installs and starts the service is called NEFSERV, and is set forth in Appendix B hereto. Figure 3 is a flowchart symbolically illustrating the operation of the registry modification service itself, NDASERV. In an initialization step 310, among other things, the service creates a shared memory region known as a memory map. It is through this memory map, as well as through the normal Windows NT signaling functions, that the administrative agent program communicates with the registry modification service. After initialization, in step 312, the registry modification service waits for a request. When the administrative agent program signals the registry modification service that a request is pending, in step 314, in response to the request, the service retrieves the operation code of the request from the memory map. In step 316, it switches on the operation code. For simplicity of illustration, only one branch of the switch is shown in Fig. 3, but it will be understood that a separate branch exists for each operation code or group of similar operation codes. In step 318, the registry modification service performs the operation specified by the operation code, on the object (registry key) specified in the memory map. Because the registry modification service was started with the administrator user name and password, it has sufficient permission to perform whatever operation the central administrative server has requested on the local client registry. After the operation is performed, the end of the switch statement is reached in step 320 and in step 322, the registry modification service signals a result code back to the administrative agent program. The registry modification service then loops back to step 312 to wait for the next request. As mentioned in the above description, the registry modification service performs operations "in response to" requests from the local administrative agent process. As used herein, a given event is considered "responsive" to a predecessor event if the predecessor event influenced the given event . If there is an intervening processing step or time period, the given event can still be "responsive" to the predecessor event. If the intervening processing step combines more than one event, the result of the processing step is considered "responsive" to each of the event inputs . Appendix C sets forth the C++ language code for NDASERV, which is compiled and loaded with NEFSERV.CPP (Appendix B) . It will be appreciated that many of the Windows API calls made in the code listings of Appendices A, B and C are well known to a person of ordinary skill. In any event, they are described on the Microsoft Developer Network CD-ROM (October 1996) , incorporated by reference herein. Given the above mechanism, Fig. 4 is a flowchart of a sample process which might take place on one of the client machines administered by the central administration server 126. In step 410, when the user boots up the client workstation, the registry modification service illustrated in Fig. 3 automatically starts. The registry modification service has administrator permissions and runs in the background. The user subsequently logs on in step 411. In step 412, the administrative agent process of Fig. 2 also starts on the client machine, and downloads the first command from the central administrative server database. In step 414, the administrative agent unsuccessfully attempts to execute the operation specified in the command, on the local machine registry key(s) . In step 416, in response to such unsuccessful attempt, the administrative agent communicates a request to the registry modification service to execute the command. In step 418, the . registry modification service, which has sufficient permission to execute the command, performs the specified operation on the specified registry key(s) and signals a result code back to the administrative agent. The foregoing description of preferred embodiments of the present invention has been provided for the purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Obviously, many modifications and variations will be apparent to practitioners skilled in this art. For example, the invention can be used with other protected objects on a computer system aside from registry keys. The embodiments were chosen and described in order to best explain the principles of the invention and its practical application, thereby enabling others skilled in the art to understand the invention for various embodiments and with various modifications as are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the following claims and their equivalents. APPENDIX A NDAREG . CPP Excerpt from Administrative Agent Program ©1997 Symantec Corp . finclude "stdafx.h" Sinclude "ndalib.h" #ιfdef SYM_WIN32 ((include "nefserv.h" #endιf II II 111111 II 11 II II 1111111111111111111111111111111 lllll 11111111111 III 111 I I CRegistryKey CRegistryKey: :CRegιstryKey( ) : m_hKey( NULL ) { InitO; } CRegistryKey: : CRegistryKey! HKEY hKey, LPCTSTR pszSubKey, LPTSTR pszClass ) : m hKeyl NULL ) { Init O ; Open ( hKey, pszSubKey, pszClass ); CRegistryKey: : CRegistryKey ( HKEY hKey, UINT nResId, LPTSTR pszClass m_hKey( NULL ) ( InitO; // fetch subkey string from string-table CString strSubKey! nResId ); Open( hKey, strSubKey, pszClass ); CRegistryKey: : -CRegistryKey ( ) ( Close! ); I II I I I I I III 1111111111111111111111111111 void CRegistryKey: : Init ( ) { m_hKey = NULL; m_lStatus = ERROR_SUCCESS; fflfdef SYM__WIN32 m_dwValues = 0; m_dwSubKeys = 0; m_bQuerιed = FALSE; memse ( Sm_tιmeLastWrιte, 0, sizeof ( FILETIME )); mJiKeyTop = NULL m iNtMap = NULL m_hNtEvent = NULL m_pNtBuff = NULL #endιf /* Open */ BOOL CRegistryKey: : Open! HKEY hKey, LPCTSTR pszSubKey, LPTSTR pszClass ) { DWORD dwDisposition = 0; CStnngTokens strToken; CStnngExt strSubKey; #lfdef SYM_WIN32 m_hKeyTop = hKey; m_strSubKey = pszSubKey; m_strClass = pszClass; #endιf // invalid subkey if ( strToken. Parse ( pszSubKey, _T('\\') ) == 0 ) return FALSE; for ( int ι = 0; I < strToken. GetCount () ; ι++ ) { // close last subkey if ( ! Closed ) return FALSE; // add sub key separator if ( ! strSubKey. IsEmpty! ) ) strSubKey += _T(".\"); // add sub key separator strSubKey += strToken [ι]; #ιfdef SYM_WIN32 // create/open registry key SetLastError! RegCreateKeyEx! hKey, strSubKey, 0, pszClass, REG_0PTI0N_N0N__V0LATILE, KEY_ALL_ACCESS, NULL, _m_hKey, SdwDisposition )); if ( GetNtService! ) ) ( NDASRV_DATA* pData = (NDASRV_DATA* ) m_pNtBuff; pData->nType = NDASRV_REG_OPEN; STRCPY! pData->szSubKey, strSubKey RunNtService ( ) ; #else SetLastError! RegCreateKey! hKey, pszSubKey, _m_hKey )); #endιf if ( GetLastError! ) '= ERROR_SUCCESS ) return FALSE; return ( GetLastError! ) == ERROR SUCCESS ) ; ii 1111111111111111111111111 ii III i mi 1111 mi/in i ii 1111 ii 111 nm 111 III i mi I* Close */ BOOL CRegistryKey: : Close ( ) { if ( m_hKey == (HKEY (NULL ) return TRUE; SetLastError! RegCloseKey! mJiKey )); m_hKey = ( HKEY) NULL; return ( GetLastError! ) == ERROR SUCCESS ); } i III III III mi 11 III III III miiiii III 11 mm in III i mi i m III III / 1 ii 11 mi 11 /* SetValue */ BOOL CRegistryKey: : SetValue ( LPCTSTR pszName, DWORD dwValue ) { #lfdef SYM_WIN32 if ( IsValid!) ) SetLastError! RegSetValueEx ( m_hKey, pszName, 0, REG_DWORD, (LPBYTE)SdwValue, sizeof! DWORD ))); if ( GetNtService! ) ) ( NDAS V_DATA* pData = ( NDASRV_DATA* ) m_pNtBuff; pData->nType = NDASRV_REG_SETVALUE; pData->d Value = REG_DWORD; pData->cbData = sizeof! DWORD ); STRCPY! pData->szValue, pszName ); memcpy! pData->bData, (LPBYTE) idwValue, pData->cbData ); RunNtService! ) ; #else TCHAR szBuf [_MA__PATH] ; εpπntf ! szBuf , _T ( "%ld" ) , dwValue ) ; SetLastError ! RegSetValue ( m_hKey, pszName, REG_SZ , szBuf , STRLEN ! szBuf ) + 1 ) } ; Bendif return ( GetLastError! ) == ERROR SUCCESS ), BOOL CRegistryKey: : SetValue ( LPCTSTR pszName, LPCTSTR pszValue } { jflfdef SYM_WIN32 DWORD cbData = STRLEN ( pszValue ) + 1; #ιfdef UNICODE cbData = 2 * cbData; ff endif i f ( IsValid ! ) ) SetLastError! RegSetValueEx! m_hKey, pszName, 0, REG_SZ, (LPBYTE)pszValue, cbData )); if ( GetNtService!) ) { NDASRV_DATA* pData ( NDASRV_DATA* ) m_pNtBuf f ; pData->nType = NDASRV__REG_SETVALUE; pData->dwValue = REG_SZ; pData->cbData = cbData; STRCPY! pData->szValue, pszName ) ; memcpy! pData->bData, (LPBYTE)pszValue, pData->cbData RunNtService ( ) ; (felse SetLastError! RegSetValue! m_hKey, pszName, REG_SZ, pszValue, STRLEN! pszValue ) + 1 )); #endιf return ( GetLastError! ) == ERROR SUCCESS BOOL CRegistryKey: : SetValue! LPCTSTR pszName, LPVOID pData, DWORD dwSize ) #ιfdef SYM_WIN32 if ( IsValid!) ) SetLastError! RegSetValueEx! m_hKey, pszName, 0, REG_BINARY, (LPBYTE)pData, dwSize )); ιf ( GetNtService!) ) f NDASRV_DATA* pData = (NDASRV_DATA* ) m_pNtBu f; pData->nType = NDASRV_REG_SETVALUE; pData->dwValue = REG_BINARY; pData->cbData = dwSize; STRCPY! pData-. szValue, pszName ); memcpy! pData->bData, (LPBYTE)pData, pData->cbData RunNtService ( ) ; #else SetLastError! RegSetValue! m_hKey, pszName, REG_SZ, (LPCTSTR)pData, dwSize ) ) ; ϊendif return { GetLastError! ) == ERROR SUCCESS ); III i n i III ii i mi III mm mi ii i III iiim III III 111 III 11 III 11 mm mi i mi i / * QueryValue */ CStπng CRegistryKey: :QueryStπng ( LPCTSTR pszName ) ( CStπng strValue; // storage for result value TCHAR szValue [SYM_MAX_PATH] ; // storage for key value #ιfdef SYM_WIN32 DWORD dwType; // data returned from query call DWORD dwSize = SYM_MAX_PATH; // size of value buffer // retrieve key value if ( IsValid!) ) SetLastError! RegQueryValueEx ( m_hKey, pszName, NULL, SdwType, (LPBYTE) szValue, idwSize )); if ( GetNtService!) ) { NDASRV_DATA* pData = (NDASRV_DATA* ) m_pNtBuff; pData->nType = NDASRV__REG_QUERYVALUE; STRCPY! pData->szValue, pszName ); if ( RunNtService! FALSE )) memcpy! szValue, pData->bData, pData-. cbData ); CloseNtService ( ) ; (else long ISize = SYM_MAX_PATH; // retrieve key value SetLastError! RegQueryValue! m_hKey, pszName, szValue, ilSize )); #endιf if ( GetLastError! ) == ERROR_SUCCESS ) strValue = szValue; return strValue; } DWORD CRegistryKey: :QueryDWord( LPCTSTR pszName ) { DWORD dwValue = 0L; // storage for result value jflfdef SYM_WIN32 DWORD dwType; // type of data in registry key DWORD dwSize = sizeof! DWORD ); // data returned from query call // retrieve key value if ( IsValid!) ) SetLastError) RegQueryValueEx! m_hKey, pszName, NULL, sdwType, (LPBYTE) idwValue, idwSize )); if ( GetNtService!) ) { NDASRV_DATA* pData = (NDASRV_DATA* ) m_pNtBu f; pData-.nType = NDASRV_REG_QUERYVALUE; STRCPY! pData->szValue, pszName ); if ( RunNtService! FALSE )) memcpy! SdwSize, pData->bData, pData-.cbData CloseNtService ( ) ; else TCHAR szValue [SYM_MAX_PATH] long ISize = SYM_MAX_PATH; SetLastError! RegQueryValue! m_hKey, pszName, szValue, ilSize )); if ( GetLastError! ) == ERROR_SUCCESS ) dwValue = (DWORD)atoι! szValue ); #endιf return dwValue; / I I I I I I 11 III 11 I I I I II III III I I I I I I GetNumKeys DWORD CRegistryKey: : GetNumKeys ( ) { if ( QueryKey!) ) return m_dwSubKeys ; return 0L; i m / ii I II ii I I I I II mm i ii III / III III 11 II GetNumValues DWORD CRegistryKey: : GetNumValues ( ) ( if ( QueryKey! ) ) return m_dwValues; return 0L; mi 111 III 11 I II I II ill ill I II nm I I I II I i II QueryKey BOOL CRegistryKey: : QueryKey! ) { if ( m_bQuerιed ) return TRUE; if ( IsValid!) ) SetLastError! RegQuerylnfoKey! m_hKey, NULL, NULL, NULL, _m_dwSubKeys , NULL, NULL, _m_dwValues, NULL, NULL, NULL, &m timeLastWπte )); if ( GetNtService!) ) { NDASRV_DATA* pData = (NDASRV_DATA* ) m_pNtBuff; pData-. nType = NDASRV REG QUERYINFOKEY; ιf ( RunNtService! FALSE )) m_dwSubKeys = pData->cbData; m_dwValues = pData->dwValue; memcpy ! _m_tιmeLastWnte, pData->bData , si zeof ! FILETIME ) ) , CloseNtService ( ) ; } mjDQueried = ( GetLastError!) == ERROR_SUCCESS ); return m bQueπed; } m 11 mi mm in mi III III im/iii/i i I I RenameValue BOOL CRegistryKey: : RenameValue! LPCTSTR pszName, LPCTSTR pszNewName ) { DWORD dwType = 0; DWORD cbData = 0; LPBYTE lpBuf = NULL; // don't allow rename to a name that already exists if ( RegQueryValueEx! m_hKey, pszNewName, NULL, NULL, NULL, NULL ) ERROR_SUCCESS ) { return ERROR_ALREADY_EXISTS; ) SetLastError! RegQueryValueEx! m_hKey, pszName, NULL, idwType, NULL, icbData ) ) ; if (( GetLastError!) == ERROR_SUCCESS ) && ( cbData > 0 )) { lpBuf = new BYTE [cbData] ; SetLastError! RegQueryValueEx! m_hKey, pszName, NULL, idwType, lpBuf, &cbData ) ) ; } if ( GetLastError!) == ERROR_SUCCESS ) SetLastError! RegSetValueEx! m_hKey, pszNewName, 0, dwType, lpBuf, cbData ) ) ; if ( GetLastError!) == ERROR_SUCCESS ) DeleteValue! pszName ); if ( lpBuf ) delete [] lpBuf; return ( GetLastError!) == ERROR SUCCESS I I I l l l l I I I II I 11 II ll lllll/lll II I I II III I I 11 EnumKey BOOL CRegistryKey: : EnumKey! DWORD dwlndex, CStringS strName ) ( TCHAR szKeyName[SYM_MAX_PATH] ; if ( IsValid!) ) SetLastError (RegEnumKey(m_ .Key, dwlndex, szKeyName, SYM_MAX_PATH) ) ; if ( GetNtService!) ) ( NDASRV_DATA* pData = (NDASRV_DATA* ) m_pNtBuff; pData->nType = NDASRV_REG_ENUMKEY; pData->dwValue = dwlndex; lf ( RunNtService! FALSE )) memcpy! S.szKeyName, pData->bData, pData->cbData ); CloseNtService ( ) ; if ( GetLastError!) == ERROR_SUCCESS { strName = szKeyName; return TRUE; strName . Empty( ) ; return FALSE; mi i III mi 111 ii i mm / m mi mini II EnumValue BOOL CRegistryKey: : EnumValue ( DWORD dwlndex, CStrings strName ) { DWORD dwSize = SYM_MAX_PATH; TCHAR szValueName [SYM_MAX_PATH] ; if ( IsValid! ) ) SetLastError! RegEnumValue ( m_hKey, dwlndex, szValueName, &dwSιze, NULL, NULL, NULL, NULL ) ) ; if ( GetNtService!) ) { NDASRV_DATA* pData = (NDASRV_DATA* ) m_pNtBuff; pData->nType = NDASRV_REG_ENUMVALUE; pData->dwValue = dwlndex; pData->cbData = SYM MAX PATH; if ( RunNtService! FALSE )) memcpy! SszValueName, pData->bData, pData->cbData ) CloseNtService ( ) ; if ( GetLastError!) == ERROR_SUCCESS ) { strName = szValueName; return TRUE; strName. Empty ( return FALSE; mi miiiiin minim III mm mm // DeleteKey LONG CRegistryKey: : DeleteKey! HKEY hKey, LPCTSTR pszSubKey ) { SetLastError! RegDeleteKey ( hKey, pszSubKey )); if ( GetLastError! ) == ERROR_SUCCESS return GetLastError! ); HKEY hKeyTgt; LONG lResult; lResult = RegOpenKeyEx ( hKey, pszSubKey, 0, KEY_ENUMERATE_SUB_KEYS | KEY_QUERY_VALUE | KEY_WRITE, ShKeyTgt if ( lResult == ERROR SUCCESS ) OSVERSIONINFO verlnfo; verlnfo.dwOSVersionlnfoSize = sizeof! OSVERSIONINFO ); if ( IGetVersionEx ( _ erlnfo )) return (LONG) :: GetLastError () ; // recurse for non Win 95 platforms if ( verlnfo. dwPlatformld != VER_PLATFORMSY__WIN32_WINDOWS ) ( DWORD dwKeys; lResult = RegQuerylnfoKey! hKeyTgt, NULL, NULL, NULL, idwKeys, NULL, NULL, NULL, NULL, NULL, NULL, NULL if ( lResult != ERROR_SUCCESS ) return lResult; for ( DWORD dwlndex = dwKeys; dwlndex > 0; dwlndex- { TCHAR szKey[SYM_MAX_PATH] ; DWORD dwSize = sizeof! szKey ); lResult = RegEnumKeyEx ( hKeyTgt, dwlndex - 1, szKey, SdwSize, NULL, NULL, NULL, NULL ); if ( lResult == ERROR_SUCCESS ) DeleteKey! hKeyTgt, szKey ); lResult = RegCloseKey! hKeyTgt ); if ( lResult != ERROR_SUCCESS ) return lResult; lResult = RegDeleteKey ( hKey, pszSubKey ); if ( GetNtService!) ) { NDASRV_DATA* pData = (NDASRV_DATA* ) m_pNtBuff; pData->nType = NDASRV_REG_DELETEKEY; pData->hKey = m_hKeyTop; pData->dwValue = dwType; pData->cbData = dwSize; STRCPY! pData->szSubKey, m_strSubKey ); memcpy! pData->bData, (LPBYTE) lpBuf, pData->cbData STRCPY! pData->szValue, pszNewName ); RunNtService ( return lResult; i imiiiimi mm III nm III III mm // CopyKey LONG CRegistryKey: :CopyKey( HKEY hKey, LPCTSTR pszSubKey, HKEY hNewKey, LPCTSTR pszNewSubKey ) ( LONG lResult; HKEY hKeySrc, hKeyTgt; lResult = RegOpenKeyEx! hKey, pszSubKey, 0, KEY_READ, ShKeySrc ); if ( lResult != ERRORJ3UCCESS ) return lResult; TCHAR szClass[SYM_MAX_PATH] ; DWORD cbClass = sizeof! szClass ); // get info required to recreate key lResult = RegQuerylnfoKey! hKeySrc, szClass, icbClass, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL, NULL ) ; if ( lResult '= ERROR_SUCCESS ) { RegCloseKey! hKeySrc ); return lResult; DWORD dwDisposition; // create new key lResult = RegCreateKeyEx! hNewKey, pszNewSubKey, 0, szClass, REG_OPTION_NON_VOLATILE,KEY_WRITE,NULL, ShKeyTgt, SdwDisposition) ; f ( lResult ι= ERROR_SUCCESS ) { RegCloseKey! hKeySrc ); return lResult; ) else if ( dwDisposition ι= REG_CREATED_NEW_KEY ) { // fail if the target key already exists RegCloseKey! hKeySrc ) ; RegCloseKey! hKeyTgt ); return ERROR_ALREADY__EXISTS; ) DWORD dwKeys, dwValues; // how many values and sub-keys to copy? lResult = RegQuerylnfoKey! hKeySrc, NULL, NULL, NULL, SdwKeys, NULL, NULL, SdwValues, NULL, NULL, NULL, NULL ); if ( lResult ι= ERROR_SUCCESS ) return lResult; // copy all values for ( DWORD dwlndex = 0; dwlndex < dwValues; dwlndex+t ) { TCHAR szValue [SYM_MAX_PATH] ; DWORD dwSize = sizeof! szValue ); DWORD dwType = 0; DWORD cbData = 0; LPBYTE lpBuf = NULL; lResult = RegEnumValue ( hKeySrc, dwlndex, szValue, _dwSιze, NULL, sdwType, NULL, ScbData ); if ( lResult '= ERROR_SUCCESS ) continue; if ( cbData > 0 ) { lpBuf = new BYTE [cbData] ; dwSize = sizeof! szValue lResult = RegEnumValue! hKeySrc, dwlndex, szValue, SdwSize, NULL, SdwType, lpBuf, ScbData ); ) RegSetValueEx! hKeyTgt, szValue, 0, dwType, lpBuf, cbData ); if lpBuf ) delete [ lpBuf; // copy all sub-keys for ( dwlndex = 0; dwlndex < dwKeys; dwlndex++ ) { TCHAR szKey [ SYM_MAX_PATH] ; DWORD dwSize = sizeof! szKey ); lResult = RegEnumKeyEx ( hKeySrc, dwlndex, szKey, idwSize, NULL, NULL, NULL, NULL ) if ( lResult == ERROR_SUCCESS ) CopyKey! hKeySrc, szKey, hKeyTgt, szKey } // cleanup lResult = RegCloseKey! hKeySrc ); if ( lResult ι= ERROR ^ SUCCESS ) return lResult; return RegCloseKey! hKeyTgt ); nm / mm m III III i III i III III 111111 / I I MoveKey LONG CRegistryKey: :MoveKey( HKEY hKey, LPCTSTR pszSubKey, HKEY hNewKey, LPCTSTR pszNewSubKey ) { LONG lResult = CopyKey! hKey, pszSubKey, hNewKey, pszNewSubKey ); if ( lResult == ERROR_SUCCESS ) return DeleteKey! hKey, pszSubKey ); return lResult; } #endιf // SYM WIN32 III 111 mm 11 ii i / III III mm ill 11 nil/mill mm i mm III III illinium /* DeleteValue */ BOOL CRegistryKey: : DeleteValue ( LPCTSTR pszName ) { ftifdef SYM_WIN32 if ( IsValid!) ) SetLastError! RegDeleteValue ( m_hKey, pszName )); if ! GetNtService!) ) { NDASRV_DATA* pData = (NDASRV_DATA* ) m_pNtBuff; pData->nType = NDASRV_REG_DELETEVALUE; STRCPY! pData->szValue, pszNewName ); RunNtService!); ) #else SetLastError! RegDeleteKey ( m_hKey, pszName )); #endιf return ( GetLastError! ) == ERROR 3UCCESS ); ) #ιfdef SYM_WIN32 BOOL CRegistryKey: : ImtNtService ( ) ( // have already got service if ( m_hNtMap '= NULL ) return TRUE; OSVERSIONINFO verlnfo; verlnfo. dwOSVersionlnfoSize = sizeof! OSVERSIONINFO ); if ( 'GetVersionEx ( Sverlnfo )) return FALSE; // is the NT registry service available if ( verlnfo. dwPlatformld ι= VER_PLATFORMSYM_WIN32_NT return FALSE; // get the handle to the memory map file HANDLE m_hNtMap = OpenFileMapping ( FILE_MAP__WRITE | FILE_MAP_READ, FALSE, NDASRVJAP ); // get the handle to the defined event HANDLE m -iNtEvent = OpenEvent! EVENT ALL ACCESS, FALSE, NDASRV EVENT if m hNtEvent NULL m_hNtMap = NULL; return FALSE; return ( m_hNtMap '= NULL ); BOOL CRegistryKey: : GetNtService ( ) { // no need to get the service if ( m_hKey '= NULL SS GetLastError! ) == ERROR_SUCCESS return FALSE; // cant get the service if ( ' ImtNtService! ) ) return FALSE; // clear last m_pNtBuff = NULL; // get the file buffer m_pNtBuff = MapViewOfFile ( mJ.NtMap, FILE MAP WRITE | FILE MAP READ, o, ~ " " ~ o, sizeof! NDASRV_DATA )); if ( m ^ pNtBuff == NULL ) return FALSE; NDASRV_DATA* pData = (NDASRV_DATA* ) m_pNtBuff; pData->hKey = m__hKeyTop; STRCPY! pData-. szSubKey, m_strSubKey ); return TRUE; ) BOOL CRegistryKey: : RunNtService ( BOOL bClose ) ( if ( m_pNtBuff == NULL ) return FALSE; UnmapViewOfFile! m_pNtBuff ); SetEvent ( m_hNtEvent ) ; WaιtForSmgleOb 3 ect ( m_hNtEvent, INFINITE ); if ( 'GetNtService!) ) return FALSE; SetLastError! ( (NDASRV_DATA* ) m_pNtBuff ) -MReturn ); If ( bClose ) CloseNtService ( ) ; return ( GetLastError! ) == ERROR SUCCESS ); void CRegistryKey: :CloseNtServιce ( ) { if ( m_pNtBuff '= NULL ) UnmapViewOfFile ( m_pNtBuff ), // clear last m_pNtBuff = NULL; Jendif APPENDIX B NEFSERV.CPP Service Installation and Control ©1997 Symantec Corp . ((include "platform. h" ((include "nefserv . h" ((include "nacutil . h" ((include <process.h> /* _begιnthreadex, _endthread */ HINSTANCE ghlnstance = NULL; Kifndef NET_SERVICE // Enforce load ordering for SYMNET service ((include "symnet.h" #else HINSTANCE ghSymnet = NULL; #endιf ((define MSG_GENERIC 0x000003E8L HANDLE termmateEvent NULL; BOOL pauseService FALSE; BOOL runningService FALSE; HANDLE threadHandle 0; SERVICE_STATUS_HANDLE serviceStatusHandle; char szServiceName [ 64] ; char szServiceDescription [64] ; char szServiceExe [10] ; typedef BOOL SYM_EXPORT (WINAPI * LPFN_MAKECONNECTIONPROC) LPFN_MAKECONNECTIONPROC lpfnMakeConnection; ftifdef NET_SERVICE extern BOOL WINAPI NETSERVCreateSYMXPCProcess () ; (tendif till WinMain II II Main Entry Point II- it WINAPI WinMain! HINSTANCE hlnstance, HINSTANCE hPrevInstance, LPTSTR lpCmdLine, int nCmdShow HINSTANCE hNAccessDll = NULL; char szServιcePath[256] ; char szUser[32] = ""; char szPassword[32] = ""; BOOL bManualStart = FALSE; // Assume Automatic start type. int ι = 0; BOOL blnstall = FALSE; BOOL bRemove = FALSE; BOOL bStart = FALSE; LPTSTR pCmd; BOOL bDomainSupplied = FALSE; ghlnstance = hlnstance; if (pCmd = strchr ( lpCmdLme, ' / ') ) { *pCmd++; // ##IPE BEGIN — DO NOT TRANSLATE if (STRNICMP (pCmd, "INSTALL", 7) == 0) blnstall = TRUE; else if (STRICMP (pCmd, "REMOVE") == 0) bRemove = TRUE; else if (STRICMP (pCmd, "START") == 0) bStart = TRUE; // (JffIPE END -- DO NOT TRANSLATE // if we have more than one parameter // assume we should start the service if (strchr (pCmd, '/') ) bStart = TRUE; GetServiceNameAndDescription (szServiceName, szServiceDescription, szServiceExe ) ; GetModuleFileName (GetModuleHandle (szServiceExe) , szServicePath, sizeof ( szServicePath) ) ; if (blnstall) { LPTSTR pPassword = STRCHR ( lpCmdLme, _T (',')) ; if (pPassword) { *pPassword++ = _T('\0'); LPTSTR pStartType = STRCHR (pPassword, _T (',')) if (pStartType) { *pStartType++ = _T('\0'); // ## IPE DO NOT TRANSLATE bManualStart = (STRICMP (pStartType, T ( "MANUAL" ) ) == 0); // ##IPE END -- DO NOT TRANSLATE // unencrypt password if necessary while (*pPassword ι= τ('\0')) if (*pPassword > 128) szPasswordji] = *pPassword + 12E else szPassword [l] = *pPassword; ι++; pPassword++; LPTSTR pUser = STRCHR! lpCmdLme, ':'); if (pUser) { pUser+÷; strcpy (szUser,pUser ) ; // did the user supply a domain prefix ι = 0; while (szUserfi] '= '\0') if (szUserfi] == '\\' ii szUser[ι+l] == '\\') { bDomainSupplied = TRUE; break; // Use default domain if none supplied if ( i bDomainSupplied ii (*pUser > = '\0')) strcpy (szUser, " . \\" ) ; strcat (szUser,pUser ) ; InstallService ( szServicePath, !szUser[0] == _T('\0')) ? NULL : szUser, (szPassword[0] == _T('\0')) ? NULL : szPassword, bManualStart) ; } if (bRemove) RemoveService ( ) ; i (bStart) StartServiceNow! ) ; return NOERR; Sifndef NET_SERVICE hNAccessDll = LoadLibrary (NEFACCESS_MODULENAME ) ; if (hNAccessDll) // (ffflPE BEGIN lpfnMakeConnection = (LPFN_MAKECONNECTIONPROC)GetProcAddress (hNAccessDll, "?MakeConnectιon@@YGHXZ" ) ; // (fftlPE END if (lpfnMakeConnection) lpfnMakeConnection ( ) ; FreeLιbrary(hNAccessDll) ; 1 (tendif StartOurService ( szServiceName) ; return NOERR; // // FUNCTION: InstallService // void SYM_EXPORT WINAPI InstallService! LPSTR IpServicePath, LPSTR lpUser, LPSTR lpPassword, BOOL bManualStart ) { SC_HANDLE hService, schSCM; char buf [200] ; HKEY hk; char szServιcePath[200] ; strcpy (szServicePath, IpServicePath) ; schSCM = : :OpenSCManager (NULL, // local machine NULL, // ServicesActive database SC_MANAGER_CREATE_SERVICE) ; // access to create if (! schSCM) return; // Create the service DWORD dwStartType = (bManualStart) ? SERVICE_DEMAND_START : SERVICE_AUTO_START; hService = : :CreateServιce ( schSCM, // handle to service control manager database szServiceName, // pointer to name of service to start szServiceDescription, // pointer to display name SERVICE_ALL__ACCESS, // type of access to service SERVICEJflIN32__OWN_PROCESS, // type of service dwStartType, // when to start service SERVICE_ERROR_NORMAL, // severity if service fails to start IpServicePath, // pointer to name of binary file NULL, // pointer to name of load ordering group NULL, // pointer to variable to get tag identifier #ιfdef NET_SERVICE NULL, #else NET_SERVICE_NAME _T ( "\ 0\ 0" ) , // SYMNET service dependency. ftendi f lpUser, // pointer to account name of service lpPassword ) ; // pointer to password for service account if ( ! hService) DWORD err = GetLastError!); if (err == ERROR SERVICE EXISTS) // Assume success ERROR SUCCESS; // Service exists, open service // and change its configuration. SC HANDLE schService : :OpenServιce (schSCM, szServiceName, SERVICE_CHANGE_CONFIG) ; // Properly configure service. // If the service is already running, the changes do not // take effect until the service is stopped. if (schService ) if (' ChangeServiceConflg ( schService, // handle to service SERVICE_WIN32_OWN_PROCESS, // service Type dwStartType, // when to start service SERVICE_ERROR__NORMAL, // ErrorControl IpServicePath, // service's binary pathname NULL, // load ordering group name NULL, // pointer to variable to get tag ldentifler Kifdef NET SERVICE NULL, #else // SYMNET service dependency. NET SERVICE NAME T("\0\0"), (tendif lpUser, // NT user account lpPassword, // password szServiceDescription) // name of service err = GetLastError ( ) ; else err = GetLastError!); : :CloseServιceHandle (schService) ; if (err '= ERROR SUCCESS) : :CloseServιceHandle (schSCM) ; return; if (hService) CloseServiceHandle (hService } ; CloseServiceHandle (schSCM) ; // install the eventlog information in the // registry // ##IPE BEGIN wsprintf (buff, "SYSTEM\\CurrentControlSet\\Servιces\\EventLog\\Applιcatιon\\%s", szServiceName) ; RegCreateKey (HKEY_LOCAL_MACHINE, buff, hk) ; RegSetValueExfhk, "EventMessageFile" , 0, REG_EXPAND_SZ, (CONST BYTE* ) szServicePath, strlen ( szServicePath) + 1); DWORD dwData = EVENTLOG_ERROR_TYPE I EVENTLOG_WARNING_TYPE | EVENTLOG_INFORMATION_TYPE; RegSetValueEx (hk, "TypesSupported" , 0, REG_DWORD, (CONST BYTE*) dwData, sizeof (DWORD) ) ; // ##IPE END RegCloseKey(hk) ; // // FUNCTION: RemoveService // / / void SYM_EXPORT WINAPI RemoveService ( ) { SC_HANDLE hService, schSCM; SERVICE_STATUS serviceStatus; BOOL bResult; schSCM = OpenSCManager (0, 0, SC MANAGER CREATE SERVICE) hService = OpenServιce( schSCM, szServiceName, SERVICE_ALL_ACCESS I DELETE); if (hService) { // if service is still running // shut it down before deleting bResult = QueryServiceStatus (hService, iserviceStatus ) ; if (bResult Si serviceStatus.dwCurrentState '= SERVICE_STOPPED) ( ControlService (hService, SERVICE_CONTR0L_STOP, iserviceStatus) DeleteService (hService) ; CloseServiceHandle (hService) ; CloseServiceHandle (schSCM) ; // // FUNCTION: StartServiceNow // void SYM_EXPORT WINAPI StartServiceNowf ) { SC HANDLE hService, schSCM; schSCM = OpenSCManager ( 0, 0, SC_MANAGER_CREATE_SERVICE) ; hService = OpenService! schSCM, szServiceName, SERVICE_ALL_ACCESS I SERVICE_START ) , StartService (hService, 0,NULL) ; CloseServiceHandle (hService) ; CloseServiceHandle ( schSCM) ; // // FUNCTION: ErrorHandler // void SYM_EXPORT WINAPI ErrorHandler ( char *sl, char *s2, char* s3, DWORD err, WORD wServiceType) HANDLE , hEventSource; const char* ps [3]; int iStr = 0; int I; ps[0] = si; ps[l] = s2; ps[2] = s3; for (ι=0; ι<3; ι++) if (ps[ι] '= NULL) ιStr++; } hEventSource = RegisterEventSource (NULL, szServiceName) ; ReportEvent (hEventSource, EVENTLOG_INFORMATION_TYPE, 0,MSG_GENERIC, ULL, ιStr,0,ps, NULL); Exit Process (err) ; // // FUNCTION: ImtService // // BOOL ImtService ( ) Jifdef NET_SERVICE if ( NETSERVCreateSYMXPCProcess!) == FALSE ) return FALSE; else f runningService = TRUE; return TRUE; ((else unsigned int id; // Instead of CreateThread threadHandle = ( HANDLE )_begmthreadex (NULL, 0, ServiceThread, NULL, 0, Sid) ; if (threadHandle == 0) return FALSE; else runmngService = TRUE; return TRUE; (f endif I ! / / FUNCTION : SendStatusToSCM // // BOOL SendStatusToSCM (DWORD dwCurrentState, DWORD dwWm32ExιtCode, DWORD dwServiceSpecificExitCode, DWORD dwCheckPoint, DWORD dwWaitHint) i WORD wResult; SERVICE_STATUS serviceStatus; serviceStatus. dwServiceType = SERVICE_WIN32_OWN_PROCESS; serviceStatus .dwCurrentState = dwCurrentState; if (dwCurrentState == SERVICE_START_PENDING) serviceStatus .dwControlsAccepted = 0; else serviceStatus . dwControlsAccepted = SERVICE__ACCEPT_STOP | // SERVICE_ACCEPT_PAUSE_CONTINUE | SERVICE ACCEPT SHUTDOWN; ~ if (dwServiceSpecificExitCode == 0) serviceStatus .dwWm32ExιtCode = dwWm32ExιtCode; else serviceStatus.dwWm32ExιtCode = ERROR_SERVICE_SPECIFIC_ERROR; serviceStatus .dwServiceSpecificExitCode = dwServiceSpecificExitCode; serviceStatus .dwCheckPoint = dwCheckPoint; serviceStatus .dwWaitHint = dwWaitHint; wResult = SetServiceStatus (serviceStatusHandle, serviceStatus); if d wResult ) StopService ( ) ; return ( BOOL ) wResult; ) / / // FUNCTION: ServiceCtrlHandler // // VOID ServiceCtrlHandler (DWORD controlCode) ( DWORD currentState = 0; WORD wResult; switch ( controlCode ) { case SERVICE_CONTROL_STOP : currentState = SERVICE_STOP_PENDING; wResult = SendStatusToSCM ( SERVECE_STOP_PENDING, NO_ERROR, 0, 1, 15000) StopService ( ) ; return; case SERVICE_CONTROL_PAUSE: if (runmngService Si IpauseService) { wResult = SendStatusToSCM (SERVICE_PAUSE_PENDING,NO_ERROR, 0, i.,1000) PauseService ( ) ; currentState = SERVICE PAUSED; break; case SERVICE_CONTROL_CONTINUE: if (runmngService is pauseService) ( wResult=SendStatusToSCM ( SERVICEJCONTINUE_PENDING, NO_ERROR, 0,1,1000), ResumeService ( ) ; currentState = SERVICE_RUNNING; } break; case SERVICE_CONTROL_INTERROGATE : break; case SERVICE_CONTROL_SHUTDOWN: return; default : break; } SendStatusToSCM (currentState, NO_ERROR, 0, 0, 0); // FUNCTION: terminate // VOID terminate (DWORD error) { if ( terminateEvent ) CloseHandle (terminateEvent) ; if (serviceStatusHandle) SendStatusToSCM (SERVICE_STOPPED, error, 0, 0, 0) if (threadHandle) CloseHandle (threadHandle ) ; // FUNCTION: ServiceMam // // VOID ServiceMam (DWORD argc, LPTSTR *argv) { WORD wResult; serviceStatusHandle = RegisterServiceCtrlHandler ( szServiceName, (LPHANDLER FUNCTION ) ServiceCtrlHandler ) ; if (! serviceStatusHandle) < terminate (GetLastError ( ) ) ; return; ) wResult = SendStatusToSCM (SERVICE_START__PENDING, NO_ERROR, 0, 1, 1000) if ('wResult) { terminate (GetLastError ( ) ) ; return; } terminateEvent = CreateEvent (0, TRUE, FALSE, 0); if (! terminateEvent ) ( terminate (GetLastError ( ) ) ; return; wResult = SendStatusToSCM (SERVICE_START_PENDING, NO_ERROR, 0, 2, 1000), if ('wResult) f terminate ( GetLastError ( ) ) ; return; } wResult = SendStatusToSCM ( SERVECE_START_PENDING, NO_ERROR, 0, 3, 5000), if ('wResult) ( terminate (GetLastError ( ) ) ; return; } wResult = ImtService () ; if ('wResult) { terminate (GetLastError ( ) ) ; return; } wResult = SendStatusToSCM ( SERVICE_RUNNING, N0_ERROR, 0, 0, 0); if ('wResult) { terminate (GetLastError ( ) ) ; return; WaιtForSιngleOb 3 ect (terminateEvent, INFINITE), terminate ( 0) ; PSECURITY ^ DESCRIPTOR AllocNullSecurityDescriptor (void) { PSECURITY_DESCRIPTOR pSD=NULL; pSD=(PSECURITY__DESCRIPTOR) malloc ( SECURITY_DESCRIPTOR_MIN_LENGTH) ; if (pSD==NULL) { return (NULL) ; memsetl (void * ) pSD, 0, SECURITY_DESCRIPTOR_MIN_LENGTH ) ; // INITIALIZE IT if ( 'InitializeSecurityDescriptor (pSD, SECURITY_DESCRIPTOR_REVISION) ) { free(pSD) ; return (NULL) ; if ( 'SetSecurityDescπptorDacl (pSD,TRUE, ( PACL) NULL, FALSE) free(pSD) ; return (NULL) ; return (pSD) ; APPENDIX C NDASERV.CPP Registry Modification Service ©1997 Symantec Corp . ♦include "platform. h" ((include "nefserv.h" extern HINSTANCE ghlnstance; extern HANDLE terminateEvent; extern BOOL pauseService; extern BOOL runmngService; extern HANDLE threadHandle; // IPE DO NOT TRANSLATE char szNDAService [ ] = "NortonDesktopAdministrator" ; char szNDADescription [ ] = "Norton Desktop Administrator Service" char szNDAExe[] = "ndaserv"; // IPE DO NOT TRANSLATE // // local protos // PSECURITY ^ DESCRIPTOR AllocNullSecurityDescriptor (void) ; static BOOL CheckKeyl HKEY hKey ); static long _RegDeleteKey ( HKEY hKey, LPCTSTR pszSubKey ); / // FUNCTION: StartOurService // // BOOL SYM EXPORT WINAPI StartOurService ( LPSTR szServiceName) strcpy! szServiceName, szNDAService ); return (StartServiceCtrlDispatcher ( serviceTable // // FUNCTION: StopService // // VOID StopService ! ) { runmngService = FALSE; SetEvent ( terminateEvent ) // // FUNCTION: PauseService // // VOID PauseService!) pauseService = TRUE; SuspendThread ( threadHandle ), // FUNCTION: ResumeService // / VOID ResumeService!) pauseService = FALSE; ResumeThread ( threadHandle ); / // FUNCTION: ServiceThread // // UINT WINAPI ServiceThread (LPVOID IpvParam) ( HANDLE hMapFile; HANDLE hWakeUp; HANDLE hReturn; PSECURITY_DESCRIPTOR pSD; SECURITY_ATTRIBUTES sa = (0); NDASRV_DATA* pData; // Fill out security descriptor pSD = AllocNullSecurityDescriptor!; sa.nLength = sizeof (sa); sa. IpSecurityDescriptor = pSD; // crerate new map file hMapFile = CreateFileMapping ( (HANDLE) OxFFFFFFFF, Ssa, PAGEJ EADWRITE , 0 , si zeof ( NDASRV_DATA ) , NDASRV_MAP ) ; // create the even to check for hWakeUp = CreateEvent ( Ssa, FALSE, FALSE, NDASRV_EVENT_SND ) ; // create the even to check for hReturn = CreateEvent ( Ssa, FALSE, FALSE, NDASRV_EVENT_ACK ) ; // must have failed if ( hMapFile == NULL | | hWakeUp == NULL I I hReturn == NULL ) return 0; while ( hMapFile ) { WaιtForSιngleOb 3 ect ( hWakeUp, INFINITE / / verify the can get buf fer pData = (NDASRV_DATA* )MapVιewOf Fιle ( hMapFile, FILE_MAP_WRITE | FILE_MAP_READ, 0 , 0 , sizeof ( NDASRV DATA )); // cant get the file mapping try again if ( pData == NULL ) SetEvent ( hReturn continue; // default to worked long IRet = ERROR_SUCCESS; BOOL bRet = TRUE; HKEY hKey = NULL; DWORD dwTmp; // invalid key if ( !CheckKey( pData->hKey ) { pData-MReturn = IRet; SetEventf hReturn ); continue ; // doing a registry item if ( pData->hKey ) { IRet = RegCreateKeyEx ( pData->hKey, pData->szSubKey, 0, NULL, REG_0PTION_NON_VOLATILE, KEY_ALL_ACCESS, NULL, ShKey, SdwTmp ) ; // dont process if ( IRet ι= ERROR_SUCCESS ) { pData-.lReturn = IRet; SetEvent ( hReturn ) ; continue; switch ( pData-. nAction ) { case NDASRV_REG _PEN: break; case NDASRV__REG_SETVALUE : IRet = RegSetValueEx ! hKey, pData-.szValue, 0, pData->dwValue, ( LPBYTE ) pData->bData , pData->cbData break; case NDASRV__REG_DELETEKEY: RegCloseKey! hKey ); hKey = NULL; IRet = _RegDeleteKey(pData->hKey, pData->szSubKey ); break; case NDASRV_REG_DELETEVALUE: IRet = RegDeleteValue! hKey, pData->szValue ); break; case NDASRV_REG_QUERYVALUE: IRet = RegQueryValueEx! hKey, pData-. szValue, NULL, SpData->dwValue, (LPBYTE)pData->bData, SpData->cbData ) ; break; case NDASRV_REG_QUERYINFOKEY: IRet = RegQuerylnfoKey! hKey, pData-.szClass, NULL, NULL, SpData-.cbData, NULL, NULL, SpData->dwValue, NULL, NULL, NULL, (PFILETIME)ipData->bData ); break; case NDASRV_REG_ENUMKEY: IRet = RegEnumKey! hKey, pData->dwValue, (LPTSTR)pData->bData, pData->cbData break; case NDASRV_REG_ENUMVALUE: IRet = RegEnumValue! hKey, pData->dwValue, ( LPTSTR )pData->bData, SpData-.cbData, NULL, NULL, NULL, NULL ); break; // non reg error if ( 'bRet ) IRet = GetLastError!); // close if needed if ( hKey ) RegCloseKey! hKey ); // save the return code pData-. IReturn = IRet; // release the mapping UnmapViewOfFile ( (LPVOID)pData ) ; // signal NDA that we are done SetEvent ( hReturn ) ; return 0; / / // FUNCTION: GetServiceNameAndDescription // BOOL SYM_EXPORT WINAPI GetServiceNameAndDescription (LPSTR szServiceName, LPSTR szServiceDescription, LPSTR szServiceExe) { strcpy(szServiceName, szNDAService) ; strcpy (szServiceDescription, szNDADescription) ; strcpy (szServiceExe, szNDAExe) ; return NOERR; ) // // FUNCTION: CheckKey // // Verify that the key is valid to open // static BOOL CheckKeyf HKEY hKey ) { if ( hKey == 0 ) return TRUE; else lf ( hKey == HKEYJ_LASSES_ROOT ) return TRUE; else if ( hKey == HKEY_CURRENT_USER ) return TRUE; else if ( hKey == HKEY_LOCAL_MACHINE return TRUE; else if ( hKey == HKEYJJSERS ) return TRUE ; return FALSE; / / // FUNCTION: _RegDeleteKey // // NT will not delete the sub keys // static long ^ RegDeleteKey ( HKEY hKey, LPCTSTR pszSubKey ) // try and 3 ust deleting the key LONG IRet = RegDeleteKey! hKey, pszSubKey // worked done if ( IRet == ERROR_SUCCESS ) return IRet; HKEY hKeyTgt; DWORD dwKeys; IRet = RegOpenKeyEx! hKey, pszSubKey, 0, KEY_ENUMERATE SUB_KEYS I KEY QUERY__VALUE | KEY_WRITE, ShKeyTgt if ( IRet '= ERROR ^ SUCCESS ) return IRet; IRet = RegQuerylnfoKey! hKeyTgt, NULL, NULL, NULL, SdwKeys, NULL, NULL, NULL, NULL, NULL, NULL, NULL ); if ( IRet '= ERROR_SUCCESS ) return IRet; foi ( DWORD dwlndex = dwKeys; dwlndex > 0; dwlnde — ) { TCHAR szKey[ AX_PATH] ; DWORD dwSize = sizeof! szKey ); IRet = RegEnumKeyEx ( hKeyTgt, dwlndex - 1, szKey, SdwSize, NULL, NULL, NULL, NULL ); if ( IRet == ERROR_SUCCESS ) _RegDeleteKey ( hKeyTgt, szKey ); IRet = RegCloseKey! hKeyTgt ); if ( IRet '= ERROR_SUCCESS ) return IRet; IRet = RegDeleteKey! hKey, pszSubKey ); return IRet;

Claims: CLAIMS l. A method for performing a first operation on a first object in a first computer system by a first process which lacks sufficient permission to perform said first operation on said first object, comprising the steps of: starting an intermediary process on said first computer, said intermediary process having sufficient permission to perform said first operation on said first object; said first process communicating a first request to said intermediary process to perform said first operation on said first object; and said intermediary process performing said first operation on said first object in response to said first request. 2. A method according to claim 1, further for performing a second operation on a second object in said first computer system by a second process which lacks sufficient permission to perform said second operation on said second object, wherein said intermediary process has sufficient permission to perform said second operation on said second object; further comprising the step of said second process communicating a second request to said intermediary process to perform said second operation on said second object; and said intermediary process performing said second operation on said second object in response to said second request. 3. A method according to claim 1, further comprising the step of said first process unsuccessfully attempting to perform said first operation on said first object, prior to said step of said intermediary process performing said first operation. 4. Apparatus according to claim 3 , wherein said step of starting an intermediary process precedes said step of said first process unsuccessfully attempting to perform said first operation. 5. Apparatus according to claim 1, for use further with a second computer system, further comprising the step of said second computer system issuing a command to said first computer system which includes performing said first operation on said first object, and wherein said step of said first process communicating a first request to said intermediary process occurs in response to said command. 6. Apparatus according to claim 3 , wherein said step of starting an intermediary process precedes said step of said second computer system issuing a command. 7. A method according to claim 1, wherein said first operation comprises a member of the group consisting of adding data to said first object, deleting data from said first object, modifying data in said first object, deleting said first object, renaming said first object, and changing properties of said first object. 8. A method according to claim 1, wherein said first object comprises a member of the group consisting of a file, a directory, a registry, a registry entry, and a node in a registry. 9. A method according to claim 1, wherein said intermediary process comprises a service. 10. A method for performing a first operation on a first object in a first computer system running a WindowsNT ® operating system, by a first process which lacks sufficient permission to perform said first operation on said first object, comprising the steps of: starting an intermediary process on said first computer, said intermediary process having sufficient permission to perform said first operation on said first object; said first process communicating a first request to said intermediary process to perform said first operation on said first object; and said intermediary process performing said first operation on said first object in response to said first request. 11. A method according to claim 10, wherein said intermediary process comprises a service running with administrator permissions. 12. A method according to claim 10, wherein said first object comprises a member of the group consisting of a WindowsNT ® registry, a WindowsNT ® registry entry and a node in a WindowsNT ® registry. 13. A method for performing a first operation on a WindowsNT ® registry in a first computer system running a WindowsNT ® operating system, by an agent process of an administration computer system, said agent process running on said first computer system and lacking sufficient permission to perform said first operation on said WindowsNT ® registry, comprising the steps of: starting an intermediary service on said first computer, said intermediary process having sufficient permission to perform said first operation on said registry; said agent process receiving a command from said administration computer system which includes performing said first operation on said registry; said agent process, in response to said command, communicating a request to said intermediary service to perform said first operation on said registry; and said intermediary service performing said first operation on said registry in response to said request. 14. A method according to claim 13 , further comprising the step of said agent process unsuccessfully attempting to perform said first operation on said registry in response to said command and prior to said step of communicating a request to said intermediary service. 15. A method according to claim 14, wherein said intermediary service runs with administrator permissions. 16. Apparatus for performing a first operation on a first object in a first computer system by a first process which lacks sufficient permission to perform said first operation on said first object, comprising: means for starting an intermediary process on said first computer, said intermediary process having sufficient permission to perform said first operation on said first object; means in said first process for communicating a first request to said intermediary process to perform said first operation on said first object; and means in said intermediary process for performing said first operation on said first object in response to said first request. 17. Apparatus according to claim 16, further for performing a second operation on a second object in said first computer system by a second process which lacks sufficient permission to perform said second operation on said second object, wherein said intermediary process has sufficient permission to perform said second operation on said second object; further comprising means in said second process for communicating a second request to said intermediary process to perform said second operation on said second object ; and means in said intermediary process for performing said second operation on said second object in response to said second request. 18. Apparatus according to claim 16, further comprising means in said first process for attempting to perform said first operation on said first object, wherein said means in said first process for communicating a first request to said intermediary process operates in response to failure of an attempt by said means for attempting. 19. Apparatus according to claim 16, for use further with a second computer system, further comprising means in said second computer system for issuing a command to said first computer system which includes performing said first operation on said first object, and wherein said means in said first process for communicating a first request to said intermediary process operates in response to said command. 20. Apparatus according to claim 18, wherein said means for starting an intermediary process operates before said means in said second computer system for issuing a command to said first computer system does so. 21. Apparatus according to claim 16, wherein said first operation comprises a member of the group consisting of adding data to said first object, deleting data from said first object, modifying data in said first object, deleting said first object, renaming said first object, and changing properties of said first object. 22. Apparatus according to claim 16, wherein said first object comprises a member of the group consisting of a file, a directory, a registry, a registry entry, and a node in a registry. 23. Apparatus according to claim 16, wherein said intermediary process comprises a service. 24. Apparatus for performing a first operation on a first object in a first computer system running a WindowsNT ® operating system, by a first process which lacks sufficient permission to perform said first operation on said first object, comprising: means for starting an intermediary process on said first computer, said intermediary process having sufficient permission to perform said first operation on said first object; means in said first process for communicating a first request to said intermediary process to perform said first operation on said first object; and means in said intermediary process for performing said first operation on said first object in response to said first request. 25. Apparatus according to claim 24, wherein said intermediary process comprises a service running with administrator permissions. 26. Apparatus according to claim 24, wherein said first object comprises a member of the group consisting of a WindowsNT ® registry, a WindowsNT ® registry entry and a node in a WindowsNT ® registry. 27. Apparatus for performing a first operation on a WindowsNT ® registry in a first computer system running a WindowsNT ® operating system, by an agent process of an administration computer system, said agent process running on said first computer system and lacking sufficient permission to perform said first operation on said WindowsNT ® registry, comprising: means for starting an intermediary service on said first computer, said intermediary process having sufficient permission to perform said first operation on said registry; means in said agent process for receiving a command from said administration computer system which includes performing said first operation on said registry; means in said agent process for, in response to said command, communicating a request to said intermediary service to perform said first operation on said registry; and means in said intermediary service performing said first operation on said registry in response to said request. 28. Apparatus according to claim 27, further comprising means in said agent process for attempting to perform said first operation on said registry in response to said command, said means for attempting operating prior to said means for communicating a request to said intermediary service. 29. Apparatus according to claim 28, wherein said intermediary service runs with administrator permissions.

Inventors: BAHR TERRY S, BAHR, TERRY, S.
Applicants: SYMANTEC CORP, SYMANTEC CORPORATION
Application year: 1998
Main classification: G06F1
IPC codes: G06F21, H04L29