Just wondering if there is a tag to pass the packet password to an archiver as a variable in sbbsecho? (similar to the %f and %s
tags)?
why would you want to do that? mail bundles (archives *.MO1, *.TU2, etc) are not password protected... they're not supposed to be... only the PKT files inside the bundles carry the password in their password field to try to ensure that the PKT actually comes from the system it says it comes from... that's all the packet password is for...
Hey, DM!
Just wondering if there is a tag to pass the packet password to an archiver as a variable in sbbsecho? (similar to the %f and %s tags)?
On an only somewhat related note, I'm using SEXPOTS for dialup, running synchronet 3.15, and have advertiselocation=true set in sexpots.ini, and the modem is providing CID to SEXPOTS, but SEXPOTS does not seem to be passing any info to synchronet. Is there a setting that I need to flip in the terminal config?
No (not as a variable/specifier like that). You could hard-code it in the command-line I guess. Are you (or your uplink is) password-protecting/encrypting bundles?Yeah, I'm playing with creating an encrypted link viewable only on ssh as a bit of a social experiment. Hardcoding works, I was just hoping I could use a variable to make things easier for multiple nodes/passwords. Thanks!
Hmm, nope. Sexpots just says Connected from COM port (handle 84) to 192.168.1.80 TCP port 23 using socket descriptor 92, doesn't show any telnet commands.On an only somewhat related note, I'm using SEXPOTS for dialup,If you have "Debug=true" in the [Telnet] section of your sexpots.ini, you should see the line "TX Telnet command: Location is x y" in the sexpots output.
running synchronet 3.15, and have advertiselocation=true set in
Do you see that?
Alternatively, on the BBS side, if you have Telnet debugging enabled, you should see the line "Node x received telnet location: x y" where x is the phone
number and y is the caller's name. Do you see that line in the log?
Re: Packet password as a variable?
By: Digital Man to Kostie Muirhead on Wed Apr 22 2015 18:49:33
No (not as a variable/specifier like that). You could hard-code it in the command-line I guess. Are you (or your uplink is) password-protecting/encrypting bundles?Yeah, I'm playing with creating an encrypted link viewable only on ssh as a bit of a social experiment. Hardcoding works, I was just hoping I could use a variable to make things easier for multiple nodes/passwords. Thanks!
Hmm, nope. Sexpots just says Connected from COM port (handle 84) to 192.168.1.80 TCP port 23 using socket descriptor 92, doesn't show any telnet commands.On an only somewhat related note, I'm using SEXPOTS for dialup,If you have "Debug=true" in the [Telnet] section of your sexpots.ini, you should see the line "TX Telnet command: Location is x y" in the sexpots output. Do you see that?
running synchronet 3.15, and have advertiselocation=true set in
Alternatively, on the BBS side, if you have Telnet debugging enabled, you should see the line "Node x received telnet location: x y" where x is the phone number and y is the caller's name. Do you see that line in the log?
Looks like the BBS side is requesting it though:
4/22 11:05:36p Node 1 sending telnet cmd: WILL Echo
4/22 11:05:36p Node 1 sending telnet cmd: WILL Suppress Go Ahead
4/22 11:05:36p Node 1 sending telnet cmd: DO Terminal Type
4/22 11:05:36p Node 1 sending telnet cmd: DO Terminal Speed
4/22 11:05:36p Node 1 sending telnet cmd: DO Send Location
4/22 11:05:36p Node 1 sending telnet cmd: DO Negotiate About Window Size 4/22 11:05:41p Node 1 received terminal auto-detection response: '\e[24;80R'
4/22 11:05:41p Node 1 received ANSI cursor position report: 80x24
Does that mean I'm missing something in SEXPOTS.ini to actually get it to use the telnet commands?
The applicable sections are setup as follows:
[TCP]
Host = 192.168.1.80 ; Hostname or IP address of TCP server
Port = 23 ; TCP port number of TCP server
NoDelay = TRUE ; Set to TRUE to disable the Nagle Algorithm
[Telnet]
Enabled = TRUE ; Set to FALSE to disable Telnet mode
Debug = TRUE ; Set to TRUE to log Telnet commands
AdvertiseLocation = TRUE ; Set to TRUE to send "WILL SEND LOCATION"
TermType = SEXPOTS ; You shouldn't normally change this value
TermSpeed = 28800,28800 ; Default terminal speed reported (tx, rx bps)
Try removing everything after the "TRUE" on those 3 lines. There was a recent bug-fix that would allow this syntax in .ini files, but that fix is probably not in the version of SEXPOTS you're running.That got it. Thanks!
Re: Packet password as a variable?
By: Digital Man to Kostie Muirhead on Thu Apr 23 2015 01:14:41
Try removing everything after the "TRUE" on those 3 lines. There was a recent bug-fix that would allow this syntax in .ini files, but that fix is probably not in the version of SEXPOTS you're running.That got it. Thanks!
One other follow on, is there an ARS flag that can be set for sexpots for accessing a sub-board etc?
Not exactly. You can check the connection rate using ARS. All Telnet, SSH, and RLogin connections will have an ARS "BPS" value of 30000. Your Sexpots connections will have a different value (e.g. 28800, 26400, etc.), so using an ARS of "BPS!=30000" would allow you to limit access to a specific BBS feature only for Sexpots/dial-in users.
Re: Packet password as a variable?
By: Digital Man to Kostie Muirhead on Thu Apr 23 2015 15:47:29
Not exactly. You can check the connection rate using ARS. All Telnet, SSH, and RLogin connections will have an ARS "BPS" value of 30000. Your Sexpots connections will have a different value (e.g. 28800, 26400, etc.), so using an ARS of "BPS!=30000" would allow you to limit access to a specific BBS feature only for Sexpots/dial-in users.
Excellent! I hadn't realized the others were constants, that knowledge may help elsewhere too.
You're the best, Rob!
| Sysop: | MCMLXXIX |
|---|---|
| Location: | Prospect, CT |
| Users: | 325 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 05:28:45 |
| Calls: | 510 |
| Messages: | 220570 |