Has anyone else noticed that when a user telnets out from the BBSlist
door to another Mystic BBS in the list of boards. If the person (for whatever reason) changes their mind and doesn't login using a handle or name. Mystic just goes down the screen over and over.. forever.. without disconneting the caller after so many times of a [blank] noname input.
Has anyone else noticed that when a user telnets out from the BBSlist
door to another Mystic BBS in the list of boards. If the person (for whatever reason) changes their mind and doesn't login using a handle or name. Mystic just goes down the screen over and over.. forever.. without disconneting the caller after so many times of a [blank] noname input.
Has anyone else noticed that when a user telnets out from the BBSlist
door to another Mystic BBS in the list of boards. If the person (for whatever reason) changes their mind and doesn't login using a handle or name. Mystic just goes down the screen over and over.. forever.. without disconneting the caller after so many times of a [blank] noname input. Needless to say, this is getting logged on the other board with the connection IP address. Anyway, I can't remember if this as already been fixed or not. But mystic should be disconnecting callers after like
maybe 3 tries. That way the telnetdoor can dump the caller back to the systems door they where using. My config will abort after 3 incorrect password a-temps. But what happens if the caller doesn't even enter a
name or handle? (hence, it scrools down the page),. anking over and over what is the user name. This is a problem... because in the example that
i saw happen, the users just ended up closing the connection completly. Closing the connection on both systems. They also were probably
wondering WTF was that all about, or didn't give it a second thought (:
recommend using Rick Parrish's TelnetDoor. Maybe that app is the issue
On 01/01/15, Skuz said the following...
Has anyone else noticed that when a user telnets out from the BBSlist door to another Mystic BBS in the list of boards. If the person (for whatever reason) changes their mind and doesn't login using a handle name. Mystic just goes down the screen over and over.. forever.. with disconneting the caller after so many times of a [blank] noname input
i just tried this with my board and just telneting in. i hit enter at the matrix to log on and then enter on the username screen and it
bounces back to the matrix. so i just hit enter 100 times and it flips between screens and never disconnects.. should have so,ething set to disconnect after so many failed attempts..
this only happened to me in the shuttle login, appears to work without
it. without the shuttle login, it disconnects after the configured amount of times is reached. havn't tried it in a long time, dont know if it still happens.
Exactly !!! Depending on whatever the board as setup (Matrix or No
Matrix) If a caller doesn't logon with a user name and keeps hitting
Enter over and over (expecting that they are going to get disconnected). That doesn't happen! like you would think. They end up dropin the
i just tried this with my board and just telneting in. i hit enter at~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
the matrix to log on and then enter on the username screen and it bounces back to the matrix. so i just hit enter 100 times and it flips between screens and never disconnects.. should have so,ething set to disconnect
after so many failed attempts..
If it's sending you back to the mtarix, the matrix should have a logoff
or disconenct option. If it doesn't thats bad design on the system's part, It's not the same as entering a bad password (3) times for
invalid login.
If it's sending you back to the mtarix, the matrix should have a logoff
or disconenct option. If it doesn't thats bad design on the system's part, It's not the same as entering a bad password (3) times for
invalid login.
On 01/01/15, Skuz said the following...
Has anyone else noticed that when a user telnets out from the BB door to another Mystic BBS in the list of boards. If the person whatever reason) changes their mind and doesn't login using a ha name. Mystic just goes down the screen over and over.. forever.. disconneting the caller after so many times of a [blank] noname
On 01/01/15, Kidd Wicked said the following...
i just tried this with my board and just telneting in. i hit enter the matrix to log on and then enter on the username screen and it bounces back to the matrix. so i just hit enter 100 times and it flip between screens and never disconnects.. should have so,ething set to disconnect after so many failed attempts..
Exactly !!! Depending on whatever the board as setup (Matrix or No
Matrix) If a caller doesn't logon with a user name and keeps hitting
Enter over and over (expecting that they are going to get disconnected). That doesn't happen! like you would think. They end up dropin the connection, and since where talking about telneting out from another board... with the Blam script (it doesn't matter of it is windows linux
or any other OS. The connection drops on ALL systems. Not a good practices.. It seems your the only one that understands the point i'm trying to make here. Sure the telnet door works great, if the user logon nornal. But, if he is a dickhead... lol or just doesn't know wtf their doing.. 100% of the time.. what happens? Correct! They drop the connection. Meaning, both system are effected. The only fix i see here,
is to make sure Mystic can closing a connection first before the caller drop carrier in the telnet door. Yes I uses the blam script in both windows and linux and the was tested by teneting to A Missing Chromosome marabbs.no-ip.org ... also a mystic board (without the matrix login). Anyway a failed lohin attemp will scrool down the screen. Unlike, KW
test of bouncing back and forth between the logon handle screen and the matrix. Logic states this is a universal mystic problem, pi (pun-intended)
Is this a Mystic problem, or a telnet client problem? What OS are you using? The only outbound telneting from the BBSList that I know of is my BLAM app. That requires the use of a 3rd party telnet client in order to telnet out from Mystic. For my linux setup, I just use the default
telnet client that comes with my distro. If you're using windows, I had recommend using Rick Parrish's TelnetDoor. Maybe that app is the issue then?
recommend using Rick Parrish's TelnetDoor. Maybe that app is the iss
I use this here and it works great!
What you are saying is true, but... If someone wanted to have a menu redraw over and over again, it really doesn't matter what BBS software
or menu you are talking about. They can do the same thing as you are describing... anywhere.
I could make a script to login to Pharcyde which runs Synchronet and do nothing but type "T" and "Q" over and over again to move to the Transfer menu to the Main menu. The only thing that can stop that is time per
I did the math and I can break it down for you if you want, but if you spammed Mystic matrix with a 2000 byte menu for 30 minutes (the default limit) you'd eat ~3.5 *megabytes* of bandwidth. The average webpage is
No its not endless, just maybe longer than you'd like! ;) By default it can only display 1800 times before Mystic will disconnect them. Thats a fry cry from millions.
2) You don't have to do #1 anymore because in A60 it will disconnect the user if XL (Matrix login menu command) is called more than "Login/Matrix->Login Attempts" number of times! in a single connection!
And its not just my board, it does it at Distortion and Clutch and anyone that runs a matrix logon.. There is a failed logon attempts
setting for the matrix but it does not seem to be working..
Well, if it is a failed login attempt, it happens. If the do login
with a name and get the password wrong. It disconnects after the configured amount of times is reached, correct. My point is they don't
do anything when ask to login except HIT their ENTER key several times before they drop carrier in the BBSLIST blam script. I'm sure it would
do the samething on a normal menu type telnet to another board setup.
I guessing that i'd need to try it again and see what happens. It
might depend on what version of mystic being used. But so far.. all
thing point to something that has not been addressed yet. Again I
could be wrong about this. Oh well, back to watching the new Hobbit.
Exactly !!! Depending on whatever the board as setup (Matrix or
No Matrix) If a caller doesn't logon with a user name and keeps
hitting Enter over and over (expecting that they are going to get
disconnected). That doesn't happen! like you would think. They
end up dropin the
It should be like 5 failed username entries and them disconnect..
My matrix has a logoff option.. But if someone wanted to be an
asshole to me all they have to do is sort of a "ping of death" with
the enter key.. I could write a script to just send the enter command 10000000 times when it makes a connection and my system would switch between the matrix and login screen as fast as it can without logging
off from failed attempts. the reason being is when you log on to my
system my lightbar is on the "logon to bbs" selection.. you hit enter. then when the user logon screen comes up and you just hit enter
instead of typing in a user name it kicks you back to the matrix
screen.. then you hit "enter" at the matrix... Endless "enter" loop..
Try it.. bbs.sinnershaven.com... well just not a million times...:)
On 01/03/15, Kidd Wicked said the following...
And its not just my board, it does it at Distortion and Clutch and anyone that runs a matrix logon.. There is a failed logon attempts setting for the matrix but it does not seem to be working..
there is? i see one general "Login Attempts" setting but not another one specific to the matrix thing...
This is why I hate reading messages in two different places (read them
on my BBS first). I already know the outcome of this, so why do I reply
to earlier posts? :)
You could always make the "Logoff" option the first one that the matrix starts on. That way anyone trying to do something ridiculously annoying like that will end their call immediately. LOL
I'm kidding! It was much more funny while I was writing it. :)
Ok, I know what you are talking about. When telnetting out from a
mystic bbs as a door, and when things get hosed, the only thing to do is to hang up, and that hangs up on all the systems, not just the one thats hosed.
What I've found, is that most telnet outbound clients will let you disconnect with the '^]' (CTL-right-bracket) command. If you do that, then you should be able to drop the hosed connection, while keeping your original connection. I admit, that is something that you will need to train your users to do, since it's not some menu option you can envoke.
While we're on the subject, there is another issue that occurs when you use the outbound telnet feature with Mystic; you cannot do file xfers. While we're on the subject, there is another issue that occurs when you use the outbound telnet feature with Mystic; you cannot do file xfers. They at least won't work with the linux client that I use on Cyberia.
It may be that other telnet clients will work, but I haven't found one
to work yet.
One question regarding your original issue tho... does this only happen when doing outbound sessions from the BBS? If you used your terminal program to call that same BBS, and just hit enter at the login prompt, would it behave the same way? Is this only an issue when calling Mystic BBSes, or does it happen with all kinds?
It happens either way, it is a issue with mystic. I know for a fact, RA will hang-up on the 3rd time of a failed login. Same goes for, RG, inqu
My matrix has a logoff option.. But if someone wanted to be an asshole~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
to me all they have to do is sort of a "ping of death" with the enter
key.. I could write a script to just send the enter command 10000000 times when it makes a connection and my system would switch between the matrix
and login screen as fast as it can without logging off from failed
attempts. the reason being is when you log on to my system my lightbar is
on the "logon to bbs" selection.. you hit enter. then when the user logon screen comes up and you just hit enter instead of typing in a user name it kicks you back to the matrix screen.. then you hit "enter" at the
matrix... Endless "enter" loop.. Try it.. bbs.sinnershaven.com... well
just not a million times...:)
Once again, are you claiming that you have the login attempts configured and it doesn't work? I have tested several alphas now and I can't find any where this feature does not work.
It happens either way, it is a issue with mystic. I know for a
fact, RA will hang-up on the 3rd time of a failed login. Same
goes for, RG, inqu
Once again, are you claiming that you have the login attempts
configured and it doesn't work? I have tested several alphas now and
I can't find any where this feature does not work.
desides that he doesn't what to do what here started to do. He telnets out to another mystic board in the list. But he doesn't login normal. He just hits ENTER over and over causing mystic the loop the user login prompt. In a perfect world, things do work great! ..hehe.. happy new
I get what your saying, i'm sure g00r00 will do something. Otherwise
you have to option to code your matrix with mpl and make it behave in
any manner desired. I've seen it done before. :)
Is there possibly a menu command that would check for that, that some people might have left out of their matrix menu when they replaced it?
i've obviously lead a sheltered life... why is this thing called a "matrix"?? is it like a "carousel", "wheel" or "hub" used on some
systems to offer a choice of different bbses to login to? the ones i'm familiar with like that actually ran different bbs software for each one...
Once again, are you claiming that you have the login attempts configured and it doesn't work? I have tested several alphas now and I can't find any where this feature does not work.
if you set mystic to shuttle login, and just keep pressing enter without putting in a user name, it doesnt disconnet.
| Sysop: | Eric Oulashin |
|---|---|
| Location: | Beaverton, Oregon, USA |
| Users: | 100 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 02:19:09 |
| Calls: | 3,448 |
| Calls today: | 1 |
| Files: | 8,461 |
| Messages: | 336,460 |