Amessyroom wrote to All <=-
I have modified my sbbs.ini to try and get it to start ssh on
2222 instead of 22. I'm running on Linux os so have my sshd
already running on 22. I would prefer to keep it that way.
I've tried setting the interface for ssh to the IP:Port also, and
still doesn't seem to start.
I've set logging to Debug, but I don't think it is starting at
all.
Any suggestions?
I have modified my sbbs.ini to try and get it to start ssh on 2222 instead of 22. I'm running on Linux os so have my sshd already running on 22. I would prefer to keep it that way.
I've tried setting the interface for ssh to the IP:Port also, and still doesn't seem to start.
I've set logging to Debug, but I don't think it is starting at all.
Any suggestions?
Re: SSH not starting on non-standard port 2222term 0005 !ERROR 13 binding SSH Server socket to port 22: Permission denied term 0005 !ERROR 13 binding SSH Server socket: Permission denied [sbbs@vmi1943160 data]$
22. I would prefer to keep it that way.
I've tried setting the interface for ssh to the IP:Port also, and still doesn't seem to start.
I've set logging to Debug, but I don't think it is starting at all.
What do your terminal server log report?
Any suggestions?
Check the log output.
Re: SSH not starting on non-standard port 2222
By: Amessyroom to All on Sat Jun 22 2024 06:42 pm
sbbs@vmi1943160 data]$ grep -i ssh error.log
term 0005 !ERROR 13 binding SSH Server socket to port 22: Permission denied term 0005 !ERROR 13 binding SSH Server socket: Permission denied [sbbs@vmi1943160 data]$ grep -i ssh ../ctrl/sbbs.ini
[BBS] Terminal (Telnet, SSH, RLogin, Raw-TCP) Server
SSHInterface =
;SSHErrorLevel = Warning
SSHErrorLevel = Debugging
; TCP port for Secure Shell (SSH) server:
SSHPort = 2424
SSHConnectTimeout = 10s
; ALLOW_SSH
; SSH_ANYAUTH
Options = XTRN_MINIMIZED| ALLOW_SSH | ALLOW_SFTP
Changed port to 2424, rebooted server, restarted SBBS and it is trying to bind to port 22; which the OS is using.
Why is it ignorning the requested port of 2424
Re: SSH not starting on non-standard port 2222
By: Digital Man to Amessyroom on Sat Jun 22 2024 08:50 pm
Re: SSH not starting on non-standard port 2222
22. I would prefer to keep it that way.
I've tried setting the interface for ssh to the IP:Port also, and still doesn't seem to start.
I've set logging to Debug, but I don't think it is starting at all.
What do your terminal server log report?
Any suggestions?
Check the log output.term 0005 !ERROR 13 binding SSH Server socket to port 22: Permission denied term 0005 !ERROR 13 binding SSH Server socket: Permission denied [sbbs@vmi1943160 data]$
I have changed OS ssh to non 22 port. I've reran setcap and confirmed it has ability to point to privilege ports.
I have setup netcat on port 22, and connected to it. So other port can be used.
Maybe and OS issue. I have specified the IP in SSHInterface. Don't understand why it cannot bind and use 22, now that I've released it.
Re: SSH not starting on non-standard port 2222
I've tried setting the interface for ssh to the IP:Port also, and
still doesn't seem to start.
[sbbs@vmi1943160 data]$ grep -i ssh ../ctrl/sbbs.ini
[BBS] Terminal (Telnet, SSH, RLogin, Raw-TCP) Server
SSHInterface =
;SSHErrorLevel = Warning
SSHErrorLevel = Debugging
; TCP port for Secure Shell (SSH) server:
SSHPort = 2424
SSHConnectTimeout = 10s
; ALLOW_SSH
; SSH_ANYAUTH
Options = XTRN_MINIMIZED| ALLOW_SSH | ALLOW_SFTP
Changed port to 2424, rebooted server, restarted SBBS and it is trying to bind
to port 22; which the OS is using.
Why is it ignorning the requested port of 2424
Denn wrote to Amessyroom <=-
Re: SSH not starting on non-standard port 2222
By: Amessyroom to Digital Man on Sun Jun 23 2024 09:33 am
Re: SSH not starting on non-standard port 2222
I've tried setting the interface for ssh to the IP:Port also, and
still doesn't seem to start.
Could it be a firewall port not opened problem?
just a thought.
Re: SSH not starting on non-standard port 2222
By: Amessyroom to Digital Man on Sun Jun 23 2024 09:33 am
Re: SSH not starting on non-standard port 2222
By: Amessyroom to Digital Man on Sun Jun 23 2024 02:49 pm
Re: SSH not starting on non-standard port 2222
By: Amessyroom to Digital Man on Sun Jun 23 2024 09:33 am
Figured it out.
sbbs generated a key when first started on the 17th, and left it , although it was never successful in starting the daemon
I did not see this on console until, I turned off all other terminal services except ssh
sbbs core dumped
6/23 16:19:19 term SSH ERROR 'Couldn't import the session key used to protect the private key: Couldn't unwrap encrypted key' (-22) getting private key from bbs_thread
[Threads: 8 Sockets: 19 Clients: 0 Served: 0 Errors: 20] (?=Help): Segmentation fault (core dumped)
[sbbs@vmi1943160 ctrl]$ find $HOME -name \*.key -print /home/sbbs/ctrl/cryptlib.key
[sbbs@vmi1943160 ctrl]$ ls -l cryptlib.key
-rw------- 1 sbbs sbbs 1289 Jun 17 20:37 cryptlib.key
[sbbs@vmi1943160 ctrl]$ date
Sun Jun 23 04:39:49 PM EDT 2024
Removing cryptlib.key fixed issue. Thanks to the documentation mentioning, this key elsewhere (when SY password is changed), I figured that is where problem was in this case.
Is the console log written anywhere?
I read in the wiki that running in daemon mode isn't recommended?
But in daemon mode , I expect the console
will be written
to syslog local3.
But then ...
Telnet server started failing. I'm just sticking with telnet.
When using ssh I had issues with syncterm 1.1b with activating session. 50/50 it would work, and then I could get logged in.
At least, I know the source of the problem. Thanks for listening to my debugging
Ummm.... no. What would a firewall have to do with a service not
Could it be a firewall port not opened problem? just a thought.firewalld is not running. and I could run netcat and bind to 22.
Do you have more than one sbbs.ini file?Yes (had backup files , i.e. sbbs.[0-9].ini), moved them to OLD directory in ctrl directory.
If you run SCFG and go to Servers->Terminal Server, what does it say for "SSH Support"?
Re: SSH not starting on non-standard port 2222
By: Denn to Amessyroom on Sun Jun 23 2024 01:17 pm
firewalld is not running. and I could run netcat and bind to 22.
and in a follow up post; i got it working after seeing an error about ssh key and removing the cryptlib.key
thanks.
Denn wrote to Gamgee <=-
Re: Re: SSH not starting on non-standard port 2222
By: Gamgee to Denn on Sun Jun 23 2024 05:48 pm
Ummm.... no. What would a firewall have to do with a service not
Uhm.... go away Spaz......
So, you're going to get offended at everything I say, even when I'm
Denn wrote to Gamgee <=-
Re: Re: SSH not starting on non-standard port 2222
By: Gamgee to Denn on Mon Jun 24 2024 07:35 am
So, you're going to get offended at everything I say, even when I'm
Not offended, just tired of idiots like you.
So, you're going to get offended at everything I say, even when I'm
Not offended, just tired of idiots like you.You must be offended, or you wouldn't keep chirping at me like a little
CLUELESS and I was actually decent and trying to educate you. I guess
Re: Re: SSH not starting on non-standard port 2222 By: Gamgee to Denn on
Sun Jun 23 2024 05:48 pm
Ummm.... no. What would a firewall have to do with a service not
Uhm.... go away Spaz......
So, you're going to get offended at everything I say, even when I'm CLEARLY right and you are OBVIOUSLY wrong, eh? I wasn't rude or anything else, just pointing out how a firewall could NOT cause the problem being discussed.
Is that right? Is that how you're going to act no matter what? Who's the "spaz" here...?
Re: Re: SSH not starting on non-standard port 2222
By: Gamgee to Denn on Mon Jun 24 2024 07:35:00
We all know where you were going with how you delivered this message, just as with the other passive agressiive attempts of showing your "superior" intellect to others. It's not hard to see, and whether you are right or wrong, In your mind you are always correct and will never have it any other way.
Seems that personality is prevalent on the internet and definatly bbsing. I don't know if it is because the "anonimity" of it all or what. but it seems to give people brains and balls they normally would'nt have IRL. So just say to yourself, "If I would'nt say this to someone looking them straight in the eyes, then maybe I should'nt say it to them here". and you will start being a person that is not so much a spaz.
Because really, viewing the totality of the messages you have written here, that is what you make yourself out to be. If you were correct with all the "helpful suggestions" you give out, and your delivery was a little less douchebaggey it would'nt be so bad. But a lot of times you are wrong.. or just just not hitting 100 percent on your suggestions, and when that happens, you kinda just "disappear".. and thats what I find real funny about it all. At first it really bothered me. but then I see that you probably just need this validation to stroke your ego or something, So now I just find it funny. I would find it sad. but for some reason, I have no pity for you.
As annoying as MRO is this Gamgee kid is worse.
Denn wrote to Gamgee <=-
So, you're going to get offended at everything I say, even when I'm
Not offended, just tired of idiots like you.
You must be offended, or you wouldn't keep chirping at me like a little
Go home and play with your tinker toys kid.
CLUELESS and I was actually decent and trying to educate you. I guess
Here's a clue "..l. .l.." just don't even respond to me.
kk4qbn wrote to Gamgee <=-
Uhm.... go away Spaz......
So, you're going to get offended at everything I say, even when I'm CLEARLY right and you are OBVIOUSLY wrong, eh? I wasn't rude or anything else, just pointing out how a firewall could NOT cause the problem being discussed.
Is that right? Is that how you're going to act no matter what? Who's the "spaz" here...?
We all know where you were going with how you delivered this
message, just as with the other passive agressiive attempts of
showing your "superior" intellect to others. It's not hard to
see, and whether you are right or wrong, In your mind you are
always correct and will never have it any other way.
Re: SSH not starting on non-standard port 2222
By: Amessyroom to Digital Man on Sun Jun 23 2024 05:12 pm
A backtrace from that core dump would likely allow me to fix that issue: https://wiki.synchro.net/howto:gdb
Not normally, but if the "syslog" command-line option is used, it'll write to syslog.It is working. Thank you.
https://wiki.synchro.net/monitor:sbbscon
I think you have that reversed: daemon mode *is* recommended. https://wiki.synchro.net/install:nix#daemon_mode
I'm not clear if you're still having an issue or not. <shrug>
and you see here.. hey.. I did'nt comment.. wonder if it's because my ALT keys aren't mapped correctly on this console, or if I just want to bother you with petiness.. I would like to be done with this, but you are always here trying to cut people down, degrade, and bully.. I would like to see you say any of what you say online to anyones face while you are looking them in the eye, I bet you could'nt. I know you would'nt because judging by how you act on here you fit the profile of a cowardess bully.gamgee..
MRO has at least cooled down with a lot of his nonsense lately, but it appears you have taken his place pretty much. I guess since he has'nt been filling your need to argue with someone you are out baiting whoever you can.
Next time when offering your valuable input, try not to be so passive agressive about it. leave out the "um nooo's" and the "you retards" and you may not look so much like well... a
---
Tim (kk4qbn)
+o kk4qbn.synchro.net
� Synchronet � KK4QBN BBS - kk4qbn.synchro.net - Chatsworth, GA USA
kk4qbn wrote to Gamgee <=-
<SNIP>
Oh, there you go cutting
Denn wrote to kk4qbn <=-
As annoying as MRO is this Gamgee kid is worse.
I was considering twitlisting bambee but I'll just ignore him.
<SNIP>
Oh, there you go cutting
<SNIP drivel>
FOAD, dimwit.
I was considering twitlisting bambee but I'll just ignore him.
Yeah, I forget that replying to this crap just makes it grow exponentially just like the ego's that spew it. I'll do the same.. maybe soon it'll just go away.
Re: SSH not starting on non-standard port 2222
By: Amessyroom to Digital Man on Sun Jun 23 2024 05:12 pm
A backtrace from that core dump would likely allow me to fix that issue: https://wiki.synchro.net/howto:gdb
Would the dump be called core?
Re: Re: SSH not starting on non-standard port 2222Well, I just fixed it, Bambee is now in my twitlist.
By: Denn to kk4qbn on Tue Jun 25 2024 12:31 pm
Lately there have been a lot of posts with the 3 of you arguing with each other. This isn't fight-o-net, is it? ;)
Nightfox
---
Seems by default they were not being saved, but have changed parameters and restarted the bbs and confirmed I will get future coredumps.Would the dump be called core?
That depends on your system configuration, but the core files usually have "core" somewhere in their name.
"core" somewhere in their name.
Re: SSH not starting on non-standard port 2222
By: Amessyroom to Digital Man on Wed Jun 26 2024 06:10 pm
Is the hypen a legal DOS character?
I used it in my system QWL name for
Dove-Net and it is working.
Trying to add another QWK networ, and after I say Yes I want this to be a QWK account it asks for name, and says that what I enter is invalid.
I would no think anything has changed recently. If is an illegal characet, what would be best approach to renaming my QWK name on my BBS and vERT for QWK networking ?
What is "it" in this context? If it's another QWKnet hub/BBS, have you tried asking that sysop about it?
I would no think anything has changed recently. If is an illegal characet, what would be best approach to renaming my QWK name on my BBS and vERT for QWK networking ?
Dash is a valid DOS filename and QWK-ID character.
Dash is a valid DOS filename and QWK-ID character.
I just attempted to set up a QWK ID node for Amessyroom on my system so that he can pick up Micronet. Synchronet 3.20 on linux would not accept "TL-QWK" as a QWK ID. It complained about an invalid character. I had to
I've tried creating a test account on my BBS as a QWK account. It looks like in newuser.js, it's failing the QWK ID check. In the chk_qwk_id() function, this is the first test:
if(str.search(QWK_ID_PATTERN) != 0)
return false;
QWK_ID_PATTERN is:
/^[A-Z]\w{1,7}$/
It looks like that pattern is looking for a single capital letter followed by 1 to 7 whitespace characters? str.search(QWK_ID_PATTERN) is returning -1 (not found), and since the test is checking it for != 0, then it returns false.
Just for fun, I just tried to change it from '_' to '-' in the User Editor and it did work. However, I am not sure what it would try to do with that edited '-' name should the system try to use it to log on.
What is "it" in this context? If it's another QWKnet hub/BBS, have you tried asking that sysop about it?
I would no think anything has changed recently. If is an illegal characet, what would be best approach to renaming my QWK name on my BBS and vERT for QWK networking ?
Dash is a valid DOS filename and QWK-ID character.
I just attempted to set up a QWK ID node for Amessyroom on my system so
that he can pick up Micronet. Synchronet 3.20 on linux would not accept "TL-QWK" as a QWK ID. It complained about an invalid character. I had to set it to TL_QWK.
I have not had any issues when using a '-' in dosemu as a filename character, but Synchronet would not accept it in the QWK ID name.
Just for fun, I just tried to change it from '_' to '-' in the User Editor and it did work. However, I am not sure what it would try to do with that edited '-' name should the system try to use it to log on.
My mistake, \w is any word character. I looked it up online, and it sounds like a word character includes letters, numbers, and underscores. It looks like that regular expression doesn't match dashes.
The thing that "would not accept" it is likely the sysop's exec/newuser.js which was probably customized by that sysop. The stock newuser.js certainly does accept the dash character.
const QWK_ID_PATTERN = /^[A-Z]\w{1,7}$/;
That regular expression says the first character must be a letter, the characters at offset 1-7 can be any non-whitespace character.
My mistake (as Nightfox pointed out) - newuser.js now fixed in git.
Thanks for your patience,
No problem. Amessyroom was the first one to ever try using a '-' in their QWK ID here, AFAIK.
| Sysop: | Coz |
|---|---|
| Location: | Anoka, MN |
| Users: | 2 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 141:10:32 |
| Calls: | 166 |
| Files: | 5,389 |
| Messages: | 223,239 |