Updated the prealphas for 11/25 at 4pm EST (for Linux and Windows no Pi or >OSX).
--- Mystic BBS v1.12 A36 2017/11/25 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)
Does this have the NNTP stuff we were discussing?
Does this have the NNTP stuff we were discussing?
It has a fix for the creating of new message bases (or I hope it does).
I do not know whether or not that is a factor in your specific problem, but I >am hoping it is!
--- Mystic BBS v1.12 A36 2017/11/25 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)
Will that affect current message bases? I assume we won't have to recreate?
Have been updated for 11/27
--- Mystic BBS v1.12 A36 2017/11/27 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)
Did notice this with the FTP:
+ 15:31:14 FTP Cannot resolve IPV6 domain, using: 2601:08C0:4280:1C81:020C:29FF:FE10:ADC3
instead of the interface being :: should I add my external ipv6 address?
Did notice this with the FTP:
+ 15:31:14 FTP Cannot resolve IPV6 domain, using: 2601:08C0:4280:1C81:020C:29FF:FE10:ADC3
instead of the interface being :: should I add my external ipv6 addre
It is resolving the BBS domain you have configured to get its external IP (unrelated to your network interface). The FTP server needs this in
order to perform passive file transfers.
Is the message there showing your external IP or your network interface?
Have been updated for 11/27
Here is the log entries:
+ 15:31:14 FTP Cannot resolve IPV6 domain, using: 2601:08C0:4280:1C81:020C:29FF:FE10:ADC3
Here is the log entries:
+ 15:31:14 FTP Cannot resolve IPV6 domain, using: 2601:08C0:4280:1C81:020C:29FF:FE10:ADC3
Its just a display bug that I just fixed!
It is resolving your IP correctly and printing the proper IPV6 address!
False alarm :)
Just updated the pre-alphas again. This has a bunch of extra SSL error logging, the old MIS is completely gone, some other minor changes here
and there.
Just updated the pre-alphas again. This has a bunch of extra SSL error logging, the old MIS is completely gone, some other minor changes here
and there.
Just change the ansi on the old MIS2 as it still references MIS2 in the
Just change the ansi on the old MIS2 as it still references MIS2 in the syntax guidelines.... HUB is now updated :)
I've updated the pre-alphas today for those brave souls who wish to test the cutting edge. Only the Windows and Intel Linux version have been
quirky), echomail security is done from a configuration standpoint,
quirky), echomail security is done from a configuration standpoint,
Can I start to implement this now for the HUBs or should I hold off?
I will be doing another upgrade of prealphas in the next hour or so I hope.
I just updated the prealphas on mysticbbs.com.
This should fix the semaphore issue reported, and the issue with the I* menu commands.
I just updated the prealphas on mysticbbs.com.
This should fix the semaphore issue reported, and the issue with the I* menu commands.
Updated! :)
Updated! :)
i downloaded it but it's showing timestamp of 2018-04-16.
i downloaded it but it's showing timestamp of 2018-04-16.Same here, updated this morning 2018-04-16
Very pleased to have encrypted sessions now for BINKP! :)
On 16-Dec-2018 06:01, NuSkooler wrote to g00r00 <=-
On Saturday, December 15th g00r00 muttered...
Very pleased to have encrypted sessions now for BINKP! :)
This sounds awesome. I may have to actually write a Bink protocol
support for Enig at some point so I can do this as well. I'd love to
drop all plain text protocols.
Very pleased to have encrypted sessions now for BINKP! :)
This sounds awesome. I may have to actually write a Bink protocol
support for Enig at some point so I can do this as well. I'd love to
drop all plain text protocols.
Would be good to have the specs opened up, so all binkp implementations can make use of encrypted sessions.
On 12-16-18 08:34, g00r00 wrote to vk3jed <=-
Would be good to have the specs opened up, so all binkp implementations can make use of encrypted sessions.
Yep, I will try to get it into BINKD or at least accepted by them as
the way they would implement it when they finally do.
I think if BINKD has it then pretty much everyone would accept it as
the standard way to do things.
That would be awesome. And would mean all 3 of my systems would
implement encryption at that point (1 Mystic, 2 binkd).
These are close to the A40 release so please test if you are interested, and let me know of any bugs or suggestions. I'd like to release A40 on XMAS or New Years assuming I do not hear anything back from people.
+ 2018.12.23 21:59:53 BINKP 1-S: NUL TIME Sun, 23 Dec 2018 21:59:53 1300 + 2018.12.23 21:59:53 BINKP 1-S: NUL VER Mystic/1.12A40 binkp/1.0
Just setting up a test version of this pre-alpha and testing things with Al today/tomorrow.
Just sent some secured netmail that was encrypted. leaving my test
system it was all good :) the packet was unreadable and the session between our two systems was secure.
I wonder if the logs should show when something is encrypted as it is exported?
You're welcome, it was only a quick add that only took a few minutes so certainly not a big deal and if it helps you pinpoint issues then it was
a no brainer!
Awesome, thank you and thank Al too. I don't know if he reads here.
Either way, I'll double check and make sure all of them have a message that says its encrypting and decrypting.
Awesome, thank you and thank Al too. I don't know if he reads here.
Awesome, thank you and thank Al too. I don't know if he reads here.
Everyday.. :)
I've updated the pre-alpha releases.
changes to BINKP but I still have a list of things to look into that I haven't yet.
I've updated the prealphas. This has some better logging for the CRC issue that people in Linux seem to be experiencing.
If someone wouldn't mind, please enable CRC checking again and see if it works. If it doesn't please paste in the log showing the CRC values.
I've updated the prealphas. This has some better logging for the CRC issue that people in Linux seem to be experiencing.
If someone wouldn't mind, please enable CRC checking again and see if it works. If it doesn't please paste in the log showing the CRC values.
I've updated the prealphas. This has some better logging for the CRC issue that people in Linux seem to be experiencing.
If someone wouldn't mind, please enable CRC checking again and see if works. If it doesn't please paste in the log showing the CRC values.
CRC checking is enabled. Just waiting for some files to come in... :)
CRC checking is enabled. Just waiting for some files to come in... :)
Great and thank you for testing. I am not really expecting it to work
but I did make a change a few weeks back as you noted earlier. If it fails it should at least print more information about the CRC values.
+ Jan 30 19:03:25 Bad file size; Moved to /home/dan/mystic/echomail/in/badfiles/
According to the .tic file, the size is:
Size 16904
And, according to Ubuntu, the actual file size is 16.9kB(19604 bytes).
As I said, I'm not sure if it's related or not, but just wanted to let
you know what I found. :)
Well thats not a step in the right direction lol. Okay thanks for
letting me know. If you happen to see anything go through or a CRC
error please let me know.
As I said, I'm not sure if it's related or not, but just wanted to le you know what I found. :)
Well thats not a step in the right direction lol. Okay thanks for
letting me know. If you happen to see anything go through or a CRC
error please let me know.
Dan have you moved to the latest A42?
Well thats not a step in the right direction lol. Okay thanks for
letting me know. If you happen to see anything go through or a CRC
error please let me know.
Well thats not a step in the right direction lol. Okay thanks for
letting me know. If you happen to see anything go through or a CRC
error please let me know.
I'm keeping my eyes peeled... :) (You know, that really sounds painful as it's typed out...) ;)
I just re-hatched out the current fsxNet infopack and nodelist to net 4. The infopack (fsxinfo.zip) was sent with the replace verb, while the nodelist (fsxnet.z32) was not.
+ Jan 31 21:05:10 File fsxinfo.zip Area FSX_INFO From 21:4/100
- Jan 31 21:05:10 Replace "fsxinfo.zip"
+ Jan 31 21:05:10 Replacing fsxinfo.zip
+ Jan 31 21:05:10 Added to fsxNet Info
No crc errors... :)
I'm keeping my eyes peeled... :) (You know, that really sounds painfu it's typed out...) ;)
Ouch yeah it does. I actually pictured like one of those old potato peelers too for some reason which makes it even worse.
Hopefully that means I fixed it up. Assuming it was fixed the problem
was that I was using a mixture of 32-bit and 64-bit integers and it
didn't like that.
Updated the pre-alphas, this just has updates to Mystic-DOS which is done except for a few larger but non-crucial commands. A few commands
haven't been tested and almost none of it has been tested on the Unix-based systems yet only in Windows.
DREAM MASTER! Go update to this if you want to test Mystic-DOS and User
to User split screen chat! Don't forget to copy userchat.* into your
TEXT directory though! :)
Upgraded, the spit screen still has an issue where I can not see what I
am typing till I hit enter.
I am planning another one or two updates (just did one now) of the prealphas as I work out the kinks for DOS and chat so keep an eye on the FTP site later tonight if you want to get the latest version. :)
Updated the pre-alphas, this just has updates to Mystic-DOS which is
Upgraded, the spit screen still has an issue where I can not see what am typing till I hit enter.
Okay I tested this in Windows and it works but in a local Linux login I see the same problem. I will investigate thank you
I am planning another one or two updates (just did one now) of the prealphas as I work out the kinks for DOS and chat so keep an eye on FTP site later tonight if you want to get the latest version. :)
Well I lied... It took me like 15 minutes to fix the chat bug in Linux :)
So prealphas have been updated again and that will probably be it for a couple of days as I have a ton of real life work to do. I think I've mostly finished Mystic DOS and worked out bugs in chat and DOS now.
Got it and the user to user now I can see it type when I type live!
Thank you so much g00r00!
Got it and the user to user now I can see it type when I type live!
Thank you so much g00r00!
Pardon the ignorance {chuckle} but what exactly is Mystic-DOS and how do you use it? Started out with MS-DOS 2.1 in the mid 1980's and have
always favored DOS over the rest. :)
Pardon the ignorance {chuckle} but what exactly is Mystic-DOS andIts just a shell that allows you to manage files, and do other BBS
stuff from it like edit text and ANSI, chat with users, run python or
mpl, zip/unzip files, etc. Its just a menu command you can run and
its now on the SysOp menu by default as of the latest prealpha.
Can't wait for Exec command {chuckle} will I be able to call a native windows program with it?
I just updated the prealphas again for Intel Linux and Windows.
This has a few bug fixes (I didn't get to look into everything on my list yet) and adds a few echomail related features.
Keep in mind this also has the new file moving code so we'll see how that goes. I am about to upgrade my own Linux BBS.
Checked these out and wow, loving these. =D
v1.12 A43 Linux/64 Compiled 2019/02/15 01:03:07
patches. My new challenge is to build a way to make Mystic update itself so I never have to use anything other than Mystic-DOS to do upgrades.
Checked these out and wow, loving these. =D
v1.12 A43 Linux/64 Compiled 2019/02/15 01:03:07
Awesome, let me know if you have any issues. I haven't got through my list yet but I did address some of them in this build.
This idea of putting Mystic on a remote Linux machine and modding/configuring it via nothing but Telnet and Mystic has been really fun. Its causing me to get off my butt and finish a bunch of ideas I've had like Mystic-DOS, those Echomail functions, encrypted Netmail, etc.
The only time I cheat has been to deploy new alphas or install OS
patches. My new challenge is to build a way to make Mystic update itself so I never have to use anything other than Mystic-DOS to do upgrades.
Now THAT will be an awesome idea! A menu command for a SysOp to run and
it performs an update automagically.
patches. My new challenge is to build a way to make Mystic update itself so I never have to use anything other than Mystic-DOS to do upgrades.
On 02-15-19 12:48, g00r00 wrote to Pequito <=-
The only time I cheat has been to deploy new alphas or install OS
patches. My new challenge is to build a way to make Mystic update
itself so I never have to use anything other than Mystic-DOS to do upgrades.
You know what I think would be cool - if you made Mystic a docker container (and I'm happy to help you with that). You may recall that I
And, if you went down a docker path, you would change your "support" from supporting different OS's to just supporting Linux on different architectures (Pi and Intel mostly I guess). Docker's pretty stable now
The only time I cheat has been to deploy new alphas or install OS patches. My new challenge is to build a way to make Mystic update itself so I never have to use anything other than Mystic-DOS to do upgrades.
If you pull that off, it would be impressive!
I don't think I would ever make Mystic docker-only but I certainly don't mind developing features that will help it run better in Docker, if someone else (you?) wanted to maintain an unofficial docker build.
To be honest I am not too familiar with the platform other than having a basic idea of it what it is, so it'd be something I would need to spend some more time with.
but we'll see! Maybe I'll give it a shot this weekend!
If you get a chance in the near future. Perhaps you could take a look at Mystic creating the filebox directory. As soon as you tell Mystic to create it, Mystic will crash. It happens in the Win/32 version. I
haven't tried it on the Linux version in awhile, so I'm unsure...
On 02-15-19 20:05, g00r00 wrote to Vk3jed <=-
If you pull that off, it would be impressive!
I don't think it should take more than a couple lines of a shell
script, but we'll see! Maybe I'll give it a shot this weekend!
On 02-15-19 19:00, Black Panther wrote to g00r00 <=-
On 15 Feb 2019, g00r00 said the following...
but we'll see! Maybe I'll give it a shot this weekend!
If you get a chance in the near future. Perhaps you could take a look
at Mystic creating the filebox directory. As soon as you tell Mystic to create it, Mystic will crash. It happens in the Win/32 version. I
haven't tried it on the Linux version in awhile, so I'm unsure...
Thank you. :)
Nah, its just a small .sh file that looks to see if the update is in a folder on the drive and if so it runs "./install replace /mystic" to
copy over the new binaries. The idea is to copy the files into that folder and the run a "DOOR ./mis shutdown" which should kick me off,
copy over the new binaries, and restart itself.
I can already recompile MPL programs and deploy any new files in a
release by just executing "DOOR ./mplc -all" or "DOOR ./install extract userchat* /mystic" for example using Mystic-DOS. I just can't replace
the MIS and Mystic binaries while they're running, so that part I will script.
On that note though:
I did try to do a fully automated update in the past. I needed to do
the theme change first because there are various issues with prompts and custom themes if updating were to be automated fully. Too many people complained about my directory revamp that was designed to make this much much easier, so it never happened.
I don't think I would ever make Mystic docker-only but I certainly don't mind developing features that will help it run better in Docker, if someone else (you?) wanted to maintain an unofficial docker build.
You and me both. Does anyone have a spare 24 hours they want to give
away for free??
If you get a chance in the near future. Perhaps you could take a look at Mystic creating the filebox directory. As soon as you tell Mystic to create it, Mystic will crash. It happens in the Win/32 version. I
haven't tried it on the Linux version in awhile, so I'm unsure...
Nevermind... I just set up a new node on the Win/32 system, and didn't have any issues... Sorry about that...
I don't think it should take more than a couple lines of a shell script, but we'll see! Maybe I'll give it a shot this weekend!
I can see this going one of 2 ways. Either it'll be dead simple or "famous last words!" :D
I can already recompile MPL programs and deploy any new files in a release by just executing "DOOR ./mplc -all" or "DOOR ./install extra userchat* /mystic" for example using Mystic-DOS. I just can't replac the MIS and Mystic binaries while they're running, so that part I wil script.
Again very useful to know, this is great information.
Yeah the small modification to the theme / prompts weren't too bad for me seeing as I don't really have much customised yet in that respect,
however I could see that being a pain for others... and to automate it would be tricky. Shame people complained about the directory revamp, it sounded like a logical step forward to me.
My first request, can you make the install unattended? Or as an alternative, how do I get the install files out of the package (and pre-configure mystic.dat)?
(It might be useful to have a "temp_path" as well - I would probably have that as a tmpfs/ramdisk, and that might be useful for non-docker users
too - especially those using a SD card device like a Pi :)
* Data - Ultimately, this needs to end up outside the container (for persistance) and its easier if its is prefixed by one path. I use /mystic/data. So /mystic and /mystic/* is inside the container, except /mystic/data which is outside. In OS terms, its another block device. (Hence my cross block device issues that you've been working on.)
I woke up today (Saturday for me) with work I still need to finish from the previous week. Then I go downstairs to get a drink and I am immediately asked to do chores. By the time I get the work done and the chores done and something to eat etc 2/3rds of my "day off" will be gone.
And I don't even have kids. I don't know how you do it!
All of this stuff was in the Mystic 2.0 demo I released a few years
back, but people voted to have me continue on 1.0 instead of working on that too lol
The secret is - don't go downstairs :)
patches. My new challenge is to build a way to make Mystic update itself so I never have to use anything other than Mystic-DOS to do upgrades.
On 02-16-19 14:04, g00r00 wrote to Vk3jed <=-
You're completely right lol
I still haven't tried it, so we'll see! The good thing about this
little experiment I am doing is that if I can't get it working, I
change Mystic so I can!
I haven't even gotten far into the installation yet and I've already
been making so many changes. I was just using the text editor and had
a need to jump to a line number. Thats a stopping point. Time for
that idea to come off of my TODO list so I can finish editing that text file!
At this rate I'll have this version of my BBS done by 2030 but we'll
have tons of new stuff!
On 02-16-19 13:52, g00r00 wrote to Avon <=-
I woke up today (Saturday for me) with work I still need to finish from the previous week. Then I go downstairs to get a drink and I am immediately asked to do chores. By the time I get the work done and
the chores done and something to eat etc 2/3rds of my "day off" will be gone.
On 02-17-19 12:06, Avon wrote to g00r00 <=-
The secret is - don't go downstairs :)
The secret is - don't go downstairs :)
LOL clever! :D
only if you can suss how to get food in without anyone noticing :)
Hah
On 17 Feb 2019 at 05:10p, Vk3jed pondered and said...
The secret is - don't go downstairs :)
LOL clever! :D
only if you can suss how to get food in without anyone noticing :) Hah
There are already some utilities that I've already mentioned but it
sounds like it may not be all that useful for what you need:
I really really really want to do this (and the entire directory
revamp), so in order for this to happen we may be forcing people to
change their door configurations.
Okay so question then about text files, menus, and scripts. Would those need to be stored outside of Mystic as well assuming people were going
to make heavy changes from the defaults?
However, at the moment, I have it all outside,
(/mystic/data/custom_theme and ) because
While building a docker container (which represents an "installed applications"), naturally I can move stuff around as part of the
install. The hard part is configuring mystic.dat (since its a binary file), so that when it starts, it knows where everything is (and that is what install does initially, but its interactive).
If I do the directory revamp, I may also do the relative paths that were also in the 2.0 demo and that will eliminate this issue, but I will do
the automated install for now at the very least.
g00r00 wrote to Black Panther <=-
Nevermind... I just set up a new node on the Win/32 system, and didn't have any issues... Sorry about that...
Of course I went to test it before I read the next message :P
I think I noticed that on my own a bit ago and fixed it up. Or maybe
you or someone else reported it. But I vaguely remember working on it.
Maybe? I don't know but its working so good enough!
I havent seen this infamouse v2.0 demo. I'm a little surprised also that folks are against (or rather didnt want to a adopt it).
Folks could always stay on v1 release if they wanted to - the
"standards" are in the protocols used ( although I have to be careful where I use that word on fidonet networks :P )
On 02-17-19 19:34, Avon wrote to Vk3jed <=-
only if you can suss how to get food in without anyone noticing :) Hah
On 02-17-19 08:36, g00r00 wrote to deon <=-
In the 2.0 demo you can rename the root Mystic directory and everything still works with no configuration changes. You can copy it to a
different drive and everything still works. You can even copy it from Windows to Linux and then later to OSX to Pi and everything still works without any configuration change.
I was shocked when people were really against me bringing this into
Mystic 1
You and me both. Does anyone have a spare 24 hours they want to give
away for free??
I don't remember this discussion, though I do recall the 2.0 demo (have
a copy installed on this Windows PC actually). I personally would
support this change to paths, it just makes things so much easier.
On 02-18-19 07:15, g00r00 wrote to Vk3jed <=-
There was a pretty substantial back and forth about the paths. It
might have been that I was put off by all the resistance I was getting
so I picked up 2.0 again which would make sense... but I can't quite remember the exact order of events.
I had a 2.0 demo back around 2003 too which was also voted down by the alpha team at the time. I seem to produce once about every 10 years or
so that never goes anywhere. Next one is currently due in the
2023-2025 range so stay tuned! lol
was wondering if the events section has been fixed?
I run ./mis -server, and have noticed that mystic is
ignoring my echomail.in event - it should run "z"
which runs mutil, then updates my ip
but all it runs is "mutil" ???
Updated prealphas for all platforms. Should fix menu settings
was wondering if the events section has been fixed?
I run ./mis -server, and have noticed that mystic is
ignoring my echomail.in event - it should run "z"
which runs mutil, then updates my ip
but all it runs is "mutil" ???
I've been running events for years no problems, and there are no reported issues at the moment although I am using the "default" events or all my echomail processing.
Can you post your event so we can take a look?
it is just the "Toss incomming echomail, I change it to run my script,
and at somepoint, mystic re-verts back to the original entry??
should I shutdown mis after changing the event?? if so, how about adding
a prompt to remind us that we need to restart the server or daemon ???
$c mci code, blank prompts crashing, seenby, pkt header, 2020 date, smtp not sending ehlo after SSL step up and so on.
To upgrade from previous prealpha just replace all your .exe files you
can do that with "install replace c:\mystic\"
To upgrade from previous prealpha just replace all your .exe files you
can do that with "install replace c:\mystic\"
Hey g00r00, I volunteer to do any linux upgrade testing if you like. Feel free to email me separately - ryanfantus@gmail.com - I'm happy to be the linux guinea pig as needed. :)
Presumably replacing the binaries with the new ones is all that would be required here as well?
Also, FYI, I have some systemd scripts for automating some Mystic stuff. Let me know if you'd like to get a look at those, perhaps for placing in the wiki or docs.
Awesome, thanks g00r00! I hate to add another one to the list, but would it be possible to remove the SMTP username/password character limits? AWS auto-generates some really long username and password combos for their SMTP services.
To upgrade from previous prealpha just replace all your .exe files yo can do that with "install replace c:\mystic\"
Just a heads up for the win32 test build I have been starting to update this feature does not work as directed and just fires up the main
install UI menu.
Mystic BBS Installation Utility Version 1.10 A53
Copyright (C) 1997-2014 By James Coyle. All Rights Reserved.
I am updating prealphas with some fixes and changes including several to BINKP that I would appreciate getting tested. They will be up in about
5 minutes or less.
I am updating prealphas with some fixes and changes including several to BINKP that I would appreciate getting tested. They will be up in about
5 minutes or less.
I am updating prealphas with some fixes and changes including several BINKP that I would appreciate getting tested. They will be up in abo 5 minutes or less.
Just checking is it build v1.12 A45 Windows/32 Compiled 2020/02/15 20:28:45 ??
I am updating prealphas with some fixes and changes including several to BINKP that I would appreciate getting tested. They will be up in about
I am updating the Prealphas today it should be done in a few minutes.
This update will have some changes to the new MIS POLL to fix display errors and to introduce some other statistical tracking.
The MUTIL [EchoMailTracker] is enabled but if you decide to try it
please be very careful because it has not had a good run through of testing yet. I will be setting up some test cases for these features soon.
I would love assistance if someone wants to try it, but I recognize this is mostly for HUBs where they may not want to risk restoring if
something doesn't work.
At the very least MIS POLL seems stable and complete though in this
build.
I'm going to try and get the SSH going on 24553 first. If anyone wants to test this at 21:1/100 please let me know.
The port should now be open and the server running.
I just tried it and it couldn't connect. Is the port behind a firewall
by chance? Could of couse be a bug. I should retest locally to make
sure I didnt break anything.
I'm going to try and get the SSH going on 24553 first. If anyone wants to test this at 21:1/100 please let me know.
The port should now be open and the server running.
I can connect, but I get an authorization failure:
--------------------- POLL v1.12 A46 2020/03/01 Sun, Mar 01 2020 (loglevel 2) + 2020.03.01 09:13:47 Polling all nodes of session type ALL + 2020.03.01 09:13:47 1-Polling 21:1/100 on slot 1 via BINKP
+ 2020.03.01 09:13:47 1-Connecting to agency.bbs.nz on port 24553
+ 2020.03.01 09:13:47 1-Connected by IPV4 to 219.89.83.33
+ 2020.03.01 09:13:48 1-Connection lost
+ 2020.03.01 09:13:48 1-Authorization failed
+ 2020.03.01 09:13:49 Polled 1 systems
I have scbbs.nsupdate.info:24553 up and running if you'd like to try a forced send to me or similar. =)
I just tried it and it couldn't connect. Is the port behind a firewa by chance? Could of couse be a bug. I should retest locally to make sure I didnt break anything.
I'm fairly sure its open. will keep playing, just posted some stuff to
the echo about this :)
Found the issue I believe, and I am uploading a new version as I type this.
Thanks :)
Getting late here but will try to update and test before eyeballs fall
out
I can connect, but I get an authorization failure:what I see internally when I force the BinkP Hostname to include a port number.
I have a feeling g00r00 may spot something soon.
I removed :24553 from your hostname in my echomail node configuratoin
and now it seems to poll you OK over SSL:
I removed :24553 from your hostname in my echomail node configuratoin
and now it seems to poll you OK over SSL:
--------------------- POLL v1.12 A46 2020/03/01 Sun, Mar 01 2020 (loglevel 2) + 2020.03.01 09:52:48 Polling all nodes of session type ALL + 2020.03.01 09:52:48 1-Polling 21:1/100 on slot 1 via BINKP
+ 2020.03.01 09:52:48 1-Connecting to agency.bbs.nz on port 24553
+ 2020.03.01 09:52:51 1-Connected by IPV4 SSL to 219.89.83.33
But then you should have been able to poll me as well? Hmm...
I have a feeling g00r00 may spot something soon.
Perhaps something related to Cryptlib on Windows?
Best regards
Well good news I just successfully exchanged via SSL with you. So at least its working with another Mystic system.
Hopefully eyeballs have preserved and will live another day!
I think thats just a timing thing. We are swapping versions as you're testing this stuff :)
No joy... but it may be your build needs an update to..
I just upgraded my L64 version as well (downloaded it 5 minutes ago),
and it seems to (still) poll just fine using SSL.
Great to hear and that will save me some time.
I think its time for me to go do something else for a few hours this evening for my own sanity. :)
Thanks for helping to test!
Deon and Al - yep to more tests, will look to do so tomorrow.
I'll setup Hub 3 to receive inbound TLS - and send the details.
OK, hub 3 is on alterant.leenooks.net:24556 (synchronet windows), and
my BBS 2/116 is on alterant.leenooks.net:24553 (synchronet linux).
I'll setup Hub 3 to receive inbound TLS - and send the details.
OK, hub 3 is on alterant.leenooks.net:24556 (synchronet windows), and
my BBS 2/116 is on alterant.leenooks.net:24553 (synchronet linux).
I have tried both of these. It connects but fails for some reason, something about the certificates.
I have tried both of these. It connects but fails for some
reason, something about the certificates.
Maybe its the TLS < v1.2 situation?
I have tried both of these. It connects but fails for some reason, something about the certificates.
Maybe its the TLS < v1.2 situation?
So, I can't poll Synchronet or Mystic presently with binkd. Can you try polling
here?
So, I can't poll Synchronet or Mystic presently with binkd. Can
you try polling here?
Error in recv() of first byte of packet header
Although, "Error in recv()..." not sure what you see on your side...
There is no mention of errors in my log but I have now turned up the verbosity so it may show more now. Also in my setup the tls is done by openssl so it is not logged by binkd.
OK, hub 3 is on alterant.leenooks.net:24556 (synchronet windows), and my
Anybody who wants to test binkps is welcome to.
Although I do see "timeout receiving first byte of packet..." so not
sure why it thinks a packet is transferring..
Interesting, I also see "Will Encrypt Session", which seems redundant
if its a TLS session - but I'll pay more attention when there is some
mail flow and check with DM if it continues.
Let me know if you want a password so that you can pull some packets
from Hub 3.
If you can set my node up and send me the details I'll setup likewise. If we get incomunicado somehow you can email me at agianson {at} gmail {dot} com
If you can set my node up and send me the details I'll setup
likewise. If we get incomunicado somehow you can email me at
I've been reading the ongoing discussion on binkps and I would like to join the "fun" if you will. I'm all about using SSL wherever possible.
I've also noticed A46 introduces a new mis poll, is there action(s) I'll need to take to get my networks functional once I upgrade?
their ssl.cert in DATA folder but that remains to be confirmed. And its also possible this will break compatibility with Synchronet).
Have we worked out what the issue is?
20:59:59 Poll BINKP node via address lookup: 21:3/100
20:59:59 1-Polling 21:3/100 on slot 1 via BINKP
20:59:59 1-Connecting to alterant.leenooks.net on port 24556
20:59:59 1-Connected by IPV4 to 101.186.5.106
21:00:31 1-Data frame timeout
21:00:31 1-Connection lost
21:00:31 1-Authorization failed
21:00:32 Polled 1 systems
If you want to use SSL with BINKP you will need to upgrade to the latest A46 prealpha (and there is potential that everyone will need to delete their ssl.cert in DATA folder but that remains to be confirmed. And its also possible this will break compatibility with Synchronet).
As of now I don't know any issues with Mystic. Are you using the latest release and are the system you're connecting with?
I was under the impression that Avon gave you some details and it seemed to be port issues. IE: When trying to connect to a "non standard" (in
this case not 24553), MIS was doing unusual things. I havent really been
I am updating the prealphas with a couple minor features and fixes for Windows and Linux. Should be available in about 5 minutes.
! Fixed a bug with BINKP where Mystic could send a 0 byte length data frame if a file size was exactly evenly divisible by the buffer size.
[snip]
Hopefully that may solve the issue the HUBs have been experiencing?
So it seems like there could be a series of different issues. I have added more detailed poll.txt and it will also create ssl.txt if it gets
an SSL read error. But on that note, I haven't had any issues with the latest build (yet).
I'm picking you must have updated the build again today then, as I am not seeing any ssl.txt logging in the one I applied this morning (my time)
That should be because you haven't had any SSL read errors. :)
I did not update it again.
Updated the prealphas. Very minor changes in this one.
Updated the prealphas. Very minor changes in this one.
Is there a ARM/Pi prealpha version? Didn't see it in the dir...
Updated the prealphas. Very minor changes in this one.
Updated the prealphas. Very minor changes in this one.
Thanks!
I noticed there is a prompts.bak in the data directory (when performing a fresh install) -- is that one needed for anything? =)
I also managed to get "Error 0" when polling HUB 1 two times in close
On 12 Mar 2020 at 04:22a, g00r00 pondered and said...
Updated the prealphas. Very minor changes in this one.
all three HUBs running Mystic are now on that 'latest' build.
If you see sometihng like this happen again please let me know. I did
Awesome, thanks g00r00! I hate to add another one to the list, but wo it be possible to remove the SMTP username/password character limits? auto-generates some really long username and password combos for thei SMTP services.
Yeah we can get that expanded. Its probably limited to what it is
because I didn't want to change the data file formats. Worst case it
will have to wait until A45 since I already sent out the A44 upgrade but maybe I can figure something out.
Awesome, thanks g00r00! I hate to add another one to the list, b it be possible to remove the SMTP username/password character li auto-generates some really long username and password combos for SMTP services.
Yeah we can get that expanded. Its probably limited to what it is because I didn't want to change the data file formats. Worst case it will have to wait until A45 since I already sent out the A44 upgrade maybe I can figure something out.
I'm not sure if this is always consistent with AWS but in my case the username is 20 characters and the password is 44 characters long
(brutally long I know) :(
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 31 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 245:19:03 |
| Calls: | 2,090 |
| Calls today: | 1 |
| Files: | 11,140 |
| Messages: | 948,886 |