Hallo Thorsten. Thorsten Glaser wrote in <[email protected]\ .org>: |Steffen Nurpmeso dixit: |>library. That increased the surprise, because all one needs for |>SOCKS5 support, even including the DNS lookup, is to hook |>connect(2) -- that is how i did it, as easy as [1]. And in fact | |Really? (About DNS. I disbelieve that, especially as the DNS |server is on the LAN normally.)
If you mean SOCKS5, the protocol allows passing a hostname instead of a resolved IP address, and then the SOCKS proxy resolves the name. lynx is pretty much a jungle there, but in an ideal world the port number comes from getservbyname(), and then we are fine out. Here the SOCKS proxy is local, so you are right. |>i became inspired by Gaetan Bisson's usocks-06.c, which can be | |Ugly, but can be used for inspiration. He is a math professor, which might explain it. And pretty pragmatic. |>Wouldn't it be much nicer if there would be a -socks=[HOST]:PORT |>command line argument and a simple, always compiled in, wrapper |>around connect, just the way i do it (in [1])? | |Yesplease! I tried to look at enabling SOCKS support, for Tor |support, and… there was not even a hint as to which library |was the right one, and the one I found was so bloated… I could not find a "socks" library. torsocks and such, yes. But never used that myself. The thing is that i do not understand why you need a library for that, what you need is the proxy. Ciao, and good night, Thorsten, --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt) _______________________________________________ Lynx-dev mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lynx-dev
