On 10/15/07(04:39) you "Maurice Glandrup" <email@example.com> wrote
|What I thought DeleGate is capable of doing is: if the browser is directed
|to a https server, DeleGate can make translations that make it appear for
|the browser that it is getting its data from a http server, while the https
|server thinks the client is a secure.
|Besides the translation from http -> https and vice versa, DeleGate also
|solves encryption and decription.
|If DeleGate can be configured this way, then it would be possible to analyze
|the decrypted HTML content.
You can cache/convert/analize the communication with the HTTPS/SSL server
by DeleGate as a HTTP proxy. If the clients sees the server as a HTTS/SSL
server, it can be done with STLS=mitm, of if the client sees the server as
if it's a HTTP server, it can be done as follows.
|> It depends on why you need it to do what. For example you can access
|> a HTTPS/SSL server like https://server as if it is http://https.server
|> over the bare HTTP protocol via DeleGate as a HTTP proxy like follows:
|> delegated -P8080 SERVER=http MOUNT="http://https.* https://*"
9 9 Yutaka Sato <firstname.lastname@example.org> http://delegate.org/y.sato/
( ~ ) National Institute of Advanced Industrial Science and Technology
_< >_ 1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan
Do the more with the less -- B. Fuller