Updated README and TODO files to reflect the current state of the
project.
This commit is contained in:
@@ -34,7 +34,6 @@ authentication. The mechanism leverages the services of the native Kerberos 5
|
||||
client to obtain Kerberos Tokens that can be used for authenticating an entity
|
||||
to a Kerberos service.
|
||||
|
||||
|
||||
SECURITY CONSIDERATIONS
|
||||
|
||||
The tokens that krb5mech generates are only utilized to authenticate the client
|
||||
|
||||
@@ -10,4 +10,7 @@ This file contains a list of the items still outstanding for krb5mech.
|
||||
|
||||
OUTSTANDING ITEMS
|
||||
|
||||
None.
|
||||
- Change to also do server authentication once the AuthMechanism interface
|
||||
is enhanced to support authentication schemes that require several token
|
||||
exchanges between the client and the server. Allow this to be configurable.
|
||||
.
|
||||
|
||||
@@ -10,4 +10,8 @@ This file contains a list of the items still outstanding for pwmech.
|
||||
|
||||
OUTSTANDING ITEMS
|
||||
|
||||
None.
|
||||
- Allow the server to specify that Desktop credentials should not be
|
||||
utilized.
|
||||
|
||||
- Try to find way to remove credentials from miCASA cache which are
|
||||
found to be invalid.
|
||||
|
||||
Reference in New Issue
Block a user