I wonder. How do You proceed with the bot's scanners? I mean I opened
the BBS to the world and all I got was just scanning and bot connecting with default passwords. And after several days I usually found my BBS's binaries corrupted. I don't know whether anyone exploited the open
access or it was my fault. But how to handle this kind of situations?
I wonder. How do You proceed with the bot's scanners? I mean I opened
the BBS to the world and all I got was just scanning and bot connecting with default passwords. And after several days I usually found my BBS's binaries corrupted. I don't know whether anyone exploited the open
access or it was my fault. But how to handle this kind of situations?
On 02/12/18, shinobi said the following...
I wonder. How do You proceed with the bot's scanners? I mean I opened the BBS to the world and all I got was just scanning and bot connecting with default passwords. And after several days I usually found my BBS's binaries corrupted. I don't know whether anyone exploited the open access or it was my fault. But how to handle this kind of situations?
Well, I am from Brazil, so you can imagine that my system gets pounded with scanners all the time.
I have restriced access with the country blocker to accept calls only from Latin American countries, Canada, the USA and a few European countries and I did not have any further issues... In my case when I blocked Asia my system stopped to crash due these scanners.
I wonder. How do You proceed with the bot's scanners? I mean I opened the BBS to the world and all I got was just scanning and bot connecting with default passwords. And after several days I usually found my BBS's binaries corrupted. I don't know whether anyone exploited the open access or it was my fault. But how to handle this kind of situations?
This is the reality on port 23. I don't think any of that will be a problem for Mystic but it can be a pain to watch. You could try using a non standard port like 2323 or somesuch.
They will hammer away but they are not going anywhere and are not much more than an eye sore.
Personally, never had this kind of issue. From the start i chose a
"weird" port(9999) and even my badip file is empty. :)
I have restriced access with the country blocker to accept calls only from Latin American countries, Canada, the USA and a few European countries and I did not have any further issues... In my case when I blocked Asia my system stopped to crash due these scanners.
It's unfortunately true. I had to do the same and the scanners are at a minimum now. Although can't say that I've ever crashed due to them.
I run the BBS on port 23 here. I get plenty of bots hitting the BBS, and
I silently chuckle when the bot is confronted with an ANSI login screen instead of the usual Linux prompt it's looking for :) I just spawn more sessions to make sure there's always an open session to connect to.
You could try using a non standard port like 2323 or somesuch.
It's unfortunately true. I had to do the same and the scanners are at a minimum now. Although can't say that I've ever crashed due to them.
That's a good idea. I wonder why most of the attacks come from Russia and Asia. I guess there is plenty of unsecured computers included in botnets.
This is the reality on port 23. I don't think any of that will be a
problem for
RE: Under bot scanning
BY: Al(21:4/106)
This is the reality on port 23. I don't think any of that will be a problem for
I would like to see more bbses using the standard port. If the bbs
crashes when bots connect, the solution isn't to move to a different
port, it's to fix the bbs. Agree that it's merely an eye sore and not a threat. Trying to figure out which weird port this or that bbs is listening on just makes the bbs less accessible.
On 02/12/18, CyntaxX said the following...
It's unfortunately true. I had to do the same and the scanners are at minimum now. Although can't say that I've ever crashed due to them.
I run my system at port 23, so I get a couple of Runtime errors due
to that from time to time...
On 02/13/18, shinobi said the following...
That's a good idea. I wonder why most of the attacks come from Russia Asia. I guess there is plenty of unsecured computers included in botn
I do get bots from the USA, for instance, but they are rare. Never understood why.
But after restricting China, India, Taiwan and Korea, the bot infiltration rate started to dwindle.
This is the reality on port 23. I don't think any of that will be a
problem for
I would like to see more bbses using the standard port. If the bbs crashes when bots connect, the solution isn't to move to a different port, it's to fix the bbs. Agree that it's merely an eye sore and not a threat. Trying to figure out which weird port this or that bbs is listening on just makes the bbs less accessible.
I would like to see more bbses using the standard port. If the bbs
crashes when bots connect, the solution isn't to move to a different
port, it's to fix the bbs. Agree that it's merely an eye sore and not a threat. Trying to figure out which weird port this or that bbs is listening on just makes the bbs less accessible.
I would like to see more bbses using the standard port. If the bbs
crashes when bots connect, the solution isn't to move to a different
port, it's to fix the bbs. Agree that it's merely an eye sore and not a threat. Trying to figure out which weird port this or that bbs is listening on just makes the bbs less accessible.
I run on 2323 and I only ever get bots from Japan.
I noticed your InterBBS video poker release. I was checking things over and I couldn't help but notice that the method for sending IBBS data was
a bit kludgy, what with having to form a mutil.ini file and running
mutil to post the file. I'm pretty sure that an MPY script can be used
to do the same thing. Just call the MX menu command within the MPY to post the file to the echomail area, like double-up does within the MPL script. Your outgoing ibbs.mpy script can read the same ibbs.ini file
to gather the needed info when calling the MX command.
I think I can whip something up if you want. Let me know what you think.
I noticed your InterBBS video poker release. I was checking things o and I couldn't help but notice that the method for sending IBBS data a bit kludgy, what with having to form a mutil.ini file and running mutil to post the file. I'm pretty sure that an MPY script can be us to do the same thing. Just call the MX menu command within the MPY t post the file to the echomail area, like double-up does within the MP script. Your outgoing ibbs.mpy script can read the same ibbs.ini fil to gather the needed info when calling the MX command.
I think I can whip something up if you want. Let me know what you th
Sure! :) I am not very familiar with Python and MPY. I start learning
some weeks ago. If you saw the package, i used your MPY script for
getting the score but for sending them, i didn't have another option. If you can write also a script for sending msg, will be great :)
But i have a question about that. To execute a MPY script we must
execute it using Mystic. If the user all ready runs the game, an
instance of Mystic will also be running. Is it safe to invoke another instance of mystic, only to run another script? Also, to execute the MPY script we should use something like ./mystic -uuser -ppass -yscript...
If i remember correct, because i did some tests with another script, the problem is that mystic loads up, but before executing the scripts, waits for a response ex. terminal, theme etc. end because this command will be in the background the user can't enter anything so it stays like this doing nothing. :(
I made the door to use any external command, so the sysop can use
whatever way prefers for sending/receiving the data. Maybe there are
other ways too. In the past i tried writing a program to read JAM bases externally (out of mystic) but i had some troubles and dropped the project. I can't understand why there aren't many JAM Libraries to read/write msg bases. I know there is one for PERL ,but i don't know a
bit about PERL and some very old units for Pascal. A Python library
would be great, to be more cross system compatible. This way we could
have a nice way to send/receive msgs/data through JAM files.
Quoting Nighthawk to Outatime <=-
I agree with you, and that's why I am running Saturn's Orbit on
port 23.
I run the DOS board on port 23. Netfoss handles all those BS connections pretty well so I've never worried about it.
Magicka defaults to 2023 so that's where it runs. If I ever totally do
away with ezycom I'll cross the port bridge when I come to it. :)
I think that you are over thinking it. If you look at my sbbl.mpy app,
it gives an example of posting a file to an echo base using the MX menu command with the menucmd() function.
Begin
GetThisUser;
MenuCMD('GY','vpibbs');
MenuCMD('DD','/home/bbs/doors/videopokerx/videopokerx
'+CfgSysPath+'temp'+Int2Str(NodeNum)+PathChar+'DOOR.SYS');
MenuCMD('GY','vpibbs_out');
End;
| Sysop: | altere |
|---|---|
| Location: | Houston, TX |
| Users: | 60 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 01:31:37 |
| Calls: | 516 |
| Files: | 7,014 |
| Messages: | 287,623 |