The best options are probably:
Security subroutines and named common switches (this was covered at U2U under
Data Security and Best Practises
Use wIntegrate thin client (more flexible and secure for this than the thick
client) and log from the wIntegrate server using wIntegrate scripting.
On 24/04/13 22:54, Tom Whitmore wrote:
Hi,
Can you provide more information on what you are trying to capture? (edits,
list commands, etc.) I suspect that you may be able to put security on the
commands you are concerned with and address the problem with less pain.
The problem with using
-0400
From: Tom Whitmore tewhitm...@ratex.com
To: U2 Users List u2-users@listserver.u2ug.org
Subject: Re: [U2] TCL input and response logging such as COMO
Message-ID: BA2E471C9317804EB8470750F458BD9801EC7D8D3D38@public
Content-Type: text/plain; charset=us-ascii
Hi,
Can you provide more
Hi maybe!
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Susan Joslyn
Sent: Thursday, April 25, 2013 12:17 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] TCL input and response logging such as COMO
Hi.
I'm
)
Message: 6
Date: Wed, 24 Apr 2013 17:54:36 -0400
From: Tom Whitmore tewhitm...@ratex.com
To: U2 Users List u2-users@listserver.u2ug.org
Subject: Re: [U2] TCL input and response logging such as COMO
Message-ID: BA2E471C9317804EB8470750F458BD9801EC7D8D3D38@public
Content-Type: text/plain
:06 a.m.
To: U2 Users List
Subject: Re: [U2] TCL input and response logging such as COMO
I can't speak for UV, but we've been required to log all sessions for specific
powerful users. It becomes a little simpler if you do it for all users. Make
sure you have some type of automated purge of whatever
I guess it depends on what legislation you must comply with for auditing
purposes and what you can get away with. If you have to log everything then I'd
agree that the unix tee command as others suggest would be best. The following
works OK on our AIX dev box but there are a few strange
input and response logging such as COMO
On 24/04/13 22:54, Tom Whitmore wrote:
Hi,
Can you provide more information on what you are trying to capture? (edits,
list commands, etc.) I suspect that you may be able to put security on the
commands you are concerned with and address the problem
In UniVerse in the SAVEDLIST directory a user's TCL statements are saved as
$$userid:user#
Dan Goble | Senior Systems Engineer
Interline Brands, Inc.
804 East Gate Drive Suite 100, Mount Laurel, NJ 08054
Office: 856.533.3110 | Mobile: 609.792.6855
E-mail: dan.go...@interlinebrands.com |
Capturing TCL entries and responses is not related to PCI compliance, which
is only related to payment card uses.
-Original Message-
From: Scott Zachary szach...@gardensalive.com
To: u2-users u2-users@listserver.u2ug.org
Sent: Wed, Apr 24, 2013 1:45 pm
Subject: [U2] TCL input
This is an automated response.
Allen Bell will be out of town and unavailable until Monday, April 29th,
2013.
On 4/24/2013 3:34 PM, Scott Zachary wrote:
For PCI compliance, we are tasked to log/capture all TCL entries and
responses. I am familiar with COMO, which is one possible solution.
I can't speak for UV, but we've been required to log all sessions for
specific powerful users. It becomes a little simpler if you do it for all
users. Make sure you have some type of automated purge of whatever log
files you create or you'll probably start filling up your file system.
This is
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of
bradley.sch...@usbank.com
Sent: Wednesday, April 24, 2013 5:06 PM
To: U2 Users List
Subject: Re: [U2] TCL input and response logging such as COMO
I can't speak for UV
Scott,
One thing that I've seen in use on unix systems is the script command. You
would put it in the user's .profile, or whatever startup script is executing
UV/UD. The syntax of the command would be script -c uv/ud command
logfile. Replace uv/ud command with the command that you use to
, April 24, 2013 2:55 PM
To: U2 Users List
Subject: Re: [U2] TCL input and response logging such as COMO
Hi,
Can you provide more information on what you are trying to capture?
(edits, list commands, etc.) I suspect that you may be able to put
security on the commands you are concerned
15 matches
Mail list logo
