Comments on: Closing Open Access to IFS http://itknowledgeexchange.techtarget.com/itanswers/closing-open-access-to-ifs/ Sat, 18 May 2013 07:52:31 +0000 hourly 1 By: tomliotta http://itknowledgeexchange.techtarget.com/itanswers/closing-open-access-to-ifs/#comment-103018 tomliotta Fri, 17 Feb 2012 01:21:21 +0000 #comment-103018 If you do nothing log accesses…

Should be “If you do nothing but log accesses…”.

Tom

]]> By: tomliotta http://itknowledgeexchange.techtarget.com/itanswers/closing-open-access-to-ifs/#comment-103017 tomliotta Fri, 17 Feb 2012 01:17:38 +0000 #comment-103017 As for knowing who accesses files, you can create an exit program over the file server QIBM_QPWFS_FILE_SERV exit point. Your exit program can create a log of accesses, if that’s what you need.

It can also return a ‘Accept’ or ‘Reject’ indication back to the file server. How you analyze the request and make the decision is up to your programming. If you do nothing log accesses, you might consider ‘Accept’ for all accesses, or perhaps ‘Reject’ for accesses from outside your system’s local subnet, or any number of variations.

Tom

]]> By: tomliotta http://itknowledgeexchange.techtarget.com/itanswers/closing-open-access-to-ifs/#comment-103016 tomliotta Fri, 17 Feb 2012 01:09:58 +0000 #comment-103016 In iSeries Navigator, expand your connection down through Network-> Servers-> TCP/IP, and right-click the NetServer server to access Properties.

On the Security tab, see if a ‘Guest user ID:’ is assigned. If one is, remove it. A ‘guest’ profile is a profile that you create (or assign) on your iSeries, to be used whenever someone requests a connection but has no profile of their own.

(And surely you don’t have a share out over the /root file system nor over /QSYS.LIB itself, right?)

Tom

]]>