RE: [suse-security] Port Authentication before Port Forwarding
Hi Steven
i.e. The client connects to port 8080 on the firewall with a web browser. On connection to the port he is served with a html login page - preferable via SSL. If the username and password is correct the port-forwarding is enabled for the clients IP
Well, that sounds for me like a proxy server. I don't know wether squid supports (user/password) authentification, maybe SOCKS does. Thiemo -- root weiss, was er tut. Wicht weiss es nicht. Halb Wicht, halb root. Geht das gut? thiemo@gmx.ch
--- Thiemo Kellner
i.e. The client connects to port 8080 on the firewall with a web browser. On connection to the port he is served with a html login page - preferable via SSL. If the username and password is correct the port-forwarding is enabled for the clients IP
Well, that sounds for me like a proxy server. I don't know wether squid supports (user/password) authentification, maybe SOCKS does.
Squid does support username/password auth AKNIT
Thiemo
-- root weiss, was er tut. Wicht weiss es nicht. Halb Wicht, halb root. Geht das gut? thiemo@gmx.ch
-- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com
____________________________________________________________ Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie
participants (2)
-
Mark Tinka -
Thiemo Kellner