Front cover - IBM Redbooks

Figure 6-6 Notes password dialog box
These dynamic symbols make it more difficult to substitute a false dialog box that
captures passwords in place of the Notes Password dialog box. Users should be
made aware of the particularities of this dialog box and of the fact that the
symbols change as they enter their passwords. If they notice that the symbols do
not change or are not present, they should stop entering their password and click
Cancel. As well, they should memorize the last image after they’ve typed their
password because the algorithm behind the symbols will always compute to the
same symbol in the end. (However, the algorithm is complicated enough that it is
not easy to sort out the password just by looking at the symbols and the way they
change).
Multiple passwords
To provide tighter security for certifier and server ID files, it is possible to assign
multiple passwords to an existing Notes ID. By doing this, it is possible to require
that more than one person, generally administrators, act together when using the
Notes ID.
It is important to dispel some confusion that generally exists here. When multiple
passwords are applied to a Notes ID, the original password for the Notes ID (or
the previous one, if the password differs from the original password) is no longer
valid. These multiple passwords replace the original password and are not
cumulative (that is, they don’t add themselves to the original password).
It is also possible to specify that only a subset of the assigned passwords be
required to access the Notes ID. For example, It is possible to assign four
passwords to access a specific Notes ID, but to define it so that it requires only
any two of the four passwords to access the Notes ID. This feature is useful
when the security policy states that giving authority for a certifier ID to a single
person should be avoided.
Note: We recommend that only Notes server IDs and Notes certifier IDs be
assigned multiple passwords. Notes user IDs should not have multiple
passwords assigned to them.
Chapter 6. Public key infrastructures 201