News for hackers. Stuff that matters.
Re:A userspace WireGuard client that exposes itself as a proxy by TedDoesntTalk on Saturday March 26, 2022 @09:27PM (#30816918)
Why wouldn’t you just run ssh -D to the remote machine? The effect is the same and you don’t need wire guard or wire proxy.
Re:A userspace WireGuard client that exposes itself as a proxy by octeep on Saturday March 26, 2022 @09:45PM (#30817019)
I made it because my friends and I use wireguard to have a private network, and they don't feel comfortable running a ssh server on their machines. It can also be used with a vpn provider like Mullvad without setting up a new nic or requiring special privs.
Re:A userspace WireGuard client that exposes itself as a proxy by ignoramous on Sunday March 27, 2022 @01:47AM (#30818009)
I want to point out a caveat to others: Proxifier != VPN

wireproxy's wg only forwards TCP and UDP. I am not sure how ICMP is handled. Other transports, though rarely used, won't be tunneled (and may leak, if not dropped).

Re:A userspace WireGuard client that exposes itself as a proxy by chockchocschoir on Sunday March 27, 2022 @09:20AM (#30820001)
Most importantly missing: DNS, which usually is handled over UDP (changing slowly now with DNS-over-HTTPS and some TCP resolvers). Without handling DNS requests via your proxy, you're still leaking information about yourself to the resolver you're using.
Re:A userspace WireGuard client that exposes itself as a proxy by TedDoesntTalk on Sunday March 27, 2022 @12:40PM (#30821643)
SOCKS5 supports DNS queries. Not sure if this project implements it though.
Re:A userspace WireGuard client that exposes itself as a proxy by octeep on Sunday March 27, 2022 @02:56AM (#30818312)
To clarify, UDP is not currently supported, but I intend to support it in the future. Incoming ICMP should be completely dropped, and outgoing ICMP is not supported.
Re:A userspace WireGuard client that exposes itself as a proxy by tptacek on Saturday March 26, 2022 @09:52PM (#30817050)
One simple reason is that the serverside might not want to expose a shell to its clients, and instead just provide network connectivity; you can configure something like that with SSH, but it's a pain, and WireGuard is approximately as simple to set up as SSH, which is the primary reason it's so popular.
Re:A userspace WireGuard client that exposes itself as a proxy by djbusby on Saturday March 26, 2022 @10:31PM (#30817239)
And it's crypto is "very good" (so I've heard, not an expert)

And it's fast/low overhead.

And yea, surprisingly easy, "just works"

I lurk their maillist, seems a nice group.

Re:A userspace WireGuard client that exposes itself as a proxy by tptacek on Saturday March 26, 2022 @10:56PM (#30817353)
It is very good, it is objectively better in a lot of ways than legacy DNS protocols. But it's popularity is, I think, mostly because of ease-of-use.
Re:A userspace WireGuard client that exposes itself as a proxy by Hello71 on Saturday March 26, 2022 @11:20PM (#30817440)
Is it a pain? As far as I know, all that's needed is to insert restrict,command="/sbin/nologin",port-forwarding before the user's key in authorized_keys. You can add more security by using a separate user, but individual Unix users for each client are not^W^Wshould not be necessary for security.
Re:A userspace WireGuard client that exposes itself as a proxy by hotpotamus on Saturday March 26, 2022 @09:34PM (#30816958)
Presumably you'd use it on a machine that doesn't expose SSH. That said, I really like sshuttle for this use case when SSH is available.