Re: Locking an ip interface to user profiles -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

I would think an Exit Program should do the trick. I don't do them, but I've
seen lots of places use them. In fact I know that is how a number of the
TCP/IP security products do there jobs.

On Wed, Aug 19, 2009 at 1:15 PM, Lance Gillespie <lgillespie@xxxxxxxx>wrote:

Is it possible to secure a tcp/ip interface so that it can only be used
by enumerated user profiles?

That is, I use Add TCP/IP Interface (ADDTCPIFC) to add a new IP address
to the iSeries and then do something so that only certain profiles can
use the new interface?

I have the ports locked down, but would like to add profile security.

I suspect the answer is no since I could not find anything about it and
it looks like security is further up the ISO stack, but I thought I would
ask.

Thanks,
Lance

--
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.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.