RE: Diabling Telnet Attention key

["Shannon ODonnell" <sodonnell@xxxxxxxxxxxxxxxxx>]

Yeah,   you know...I tested the very same thing after I posted my reply
this morning and it worked that way for me too. 

The strange thing that I'm seeing, and it's entirely possible that I'm
totally misunderstanding what I'm seeing or what's going on...(wouldn't
be the first and certainly won't be the last time I make a
mistake...)...but

For what I'm doing... In a CL program I swap the original user profile
to a new profile (a public user that has special authorities for the
application) using a couple of security apis.  It is this new profile
that I telnet to the remote system. 

Now...once on the remote system,  that user can press the atn key and
see the atn key menu and command line. 

What happens then is that the user is able to enter commands on the
command line such as "CALL" or "WRKACTJOB".
This despite the fact that for both the original user profile and the
public user profile, the LMTCPB paramater is set to (*YES) and the
ATNPGM parm is set to *NONE. 

What I am wondering... Since I log onto the very first AS/400 via Client
Access with my "normal" user profile, which has *SECADM authorities in
it, and then sign on to a 5250 session using the "limited" profile
before telnetting....I'm wondering if the Telnet Send Control Functions
menu is picking up the authorities from my original user profile that
started the first Client Access session?  

In any event, on Monday, I'll be at a dumb terminal and I'll sign on
directly from there using only the limited profile and see what happens.

Thanks all for your responses and creative (Scott) answers!



Shannon O'Donnell





-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Ingvaldson, Scott
Sent: Friday, February 13, 2004 10:38 AM
To: 'midrange-l@xxxxxxxxxxxx'
Subject: RE: Diabling Telnet Attention key


Shannon -

I tested this today with LMTCPB(*YES)(on the client side) and tho' I
could see the command line, I could not issue a command.  I then tried
this using a profile with LMTCPB(*YES) and *ALLOBJ and still could not
issue a command. Does it matter that the user can see the command line
if they cannot use it?

Regards,

Scott Ingvaldson
AS/400 System Administrator
GuideOne Insurance Group

-----Original Message-----
date: Fri, 13 Feb 2004 09:37:12 -0600
from: "Shannon ODonnell" <sodonnell@xxxxxxxxxxxxxxxxx>
subject: RE: Diabling Telnet Attention key

Well, that would be nice and easy, but,  LMTCPB has zero effect on
whether or not the user sees the TELNET Send Functions menu and command
line.  That menu and command line operates outside of the LMTCPB(*YES)
and ATNPGM(*NO) paramaters on the User Profile.

Shannon O'Donnell


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of McCallion, Martin
Sent: Friday, February 13, 2004 4:19 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Diabling Telnet Attention key


Shannon wrote:

> What I'm doing is issuing the Telnet command from within a CL program

<snip>

> The problem is that when the user presses the Attention Key on the
> telnet session (one as/400 to another as/400 remember...) they see 
> that Attention Control menu, which, among other things, gives them
> a command
> line on their home system.

If they're that tightly restricted anyway, why not just make them
limited-capabilities users (LMTCPB(*YES))?  That way they won't be able
to do anything on the command line.

Cheers,

Martin.

-- 
Martin McCallion
Senior Technical Consultant
Misys Wholesale Banking Systems
1 St George's Road, London, SW19 4DR, UK
T +44 (0)20 8486 1951
F +44 (0) 20 8947 3373
martin.mccallion@xxxxxxxxx
www.misys.com

   
This message and accompanying documents are covered by the Electronic
Communications Privacy Act, 18 U.S.C. §§ 2510-2521, and contains
information intended for the specified individual(s) only. This
information is confidential. If you are not the intended recipient or an
agent responsible for delivering it to the intended recipient, you are
hereby notified that you have received this document in error and that
any review, dissemination, copying, or the taking of any action based on
the contents of this information is strictly prohibited. If you have
received this communication in error, please notify us immediately by
e-mail, and delete the original message.

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.