[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[gopher] Gopher+ Authentication (update)

Hash: SHA1

A small update to the Gopher+ Authentication proposal.  

- From the Gopher+ standard:

"The folks with a hirsute tendency will have noticed 
that all  these interactions  are static rather than 
truly dynamic and  interactive.  In other words, the  
server cannot ask different questions in response to 
different answers.   +ASK does not constitute a  
scripting language by any  means."

The last proposal would have worked dynamically--which is explicitly forbidden 
by the above.  Instead of making an incompatible change to the current 
protocol that would have gone against the orginal intent, I decided to make a 
slight modification to the proposal to use something that is similar, but not 
quite like +ASK.

Additionally, a new Gopher+ entry in the menu system has been defined to note 
which entries require authentication.

Gopher+ SRP Authentication

By Timm Murray

This document provides a secure means of authentication using 
the Secure Remote Password (SRP) scheme.  This scheme is documented 
in RFC 2945.  Implementors should be familer with that RFC.

In breaking with Gopher tradition, this document uses '\t' to denote a 
tab, '\r' to denote a cariage return, and '\n' to denote a newline.  
'C:' is a line of text sent by the client, and 'S: is a line sent by the 
server.  Calculations by one side or the other are contained in '[' ']' 
brackets, with a note specifiying who is doing the calculations.  Any 
numbers sent MUST be Base16 encoded [0-9A-Fa-f].

'|' indicates string cancatanation.  '^' is exponentation.  '%' is integer 
remainder. '==' checks for equivilence, while '!=' checks for unequivilence.  
SHA1() does an SHA-1 hash on the data.  SHA1_Interleave() is a special 
function that doubles the normal length of the SHA-1 hash, and is described 
in RFC 2945.

The means of storing username/password/salt values is also described in 
RFC 2945.  In short:

u = stored username
v = stored password verifier
s = salt value

At the beginning of the connection, the server sends a "HashType" field.  
This is a string specifying the type of cryptgraphic hash to use.  Where 
the protocol specifies "SHA1()" in calculations, the client and server MUST 
replace it with the proper hash type.  "SHA1_Interleave()" is also modified 
accordingly.  At a bare minimum, the clients and servers MUST implement the 

Name        Referance
- ----        ---------
SHA-1       RFC 3174
MD5         RFC 1321

Authentication works as follows:

C: <selector string>\r\n
S: +AUTH \r\n
	selects values for g and N
S: g \t N \t HashType \r\n
	if unrecoginized HashType, then send "Unknown Hash" and cut connection
	a = random()
	A = g^a % N
C: U \t A \r\n
	if A % N == 0, then cut the connection.
	v = <stored password verifier>
	b = random()
	B = (u + g^b) % N
	s = salt stored for username
S: s \t B \r\n
	if B % N == 0, then cut the connection. 
	p = <raw password>
	x = SHA(s | SHA(U | ':' | p))
	S = (B - g^x)^(a + u * x) % N
	K = SHA1_Interleave(S)
	M = SHA1(SHA1(N) XOR SHA1(g) | SHA1(U) | S | A | B | K)
	S = (A * v^u)^b % N
	K = SHA1_Interleave(S)
C: M \r\n
	J = SHA1(SHA1(N) XOR SHA1(g) | SHA1(U) | S | A | B | K)
	if J != M, then cut the connection.
	L = SHA1(A | M | K)
	I = SHA1(A | M | K)
S: OK \t L \r\n
	if L != I, then cut the connection

The server now proceeds with normal operation on the selector 


Menu entities pointing to items requiring authentication use a '*' character 
after the last tab.  For instance:

0This file requires authentication \t /testauth \t host \t port \t * \r\n

This signals the client to be prepared for an authentication exchange.  After 
'*', another Gopher+ type may be placed.  For instance, an +ASK value can be 
specified like this: 

0Authenticate \t /auth \t host \t port \t *? \r\n
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org


Reply to: