Changes between Version 4 and Version 5 of SWEET32
- Timestamp:
- 08/26/16 00:45:56 (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
SWEET32
v4 v5 42 42 The (undocumented) {{{auth-token}}} option can be pushed by a client-connect script (running on the server) to instruct the connecting client to return this token as the password during the next authentication. The auth-user-pass-verify script (running on the server) should accept this token during the next authentication sessions, until the token expires. 43 43 44 The following client-connect and auth-user-pass-verify scripts illustrate how these options can be used. Note that these scripts are examples for auth-token usage only, and should be adapted to your own needs before using them. T hese scripts should not be used as-is!44 The following client-connect and auth-user-pass-verify scripts illustrate how these options can be used. Note that these scripts are examples for auth-token usage only, and should be adapted to your own needs before using them. THESE SCRIPTS SHOULD NOT BE USED AS-IS! 45 45 46 46 client-connect: