>>something on RSA type public / private key encryption challenges.

>That's pretty vague.  What are you trying to get done?  If it's keeping
>attackers on the network between client and server out of the way, then
you
>need to start with SSL.  Client certificates and JS can solve
>authentication
>problems, where only people who know or have certain things are allowed
>access
>to something, but you still need to carefully define the parameters.


I think I figured something out. I just wanted to secure up the
authentication module a little bit, I'm in an environment where ssl is
not possible. And I don't want the password sent plaintext over the net.
So I found this little snippet (thanks to Andrew J. ) From BYU's
Blackboard program.

I think this will do what I want (I'll tell you how the implementation
goes)

<SCRIPT language="JavaScript" src="/javascript/md5.js"></SCRIPT>

<SCRIPT language="JavaScript" src="/javascript/base64.js"></SCRIPT>
<SCRIPT language="JavaScript">
var _useChallenge = true;
function validate_form(form) {
    //short-cut if challenge/response is disabled.
    if ( !_useChallenge )
    {
     //form.encoded_pw.value = base64encode( form.password.value );
     form.encoded_pw.value = calcMD5( form.password.value );
     form.password.value = "";
     return true;
    }
                        
    var passwd_enc = calcMD5(form.password.value);
    var final_to_encode = passwd_enc + form.one_time_token.value;
    form.encoded_pw.value = calcMD5(final_to_encode);
    form.password.value = "";
    return true; 
}

This way the password cannot be "sniffed" and the page is not vulnerable
to a replay attack.

Comments, Questions, or am I totally off I left field.


____________________
BYU Unix Users Group
http://uug.byu.edu/
___________________________________________________________________
List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list

Reply via email to