#So your client is using what kind of OS? if its using Win there's an easy client called stunnelw a win port of the client. Pero if you're using Linux, that will do. # #
Currently, I only use stunnel with Linux-based clients.. but the Windows-based ones will follow (wife's already bugging me to get done with the setup.. he he) #>Server: #>./stunnel -c stunnel.pem -f -d 192.168.0.1:1234 -r localhost:3128 # #In this command you are saying to stunnel the process identifier is "stunnel.pem" not the key itself. # I already figured out what was wrong with the command -- it's a misplaced -c and a missing -p before "stunnel.pem." #>Client: #>./stunnel -c -f -d localhost:3128 -r 192.168.0.1:1234 # # #drop the -f =) # Eventually, I will. It's there so stunnel stays in the foregroud; it's easier to debug that way. #Note : You can attach the command u used for stunnels to your xinetd or inetd.conf on your server. use ports 900 and higher, standards for shttp. # Thanks, I appreciate the help. stay cool. jeff -- -- Jeff Gutierrez Pinoy Ako! May reklamo? Mapua Online! http://www.mapua.org http://www.mapua.com http://www.mapua.net Intertainer, Entertainment On Demand http://www.intertainer.tv _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
