246
Novell eDirectory 8.8 Administration Guide
no
vd
ocx (
E
NU)
01
F
ebr
ua
ry
200
6
2
Click
Replica Synchronization
for the partition you want to view.
The replica status information is displayed. The
Encryption Status
field displays whether the
link from the replica to which you are currently connected is encrypted or not.
Basically, there are three scenarios in encryption replication (ER):
• ER enabled at partition level:
The replica to which you are connected to shows
Encryption State
is enabled.
To find out which replica you are connected to, in the replica frame, the one that is not
hyper linked is the one you are connected to. If you browse to the other replicas it shows
that the
Encryption State
is also marked Enabled.
• ER enabled at replica level:
You have enabled ER for all replicas from one particular
replica (that is, One to All.) In this case, when you are connected to that replica, its
Encryption State
is marked Enabled.
• ER enabled/disabled for a combination of replicas:
ER enabled/disabled for one
combination of replicas - You have enabled ER for the whole partition but not for a
selected set of servers or vice versa.
For example, you have enabled ER for partition A that has three replicas 1, 2, and 3 and
disabled ER for 1 <--> 3. In this case, if you are connected to replica 1, the
Encryption
State
is displayed as:
Server 1 Enabled
Server 2
Server 3 Disabled
This means that Server 1 is enabled for encrypted replication to all the servers in the
replica ring but 1<-->3 is disabled by the administrator.
9.3 Achieving Complete Security While
Encrypting Data
The first important basic rule to be followed before encrypting the data is:
No information that would eventually be encrypted should ever be written to the hard disk (or any
other media) in the clear.
When you mark existing clear text data for encryption, though the data gets encrypted, the existing
clear text data might still be present on some part of hard disk where the DIB resides.
There will be “Left Over” clear text pieces of data in some blocks of database if you try to do
following operations:
• Mark existing clear text data for encryption
• Change the encryption scheme of an encrypted attribute
The following sections depict deployment scenarios for encrypted data and steps to ensure that the
encrypted data is truly secure:
•
Section 9.3.1, “Encrypting Data in an All New Setup,” on page 247
•
Section 9.3.2, “Encrypting Data in an Existing Setup,” on page 247
•
Section 9.3.3, “Conclusion,” on page 249
Summary of Contents for EDIRECTORY 8.8 - GUIDE
Page 4: ...novdocx ENU 01 February 2006...
Page 16: ...16 Novell eDirectory 8 8 Administration Guide novdocx ENU 01 February 2006...
Page 68: ...68 Novell eDirectory 8 8 Administration Guide novdocx ENU 01 February 2006...
Page 90: ...90 Novell eDirectory 8 8 Administration Guide novdocx ENU 01 February 2006...
Page 116: ...116 Novell eDirectory 8 8 Administration Guide novdocx ENU 01 February 2006...
Page 128: ...128 Novell eDirectory 8 8 Administration Guide novdocx ENU 01 February 2006...
Page 184: ...184 Novell eDirectory 8 8 Administration Guide novdocx ENU 01 February 2006...
Page 249: ...250 Novell eDirectory 8 8 Administration Guide novdocx ENU 01 February 2006...
Page 307: ...308 Novell eDirectory 8 8 Administration Guide novdocx ENU 01 February 2006...
Page 333: ...334 Novell eDirectory 8 8 Administration Guide novdocx ENU 01 February 2006...
Page 371: ...372 Novell eDirectory 8 8 Administration Guide novdocx ENU 01 February 2006...
Page 439: ...440 Novell eDirectory 8 8 Administration Guide novdocx ENU 01 February 2006...
Page 519: ...520 Novell eDirectory 8 8 Administration Guide novdocx ENU 01 February 2006...
Page 529: ...530 Novell eDirectory 8 8 Administration Guide novdocx ENU 01 February 2006...
Page 555: ...556 Novell eDirectory 8 8 Administration Guide novdocx ENU 01 February 2006...