OK i need to know how this is done so I can stop the person who is doing it to me.
Someone logs on my bbs but the name can't be seen. all i can see is a blank where the channel is in use on worldgroup 3.3 old dos screen. it is like somehow they are using ansi color to hide the name, then they telnet out to a friends bbs and use my account to hack his mudgame. I have banned over 25 ips in the last few days but he keeps comming back with more. I am damn near at a loss here..If anyone could shed some light on this i would appreciate it. He is tearing up my friends bbs bad and what looks bad is it is showing up as my ip cause he is comming thru my system to do this shit.
worldgroup hack
Re: worldgroup hack
its not showing as world-wide-web call accepted or a w on the user list is it?
-
FreeBander
- Posts: 51
- Joined: Thu Dec 26, 2002 6:00 am
Re: worldgroup hack
sometimes it is other times it is showing on the c/s side then sometimes just the double arrows that shows a full log on but when I do a =# its shows the active channel but nothing for a name.
Re: worldgroup hack
disable your modules! -- http://www.forumshq.com/showthread.php?t=4074
there is no reason to have c/s enabled or the "telnet client" (telnet out from bbs). also, in the general setup under core general setup, turn off "support c/s users"
there is no reason to have c/s enabled or the "telnet client" (telnet out from bbs). also, in the general setup under core general setup, turn off "support c/s users"
-
FreeBander
- Posts: 51
- Joined: Thu Dec 26, 2002 6:00 am
Re: worldgroup hack
Unfortunatly I use c/s to access the bbs from work and make menu changes ect while the bbs is up humm. and telnet takes you to the tradewars server from the games menu. that is the only reason I have these enabled.
-
Hunter
Re: worldgroup hack
you do not need to have telnet out enabled in order to use the menu choice command to let your users get to your door computer. I'm assuming you are running Synchronet?
I have telnet out disabled, and anyone can use the menu choice from my games menu page to get to the door server over the cad cable via telnet.
Have you tried disabling telnet out?
I have telnet out disabled, and anyone can use the menu choice from my games menu page to get to the door server over the cad cable via telnet.
Have you tried disabling telnet out?
-
FreeBander
- Posts: 51
- Joined: Thu Dec 26, 2002 6:00 am
Re: worldgroup hack
no i don't use Synchronet. The games menu telnets you out to a seperate server runing tradewars 2002gs when you select the game tradewars or tradewars remote editor depending on the access you have.
-
PuFF
Re: worldgroup hack
You dont need telnet to run the tradewars server. If u have the actual tradewars server software and not the Door program. I just downloaded the new beta of the server and there are instructions to run it on the same pc as WG. U use local loop 127.0.0.1 and rlogin, and make a menu option to tradewars as an rlogin module with 127.0.0.1 as the "command line". Have the tradewars server running, and when you hit the tradewars menu item, it will launch itself into the tradewars server. this is the link to the spot in the forums which worked for me
http://www.tradewars.com/twforum/topic.asp?TOPIC_ID=2949&SearchTerms=worldgroup
and following is the instructions that i just cut/pasted here
Note: this is for TradeWars server, and NOT the tradewars door. I have a menu item with the rlogin module that connects to the TWserver which resides on the same pc as WG..also using wg3.3, THIS WAY, you dont need your telnet module running for Tradewars :)
**********************************************************************
Running from a Worldgroup BBS
By calling TWGS from Worldgroup with the RLogin connection protocol, you can limit your game server users to a single login per Worldgroup account. If you maintain control over player accounts on your BBS, you will have no problems with duping on the server.
Step 1: Configure TWGS for Worldgroup connections.
1) Disable the server and enter the Configuration area.
2) Select the Server tab
3) Select port 513 (required for Worldgroup RLogin connections)
Set the port protocol to RLogin to allow passing of BBS user name from the BBS to TWGS. This must be set for the Worldgroup connection to work. Since only port 513 connections are allowed, you cannot use RLogin for both the game and the admin connections. Set the admin port to telnet.
The "User RLogin name" setting may need to be changed from the default "Passed 2nd" setting. This setting determines which RLogin login string TWGS treats as the user login name. If TWGS isn't reading the correct login name, you should switch to "Passed 1st".
Step 3: Specify a limited IP connection list
Under the IP Lists tab of the Configuration area, you should add the IP address of your BBS machine to the Game Connection and Admin Connection IP lists. This will limit TWGS connections to only those originating from the machine that is running your BBS.
If you are running TWGS from the same machine as the BBS, you should use the local loopback address for the IP (127.0.0.1). If you are running TWGS from a separate machine from the BBS, put the IP address of the BBS machine into these lists.
WARNING: If you do not specify an IP address in the Admin Connection list, others can remote connect to your administration port. This will provide them access to TEDIT on all of your games. You should specify TEDIT passwords, but it is still most safe to allow connections only from a specific list of IPs.
Step 4: Create a Worldgroup TWGS menu option.
1) Enter the menu tree editor
2) Add a page for the TWGS
3) Set the page to "Module page" and select your TCP/IP (RLogin) module
Type in the command-line to connect to TWGS. This will vary depending on the TCP/IP module you are using. I will provide two examples, one for VircomTCP/IP and one for the standard WG3 RLogin Module.
I will build the command for a sample loopback (local) connection.
VircomTCP/IP:
Specify RLogin connection protocol
Command: "L ..."
1) Specify the IP address of the Game Server.
If you have TWGS set to run on the same machine as your BBS, this should be the local loopback IP address, 127.0.0.1. This is most efficient because TCP/IP skips many unnecessary levels of processing when the data is passed to the same machine. You must set this local loopback address as the TWGS IP address in the TWGS Configuration area, Server tab, or click the Local check box.
If you have TWGS set to run from a different machine, this should be the IP addressed associated with that machine. The machine can be connected via a LAN or the Internet. The simplest way to configure TWGS in this case is to use auto IP address detection. TWGS will determine the IP address of the machine whenever is it started.
Command: "L 127.0.0.1 ..."
Specify the RLogin connection strings.
RLogin passes two user login strings and a terminal type. WG allows you to pass user names using the %u macro. To pass two user names and a terminal type, enter a line like this:
Command: "L 127.0.0.1 %u %u ansi"
WG3 RLogin Module:
Specify the IP address of the Game Server.
If you have TWGS set to run on the same machine as your BBS, this should be the local loopback IP address, 127.0.0.1. This is most efficient because TCP/IP skips many unnecessary levels of processing when the data is passed to the same machine. You must set this local loopback address as the TWGS IP address in the TWGS Configuration area, Server tab, or click the Local check box.
If you have TWGS set to run from a different machine, this should be the IP addressed associated with that machine. The machine can be connected via a LAN or the Internet. The simplest way to configure TWGS in this case is to use auto IP address detection. TWGS will determine the IP address of the machine whenever is it started.
Command: "127.0.0.1"
Save your menu settings.
Step 6: Test the connection
Start TWGS and enable the server
Connect to your BBS and go to the TWGS connection menu item. Select the item to start a TWGS session. You should be immediately presented with the TWGS intro menu. Use the # key to see who is online. The name specified in this list should be your BBS name. You cannot alter this name from TWGS, and it is used for all TW game sessions. This guarantees that only one Trade Wars game account can exist in any game for each BBS user name
******************************************************
Goodluck , but i didnt have ANY problems doing it this way..they have a thier new beta version of the server available as a 30day demo.
Unfortunatly I use c/s to access the bbs from work and make menu changes ect while the bbs is up humm. and telnet takes you to the tradewars server from the games menu. that is the only reason I have these enabled.
http://www.tradewars.com/twforum/topic.asp?TOPIC_ID=2949&SearchTerms=worldgroup
and following is the instructions that i just cut/pasted here
Note: this is for TradeWars server, and NOT the tradewars door. I have a menu item with the rlogin module that connects to the TWserver which resides on the same pc as WG..also using wg3.3, THIS WAY, you dont need your telnet module running for Tradewars :)
**********************************************************************
Running from a Worldgroup BBS
By calling TWGS from Worldgroup with the RLogin connection protocol, you can limit your game server users to a single login per Worldgroup account. If you maintain control over player accounts on your BBS, you will have no problems with duping on the server.
Step 1: Configure TWGS for Worldgroup connections.
1) Disable the server and enter the Configuration area.
2) Select the Server tab
3) Select port 513 (required for Worldgroup RLogin connections)
Set the port protocol to RLogin to allow passing of BBS user name from the BBS to TWGS. This must be set for the Worldgroup connection to work. Since only port 513 connections are allowed, you cannot use RLogin for both the game and the admin connections. Set the admin port to telnet.
The "User RLogin name" setting may need to be changed from the default "Passed 2nd" setting. This setting determines which RLogin login string TWGS treats as the user login name. If TWGS isn't reading the correct login name, you should switch to "Passed 1st".
Step 3: Specify a limited IP connection list
Under the IP Lists tab of the Configuration area, you should add the IP address of your BBS machine to the Game Connection and Admin Connection IP lists. This will limit TWGS connections to only those originating from the machine that is running your BBS.
If you are running TWGS from the same machine as the BBS, you should use the local loopback address for the IP (127.0.0.1). If you are running TWGS from a separate machine from the BBS, put the IP address of the BBS machine into these lists.
WARNING: If you do not specify an IP address in the Admin Connection list, others can remote connect to your administration port. This will provide them access to TEDIT on all of your games. You should specify TEDIT passwords, but it is still most safe to allow connections only from a specific list of IPs.
Step 4: Create a Worldgroup TWGS menu option.
1) Enter the menu tree editor
2) Add a page for the TWGS
3) Set the page to "Module page" and select your TCP/IP (RLogin) module
Type in the command-line to connect to TWGS. This will vary depending on the TCP/IP module you are using. I will provide two examples, one for VircomTCP/IP and one for the standard WG3 RLogin Module.
I will build the command for a sample loopback (local) connection.
VircomTCP/IP:
Specify RLogin connection protocol
Command: "L ..."
1) Specify the IP address of the Game Server.
If you have TWGS set to run on the same machine as your BBS, this should be the local loopback IP address, 127.0.0.1. This is most efficient because TCP/IP skips many unnecessary levels of processing when the data is passed to the same machine. You must set this local loopback address as the TWGS IP address in the TWGS Configuration area, Server tab, or click the Local check box.
If you have TWGS set to run from a different machine, this should be the IP addressed associated with that machine. The machine can be connected via a LAN or the Internet. The simplest way to configure TWGS in this case is to use auto IP address detection. TWGS will determine the IP address of the machine whenever is it started.
Command: "L 127.0.0.1 ..."
Specify the RLogin connection strings.
RLogin passes two user login strings and a terminal type. WG allows you to pass user names using the %u macro. To pass two user names and a terminal type, enter a line like this:
Command: "L 127.0.0.1 %u %u ansi"
WG3 RLogin Module:
Specify the IP address of the Game Server.
If you have TWGS set to run on the same machine as your BBS, this should be the local loopback IP address, 127.0.0.1. This is most efficient because TCP/IP skips many unnecessary levels of processing when the data is passed to the same machine. You must set this local loopback address as the TWGS IP address in the TWGS Configuration area, Server tab, or click the Local check box.
If you have TWGS set to run from a different machine, this should be the IP addressed associated with that machine. The machine can be connected via a LAN or the Internet. The simplest way to configure TWGS in this case is to use auto IP address detection. TWGS will determine the IP address of the machine whenever is it started.
Command: "127.0.0.1"
Save your menu settings.
Step 6: Test the connection
Start TWGS and enable the server
Connect to your BBS and go to the TWGS connection menu item. Select the item to start a TWGS session. You should be immediately presented with the TWGS intro menu. Use the # key to see who is online. The name specified in this list should be your BBS name. You cannot alter this name from TWGS, and it is used for all TW game sessions. This guarantees that only one Trade Wars game account can exist in any game for each BBS user name
******************************************************
Goodluck , but i didnt have ANY problems doing it this way..they have a thier new beta version of the server available as a 30day demo.
Unfortunatly I use c/s to access the bbs from work and make menu changes ect while the bbs is up humm. and telnet takes you to the tradewars server from the games menu. that is the only reason I have these enabled.
Re: worldgroup hack
Goodluck , but i didnt have ANY problems doing it this way..they have a thier new beta version of the server available as a 30day demo.
That's rather odd, since WorldGroup 3.xx doesn't allow you to rlogin to localhost or any loopback IP!
Are you running WG + Vircom TCP/IP, or do you have a magical system that isn't affected by the annoying WG 3 rlogin bug that has affected 100+ other sysops? :huh:
btw, you don't specifically need TW Game Server to offer rlogin tradewars. You can set up Synchronet to run via rlogin, and have the WG bbs rlogin to that, and run the door version of TradeWars. You can edit Synchronet so that it only offers a game menu upon login. Hell, you can edit Synchronet specifically so taht it only loads TradeWars upon login if you want...
It's a longer setup process than just using TWGS, but it costs a bit less $. Depends which is a bigger factor for you.
*If you can afford TWGS*, and if you don't want to run any other doors, I'd definitely say use TWGS. But otherwise I'd say go the Synchronet route.
That's rather odd, since WorldGroup 3.xx doesn't allow you to rlogin to localhost or any loopback IP!
Are you running WG + Vircom TCP/IP, or do you have a magical system that isn't affected by the annoying WG 3 rlogin bug that has affected 100+ other sysops? :huh:
btw, you don't specifically need TW Game Server to offer rlogin tradewars. You can set up Synchronet to run via rlogin, and have the WG bbs rlogin to that, and run the door version of TradeWars. You can edit Synchronet so that it only offers a game menu upon login. Hell, you can edit Synchronet specifically so taht it only loads TradeWars upon login if you want...
It's a longer setup process than just using TWGS, but it costs a bit less $. Depends which is a bigger factor for you.
*If you can afford TWGS*, and if you don't want to run any other doors, I'd definitely say use TWGS. But otherwise I'd say go the Synchronet route.