SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #797864
Ticket Status: Wishlist

PoP: (not applicable)

error in TIC documentation
[ar] Shadow Hawkins on Friday, 29 August 2008 06:23:38
I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there: Hi, in https://www.sixxs.net/tools/tic/ 1 The Authentication reads: to authenticate the following comparison is used:
md5sum(md5sum(clearpass).challenge) == md5sum(storedpass.challenge
A client sends the first part (...) it would be more precise if it read to authenticate the following comparison is used:
md5sum(challenge.md5sum(clearpass)) == md5sum(challenge.storedpass)
A client sends the first part (...) Rationale: the AICCU implementation of this operation is:
//challenge in &buf[4] MD5String(password, sSignature, sizeof(sSignature)); //md5sum(clearpass) snprintf(sChallenge, sizeof(sChallenge), "%s%s", &buf[4], sSignature); //challenge.md5sum(clearpass) MD5String(sChallenge, sSignature, sizeof(sSignature)); //md5sum(challenge.md5sum(clearpass))
md5sum(clearpass).challenge
conveys the idea that the challenge is concatenated after the clearpass MD5, but it is actually concatenated before. 2. In Typical Session section, the 4th line of the example reads handle JRM1-RIPE it should read username JRM1-RIPE (handle is an unknown command) Regards Javier Godoy
State change: wishlist Locked
[ch] Jeroen Massar SixXS Staff on Friday, 29 August 2008 16:09:19
Message is Locked
The state of this ticket has been changed to wishlist
error in TIC documentation
[ch] Jeroen Massar SixXS Staff on Friday, 29 August 2008 16:10:36
TIC documentation is out of date and does not match reality, that is also why it is not in any form of IETF draft. There are no other client or server implementations, nor have their been any requests for this.
error in TIC documentation
[ar] Shadow Hawkins on Monday, 01 September 2008 09:46:16
Well... I'm using my own TIC + heartbeat client implementation ;-) It is not so complete as the full AICCU suite, but it is enough for me.
error in TIC documentation
[ch] Jeroen Massar SixXS Staff on Tuesday, 02 September 2008 13:36:32
Any reason why you need your own implementation? Is there anything wrong with AICCU?
error in TIC documentation
[ar] Shadow Hawkins on Wednesday, 03 September 2008 07:07:20
No reasons at all (and nothing wrong with AICCU)... I just wanted to try it by myself.

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker