-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Michael,
I'm working on adding the "basic" and "NTLM" proxy authentication
schemes to the fwknop client. I'm curious how you'd prefer the interface
to work. I have an idea of how I'd like to do it:
I suggest we allow an option like "--http-proxy=on" or
"--http-proxy-on". If this option is specified, we look to the same
environment variables that wget uses. It's set with something like
export http_proxy="http://proxy.example.com:8080";
If authentication is needed:
export http_proxy="username:passw...@http://proxy.example.com:8080";
I think it would good to also allow the proxy information to be
specified as an option, much like "--http-proxy" is used now. Perhaps
"--http-proxy-user <proxy userid>" and "--http-proxy-password <proxy
password>".
There are some other details that I'm still working out. I'm wading
through the "basic" authentication rfc to make sure I implement it properly.
(http://www.ietf.org/rfc/rfc2617.txt)
I look forward to your input,
Jonathan Bennett
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAkrghZcACgkQhFXk1UR7WbcgFgCeJ0UvPEro8NRbUwofpsNFKQRH
eiAAoK+v3UKYTZHfoAJRxrxol39j//3J
=8tVx
-----END PGP SIGNATURE-----
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Fwknop-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fwknop-discuss
