secure user-authentication in squid: The Story
- by Isaac
once upon a time, there was a beautiful warm virtual-jungle in south america, and a squid server lived there. here is an perceptual image of the network:
<the Internet>
|
|
A | B
Users <---------> [squid-Server] <---> [LDAP-Server]
When the Users request access to the Internet, squid ask their name and passport, authenticate them by LDAP and if ldap approved them, then he granted them.
Everyone was happy until some sniffers stole passport in path between users and squid [path A]. This disaster happened because squid used Basic-Authentication method.
The people of jungle gathered to solve the problem. Some bunnies offered using NTLM of method. Snakes prefered Digest-Authentication while Kerberos recommended by trees.
After all, many solution offered by people of jungle and all was confused!
The Lion decided to end the situation. He shouted the rules for solutions:
Shall the solution be secure!
Shall the solution work for most of browsers and softwares (e.g. download softwares)
Shall the solution be simple and do not need other huge subsystem (like Samba server)
Shall not the method depend on special domain. (e.g. Active Directory)
Then, a very resonable-comprehensive-clever solution offered by a monkey, making him the new king of the jungle!
can you guess what was the solution?
Tip:
The path between squid and LDAP is protected by the lion, so the solution have not to secure it.
Note: sorry for this boring and messy story!
/~\/~\/~\
/\~/~\/~\/~\/~\
((/~\/~\/~\/~\/~\))
(/~\/~\/~\/~\/~\/~\/~\)
(//// ~ ~ \\\\)
(\\\\( (0) (0) )////)
(\\\\( __\-/__ )////)
(\\\( /-\ )///)
(\\\( (""""") )///)
(\\\( \^^^/ )///)
(\\\( )///)
(\/~\/~\/~\/) **
(\/~\/~\/) *####*
| | ****
/| | | |\ \\
_/ | | | | \_ _________// Thanks!
(,,)(,,)_(,,)(,,)--------'
