TACACS Client Change History

• V 1.12 May 5, 2005

  · The debug packet display shows both the plain text and encrypted versions of the packet.

  · Corrupt packets (likely due to bad encodings by mismatched secrets) are detected.

  · More complete checking of the header information to assist debugging.

• V 1.11 April 22, 2005

  · Fixed a display problem in Continue packets.

  · New example clients have been added that illustrate ARAP, MSCHAP, PAP, CHAP, and ASCII authentication methods as well as authorization and accounting.

• V 1.10 April 12, 2005

  · Fixed a problem with ARAP. It was not creating the DES key properly.

• V 1.09 March 17, 2005

  · The AVPair class did not understand that an attribute may have an empty value. This has been fixed.

  · Sun's crypto provider does not provide the MD4 message digest. Other code has been provided to overcome this omission on Sun's part. This affected MSCHAP authentication - it would throw a null pointer exception.

• V 1.08 March 1, 2005

  · Fixed a problem that caused the faulty contruction of the jar and source files that resulted in the demo random number generator being included instead of the SecureRandom version. V 1.07 Feb 14, 2005

  · Removed specific BouncyCastle crypto functions. Now the default provider is used. This changed how the MD4 and MD5 digests are created. BouncyCastle provides a much faster MD5/MD4 than the default algthough for a client is is probably not that important. DES encryption is now accessed from the default crypto provider as well.

  · The mschap.java class has been renamed to MSChap and the construct is public.

  · The TACACSClient method authenticationContinue() has been fixed to use the correct flags (TAC_PLUS_CONTINUE_FLAG_ABORT and TAC_PLUS_CONTINUE_FLAG_OK). The CONTINUE / REPLY protocol works better now.

• V 1.06 Jan 7, 2005

  · Some cosmetic changes inside to make better use of constants.

• V 1.05 July 12, 2004

  · Changed the DES crypto to use the SUN crypto package. Some methods that didn't formerly throw the TACACException now do. Please recomplile your code with the new jar file to find these methods.

• V 1.04 Mar 06, 2004

  · Internal changes to some private and protected methods to allow for debugging display of packets.

  · When debugging is enabled using the TACACSClient.setDebugging() method request and reply packet unencrypted contents are be displayed.

  · Fixed an error in decoding the different authentication replies - two messages were picked up where only one was present. The getAdminMessage() method has been removed.

  · Added missing Authorization STATUS contstants, like TAC_PLUS_AUTHOR_STATUS_FAIL.

  · Improved the examples/modserver/ModAttributes example.

• V 1.03 Mar 03, 2004

  · Changes the name of TACACSSession.encrypt(boolean encrypt) to TACACSSession.enableEncryption(boolean enable) so it matches the same method used in the TACACSClient.

  · The global settings of the header flags weren't sent to the TACACSSession when it was created. This is fixed. Now global settings will initially apply to the session.

• V 1.02 Feb 17, 2004

  · Removed the list of legal attributes from AuthenticationAttributes and AuthorizationAttributes. The AttributeList class replaces both.

• V 1.01 Feb 12, 2004

  · Fixed a problem with authorization attributes not being returned.

• V 1.0 Jan 8, 2004

  · Initial coding.