Secured TELNET
Home > IT Answers > Microsoft Windows > Secured TELNET
Abigail
215 pts.
0
Q:
Secured TELNET
Secured TELNET, Telnet, V5R4M0, V5R3MO, iSeries Telnet
How can I secure telnet so one cannot just telnet to our systm name and access a QPADEV* session? TIA

Software/Hardware used:
iSeries O/S V5R4M0
ASKED: Oct 12 2009  1:22 PM GMT
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
RELATED QUESTIONS
0
Teandy
3250 pts.
0
A:
 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0
  • AddThis Social Bookmark Button
The first thing I would do would be to set Public authority to *EXCLUDE. You can also look into exit programs. You can write you own or look into a commercial application.

This thread may help:

http://archive.midrange.com/midrange-l/200811/msg00380.html

Also you can check :

http://publib.boulder.ibm.com/html/as400/v5r1/ic2989/index.htm?info/rzaiw/rzaiwprogramtypes.htm

http://www.google.com/search?hl=en&source=hp&q=QIBM_QTG_DEVINIT+&btnG=Google+Search&aq=f&oq=&aqi=

---------------------------------------------------------------------------------------------------------------------------------------------



We control access from our interactive subsystems. In QINTER, for example, we add workstation names that DO NOT begin with QPADEV*. So, if someone is not assigned a workstation name, they will not obtain a signon for our system.
Last Answered: Oct 14 2009  6:43 PM GMT by Teandy   3250 pts.
Latest Contributors: Batman47   525 pts.
  •   
0
0
RSS - Discussions Help
Discuss This Answer:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _



_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Abigail   215 pts.  |   Oct 12 2009  6:13PM GMT

What would you set to Public *EXCLUDE?

 

TomLiotta   7990 pts.  |   Oct 12 2009  10:30PM GMT

Do you want to stop unauthorized telnet access from outside or do you simply want to block access to QPADEV* devices? The two are not totally synonymous. Unauthorized outside access can connect to devices other than QPADEV* devices.

Tom

 

Whatis23   4040 pts.  |   Oct 13 2009  8:51AM GMT

Total lock out to the command TELNET for login is to set to public *exclude.

 

WoodEngineer   2280 pts.  |   Oct 13 2009  3:42PM GMT

We have had good success using the TELNET exit program provided by IBM, which can be found from the URL metnnioned by Teandy. It installed smoothly and is very secure.

 

Pdraebel   885 pts.  |   Oct 14 2009  9:02AM GMT

If you now which IP adresses (ranges) are allowed access you cold use CFGTPC option 2 (Routes) and remove the *DFTROUTE and add only the IP ranges you want to allow access toyour iSeries.
Doing that will cause you i not to reply to any requessts from IP’s outside allowed ranges.

 

Teandy   3250 pts.  |   Oct 14 2009  6:41PM GMT

Abigail wrote:
What would you set to Public *EXCLUDE?

On the command line, type WRKOBJ TELNET.

On the next screen, take option 2. Then change *PUBLIC authority to *EXCLUDE.

                            Edit Object Authority                              

Object . . . . . . . :   TELNET          Owner  . . . . . . . :   QSYS
  Library  . . . . . :     QSYS          Primary group  . . . :   *NONE
Object type  . . . . :   *CMD            ASP device . . . . . :   *SYSBAS      

Type changes to current authorities, press Enter.                              

  Object secured by authorization list  . . . . . . . . . . . .   *NONE        

                         Object
User        Group       Authority
*PUBLIC                 *EXCLUDE

You can also use EDTOBJAUT OBJ(TELNET) OBJTYPE(*CMD). Both commands eventually take you to the same screen.

 
0