openbsd/src/usr.bin/nc/nc.1, branch OPENBSD_7_9_BASE A mirror of https://github.com/libressl/openbsd.git https://git.lua4.win/openbsd/atom?h=OPENBSD_7_9_BASE 2025-06-24T13:37:39+00:00 nc: document -Talpn 2025-06-24T13:37:39+00:00 tb 2025-06-24T13:37:39+00:00 urn:sha1:78b30ca5eb2333bc5fc3c994b228b316ed42905a From David Leadbeater limitiation -> limitation 2025-05-28T03:57:13+00:00 jsg 2025-05-28T03:57:13+00:00 urn:sha1:2fb1ca21ad4a3bebfe3187bb4e4e7d681ce52c6d add SOCKS4A support to nc(1)'s proxy (-X) mode 2025-05-21T08:41:35+00:00 djm 2025-05-21T08:41:35+00:00 urn:sha1:17435627329f6bb33c752a3bfef47a2a84dcebd0 SOCKS4A is a fairly obscure extension to the olde SOCKS4 protocol that allows passing the destination as a string rather than a literal IPv4 address, which is the only thing that vanilla SOCKS4 supports. The motivation for adding something so niche is to test the SOCKS4A server code in ssh(1)'s dynamic forwarding (-D) support. ok tb@ Mention that port can be specified as 0 in some situations, so that the 2024-04-01T12:40:18+00:00 deraadt 2024-04-01T12:40:18+00:00 urn:sha1:5c866cf89a8430be07c0f516944dc505b3916c62 system will allocate a port. Replace archaic \*(Lt and \*(Gt by plain < and >, respectively, 2022-09-11T09:58:06+00:00 schwarze 2022-09-11T09:58:06+00:00 urn:sha1:915fe5ab63f3761883fccbd0290be92d0daf8f80 because these inspire devotion to cargo cult in developers. Cleanup suggested by kn@. one of the examples needs an -N (and explanation); 2021-03-31T20:41:35+00:00 jmc 2021-03-31T20:41:35+00:00 urn:sha1:02d9600145759275fdb18558db4e5a4a85bd0c23 diff from robert scheck discussed with and tweaked by sthen Standardize argument naming for "sourceaddr" and unify the wording a bit, 2020-02-12T14:46:36+00:00 schwarze 2020-02-12T14:46:36+00:00 urn:sha1:4970e0155d7f95c3e44ba85c3286257e319af0bb similar to what deraadt@ recently did in other manual pages. Service names are still resolved with -n 2019-10-24T17:27:08+00:00 kn 2019-10-24T17:27:08+00:00 urn:sha1:cc296ed627856799a9677fa96ce42ce970107127 Just like pfctl(8)'s -N, this flag only avoid DNS; "nc -vz ::1 socks" still works. Fix documentation by copying pfctl's wording. OK deraadt too many words in previous; 2018-12-27T17:45:36+00:00 jmc 2018-12-27T17:45:36+00:00 urn:sha1:ce7114d95a1c3dfb5c5ad6eebe0c91e4c8be5f1b port ranges can be ambiguous with hypenated port-names. 2018-12-27T17:22:45+00:00 tedu 2018-12-27T17:22:45+00:00 urn:sha1:d19a006e485ef991d2f5bdf8bb2f5796bbd39ca6 specify that ranges must be numeric, and only check for range if first argument is a digit. identified by danj, fix suggest by sthen