On Fri, 5 Mar 2004, Andrew Jorgensen wrote:
[...]
> So Jason, supposing you had to implement this kind of a system (and
> let's say you can't just say "That's stupid!" and walk away.) How would
> you do it? In particular, how would you handle the token properly?
[...]
> But in your case that won't help, 'cause you still have to send a
> plain-text password to the LDAP server anyway (BYU's LDAP server for
> those who just tuned in). In fact I really can't think of a good way to
> do what you want to do without SSL.
That's the thing - authentication and secure channels are complicated problems
to solve correctly, and it's easy to get something that looks a lot like a
secure solution while still being completely broken. It may not even be
possible to solve his particular problem completely without, say, implementing
the bulk of SSL in Javascript, if that's the constraint.
So, yeah, a properly used nonce is a good start. But then what? If you just
hand out cookies at that point, I can steal them and use them directly,
without a password at all. You're almost certainly going to want a
confidential, authenticated channel, and that means SSL.
(Of course, even with SSL, you're not guaranteed safety - our lab has been
doing authentication systems over SSL, and finding that man-in-the-middle
attacks are still possible in many configurations.)
-J
____________________
BYU Unix Users Group
http://uug.byu.edu/
___________________________________________________________________
List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list