On Thu, 2007-03-01 at 18:28 +0100, Gregor Reich wrote: > This is a simple and properly working solution. But our clients won't > think good about us and the product if we give them this kind of login > procedure. They are used to type in the URL (at most we can let them > type https) and the the connection has to be there. So I would still > appreciate a solution where only the URL determines whether to use > encryption or not. (I didn't work with stunnel before, I guess that this > would be possible using stunnel??) So if somebody has a working solution > or knows where to find it, please let me know.
Your clients should be more worried about why remote access to their SPAM filter is needed at all. If they have to run a local stunnel command to connect, how is that different to running a local ssh port forward ? If you are running stunnel permanently on a host how would you be preventing someone else from using it also ? Wouldn't they have a VPN somewhere in this equation that would give them access as if they were a local client anyway ? If you really just want the comfort of the user seeing https in the URL can you not proxy forward to ASSP from, say, apache ?
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
