From 874893b8f51eb452acd16516004a58e459e769b5 Mon Sep 17 00:00:00 2001 From: Rob van Son Date: Wed, 6 Jun 2012 11:58:10 +0200 Subject: [PATCH] Updated documentation --- CGIscriptor.html | 28 ++++++++++++++-------------- CGIscriptor.pl | 36 ++++++++++++++++++++---------------- Private/.Passwords/test | 4 ++-- Private/.Passwords/testip | 4 ++-- Private/ChangePassword.html | 44 +++++++++++++++++++++++++++++++++++--------- Private/Login.html | 3 ++- Private/manual.html | 26 +++++++++++++------------- 7 files changed, 88 insertions(+), 57 deletions(-) diff --git a/CGIscriptor.html b/CGIscriptor.html index 90d14da..d2bfad1 100644 --- a/CGIscriptor.html +++ b/CGIscriptor.html @@ -1555,10 +1555,10 @@ for security). The example session model implements 3 functions:
  1. Login
    -The password is hashed with the server side salt, and then hashed with -a Random salt. Client and Server both perform these actions and the -Server only grants access if restults are the same. The server side only -stores the password hashed with the +The password is hashed with the user name and server side salt, and then +hashed with a Random salt. Client and Server both perform these actions +and the Server only grants access if restults are the same. The server +side only stores the password hashed with the user name and server side salt. Neither the plain password, nor the hashed password is ever exchanged. Only values hashed with the one-time salt are exchanged.
  2. @@ -1573,11 +1573,11 @@ one-time Session Ticket from a value derived from the password and a random string.
  3. Password Change
    -A new password is hashed with the server side salt, and then encrypted -(XORed) -with the old password hashed with the salt. That value is exchanged -and XORed with the stored old hashed(salt+password). Again, the -stored password value is never exchanged unencrypted. +A new password is hashed with the user name and server side salt, and +then encrypted (XORed) +with the old password hashed with the user name and salt. That value is +exchanged and XORed with the stored old hashed(salt+password+username). +Again, the stored password value is never exchanged unencrypted.

@@ -1585,8 +1585,8 @@ stored password value is never exchanged unencrypted.

The session authentication mechanism is based on the exchange of ticket identifiers. A ticket identifier is just a string of characters, a name -or a random 40 character hexadecimal string. There are four types of -tickets: +or a random 40 character hexadecimal string. Ticket identifiers should be +"safe" filenames (except user names). There are four types of tickets: