Subj : Re: fTelnet
To   : Shurato
From : tassiebob
Date : Fri Oct 18 2024 20:53:36

 Sh> websockify --cert=c:\apache24\conf\bundle.pem 192.168.0.4:8080
 Sh> 192.168.0.3:24
 Sh> 
 Sh> Again, point ftelnet to the hostname and socket port number, and don't
 Sh> supply proxy information.

Thanks for the pointer - I have this working, but still have a couple of things to try and solve...

* websockify needs to access the private key for the certificate, but that by default requires root to access the file.  Obviously I don't want to run websockify as root :-)  I suspect I'll have to drop in a hook in certbot to either copy it somewhere websockify can access, or set the permissions so a group websockify is in has read access.  The former is probably safer, in case something else checks the file mode and bails if it's too open.

* If I read the documentation correctly, websockify won't notice when the certificate is updated, so the certbot hook will probably have to restart wensockify as well, which will break existing sessions.  Probably not too much of an issue - not like we're being buried with BBS users these days :-(

Thanks again for the pointer!

--- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
 * Origin: TassieBob BBS, Hobart, Tasmania (21:3/169)

.