Re: Building Synchronet with SSH (libcl.a)
By: Jordanjm42 to Digital Man on Thu Sep 11 2025 08:16 pm
Ive watched sbbs run, there is no attempt to bind to port.
Are you sure about that? If Telnet and RLogin are working, then you'd see the attempts to bind to *those* ports. And if you have SSH enabled (which is enabled by default), then you'd see it attempting to bind to *that* port too, like this:
2025-09-09T13:33:54.256530-07:00 git sbbs: term Initializing on Tue Sep 9 13:33:54 2025 with options: 13020
2025-09-09T13:33:54.256581-07:00 git sbbs: term Loading configuration files from /sbbs/ctrl
2025-09-09T13:33:54.533201-07:00 git sbbs: term Telnet Server listening on socket 71.95.196.36 port 23
2025-09-09T13:33:54.792812-07:00 git sbbs: term RLogin Server listening on socket 2600:6c88:8c40:5b::5bb5 port 513
2025-09-09T13:33:54.904038-07:00 git sbbs: term SSH Server listening on socket 127.0.0.1 port 22
I've checked all the logs I could find with the same result, nothing indicating an issue. This leaves me to believe the Terminal server is not attempting to bind to the ssh port.
Only if you have SSH listening disabled for some reason.
(Note: installer originally tried libnettle-dev, but on Ubuntu 24.04/25.04 it's replaced by nettle-dev.)
I believe since these do not show results, that libcl.a isn't being built in. nm -A sbbs | grep cl_
objdump -t sbbs | grep cl_
You're on the wrong the track. Just look more closely at the log or console output from sbbs and your configuration in SCFG->Servers->Terminal Server and the output of 'netstat -l' or 'ss -l'.
https://wiki.synchro.net/monitor:index
--
digital man (rob)
Rush quote #36:
Raging at unreachable glory, straining at invisible chains
Norco, CA WX: 64.7øF, 83.0% humidity, 2 mph NW wind, 0.00 inches rain/24hrs
---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net