Re:Using OpenBSD Relayd(8) as an Application Layer Gateway
by pseudostem on Thursday October 12, 2023 @01:44AM
(#37853807)
Not sure about now, but at least a couple of years ago it didn't support SNI either.
What I love about openBSD documentation is that if it's not there in the docs, one can be sure that it doesn't exist.
Re:Using OpenBSD Relayd(8) as an Application Layer Gateway
by ggm on Thursday October 12, 2023 @02:00AM
(#37853908)
Yes, after "its rock solid and they fix bugs, real bugs, especially security bugs FAST" the docs are consistent. It's amazing.
Re:Using OpenBSD Relayd(8) as an Application Layer Gateway
by bxrt on Thursday October 12, 2023 @04:46AM
(#37854856)
SNI support was added with "tls keypair" option in OpenBSD 6.6: https://marc.info/?l=openbsd-cvs&m=155931636824866&w=2
Re:Using OpenBSD Relayd(8) as an Application Layer Gateway
by pseudostem on Thursday October 12, 2023 @06:27AM
(#37855405)
I stand corrected.
It was just about time, considering there was a jestful tricking the developer of relayd to reprogram it to httpd. IIRC he got epic tricked into it! In the sense he didn't even know he was making a webserver until he actually made it. This may not be a very true version, but I love to believe so.
The camaraderie and passion in the project is mind boggling.
Re:Using OpenBSD Relayd(8) as an Application Layer Gateway
by somat on Thursday October 12, 2023 @03:59AM
(#37854594)
I am not exactly sure what you want(Auth in the relayd process?) however you do mention ssh so I present you authpf.
Update: I think strictly speaking auth is outside the scope of relayd, but looking at the docs, I bet I could wire something together around having specific cookies or other headers.
match request type cookie "ident" value "hashed password"
or match request header "Authorization" value "Basic dXNlcm5hbWU6dGhpcyBpcyBzZWNyZXQK"
The above will not work by the way, last time I used relayd I found it to be one of the few openbsd programs where I had a hard time thinking the same way as it's author. That is, The syntax made my head hurt. I got it working but it was a chore. I think it is more that it ends up being a very complicated domain than poor syntax.
an ssh -D SOCKS5 tunnel requires you to present credentials on the jump host. This daemon bypasses that need. (happy to be corrected. I'd love to be wrong)