jdn points out that we need to add a Socket parameter to the choose
methods of the X509KeyManager class. This way, we can use the
socket to provide a hint to the KeyManager as to which key would
be better suited to this socket.

bradford.wetmore@eng 2000-11-09

From our CCC request:

    When making the decision as to which certificate(s) to use when
    connecting to a remote host, the SSL socket should really be
    available to the X509KeyManager. There may be alternate keys to
    use for certain remote hosts, and the socket parameter would
    provide an excellent hint as to which certificate to use.

bradford.wetmore@eng 2000-11-09

IBM has also asked for there to be a way to pick out any
type of key from a keystore. We need to include
all possible types of keys, and pass those along.

From our CCC request

    Also, IBM and many other customers have asked for there to
    be a way to select one key out of many possible key entries in
    a keystore. Currently, JSSE provides this mechanism by
    developers overriding the X509KeyManager, however, this only
    works for specific keytypes (DSA/RSA). Each key type requires
    a separate call to choose*Alias(), and thus there is no way
    for developers to have a single callback from which to
    they can choose the "best" key.

bradford.wetmore@eng 2000-12-04