Ari Pollak <[EMAIL PROTECTED]> wrote: > I don't think using environment variables to specify username & > passwords are a very secure way to do things. Other users on a system > can easily look at other users' environments. > > Benjamin C. W. Sittler wrote: > > Package: pork > > Version: 0.99.5-2 > > Severity: normal > > Tags: patch > > > > > > although the bundled libfaim does support SOCKS5 proxies, pork does > > not; this means that the otrproxy for secure, deniable IM from > > > > http://www.cypherpunks.ca/otr/ > > > > does not work. i've attached a patch that changes pork to use the > > libfaim connection code so that this works. to use it, type e.g. > > > > otrproxy & > > env SOCKS5_PROXY=127.0.0.1 pork > > > > and you'll have secured im. this should work with other SOCKS5 proxies > > too (useful from behind some firewalls), but otrproxy is the only one > > i have tested it with. > > > > patch is also online at > > > > http://xent.com/~bsittler/pork-0.99.7-socks5.diff
i agree. the otrproxy doesn't support username/password auth anyhow, but the environment variables seem to be the standard way to specify a SOCKS5 proxy's username and password. Would you like me to send an updated version of the patch with Perl bindings for setting the proxy address and credentials? alternatively, would you prefer a version without username/password support, given that the proxy i'm using doesn't allow me to test that funcionality? -ben -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
