Re: [tor-dev] Proposal 351: Making SOCKS5 authentication extensions extensible

2024-09-10 Thread Nick Mathewson
On Tue, Sep 10, 2024 at 6:26 PM Jim Newsome wrote: > > It'd be helpful to have more context about the object IDs and what we're > trying to accomplish with them here; why we need/want them in arti but > didn't in c-tor. I'm inferring (maybe incorrectly) that the idea is that > this is effectively

Re: [tor-dev] Proposal 351: Making SOCKS5 authentication extensions extensible

2024-09-10 Thread Jim Newsome
It'd be helpful to have more context about the object IDs and what we're trying to accomplish with them here; why we need/want them in arti but didn't in c-tor. I'm inferring (maybe incorrectly) that the idea is that this is effectively letting us multiplex differently-configured SOCKS->Tor ser

Re: [tor-dev] Proposal 351: Making SOCKS5 authentication extensions extensible

2024-09-10 Thread Nick Mathewson
On Tue, Sep 10, 2024 at 9:25 AM Q Misell via tor-dev wrote: > > Is there a reason why this proposal extends the existing username/password > auth, instead of defining a new SOCKS5 authentication type? c.f. > https://datatracker.ietf.org/doc/html/rfc1928#section-3 Indeed there is! The one I was

Re: [tor-dev] Proposal 351: Making SOCKS5 authentication extensions extensible

2024-09-10 Thread Q Misell via tor-dev
Is there a reason why this proposal extends the existing username/password auth, instead of defining a new SOCKS5 authentication type? c.f. https://e.as207960.net/w4bdyj/5dQ6fT3QLm2aTfUx -- Any statements contained in this email are personal to the author and are not ne