Microsoft Windows NT 4.0 Guide Manual de usuario descargar pdf (Pagina 102)

Microsoft

Windows Server

™

2003 White Paper

Windows NT 4.0 Server Upgrade Guide 97

Modified LDAP Signing

This change affects the wldap32.dll LDAP bind initialization sequence so that signing is requested

even if the client doesn’t ask for it. This step does not occur if TLS or SSL protocol is used.

LSAP signing is similar in effect to the SMB signing. LDAP always requests signing now.

Stopped Allowed Paths Leakage

This change eliminates unnecessary information disclosure pertaining to system configurations.

Many areas of the registry require Administrator privileges to read. However, security for certain

branches was loosened through the use of the AllowedPaths key, which gave non-administrators

privileges to read the data in that part of the registry. However, too much information could be

read. Windows Server 2003 narrowed the paths to specific subtrees and specific subkeys. As a

result, applications can no longer access a subtree around the data you are looking for.

Console Applications

Remote execution of console applications is now restricted to administrators only.

COM+ Security and Active Directory

Security in COM+ has been enhanced to integrate more closely with Active Directory by using two

new technologies: COM+ partitions and partition sets.

COM+ partitions stored in Active Directory are used to map a local COM+ partition, which stores

the actual COM+ application, to specific users or organizational units in your enterprise. COM+

applications are groups of COM components developed to work together to make use of COM+

services such as queuing, role-based security, and so on.

There are two types of COM+ partitions: COM+ partitions stored in Active Directory and local

COM+ partitions stored on application servers. Using COM+ partitions stored in Active Directory,

you can assign domain users and entire organizational units to applications stored in local COM+

partitions. Local COM+ partitions are application containers used to manage multiple instances of

COM+ applications on a single application server.

A local COM+ partition can store only one instance of an application. For example, if you need to

make two or more versions of the same application available to domain users, you must create

two separate local COM+ partitions on an application server and associate (or link) them with two

separate COM+ partitions in Active Directory.

To enable COM+ partitions, open Component Services, and then expand the list view to select a

computer for which you want to enable partitions. Select Properties, click the Options tab, and

select the Enable Partitions option. The following dialog box appears when enabling COM+

Partitions:

1 2 ... 97 98 99 100 101 102 103 104 105 106 107 ... 154 155

Sin comentarios

Microsoft Windows NT 4.0 Guide Manual de usuario Pagina 102