Look seriously at both Ray's SQL solution and Mark's
Data-At-Rest-Encryption. The latter is a UV 10.2 enhancement.
-Original Message-
From: Ray Wurlod
Sent: Thursday, November 29, 2007 1:59 PM
If you were to convert the file into an SQL table, then you can grant
SELECT privilege (or not)
If you were to convert the file into an SQL table, then you can grant SELECT
privilege (or not) at the individual column level. And/or you can restrict the
table entirely to a single SQL user (at least in UniVerse) and only access it
via programs compiled with the AUTHORIZATION statement.
My $
Augusto,
Can you change your application to use OPENPATH rather than OPEN. This does not
require a VOC entry just a path.
Cheers,
Andy
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Augusto Alonso
Sent: 28 November 2007 18:46
To: u2-users@listserver.u2ug
-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Craig Bennett
Sent: Wednesday, November 28, 2007 5:07 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Need to partially hide a file
Augusto,
when you say hidden, how hidden do you mean?
>>> We need to hide some pri
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
erse (neither under
> windows nor under linux)
> I was thinking in a pointer-like sollution, so that the code remains
> unchanged.
>
> - Original Message -
> From: "Baker Hughes" <[EMAIL PROTECTED]>
> To:
> Sent: Wednesday, November 28, 2007 11:47 PM
a pointer-like sollution, so that the code remains
unchanged.
- Original Message -
From: "Baker Hughes" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, November 28, 2007 11:47 PM
Subject: RE: [U2] Need to partially hide a file
Augusto,
sort of along the same line of thinking a
Augusto,
sort of along the same line of thinking as Dave ... play with the user's
logon as soon as they login...
Modify your LOGIN VOC item so that it:
a) Checks a Data Security flag for that specific user [ @logname = Item
ID in DSA.Flags file]
b) Open the Cust.Secure.Data file to a named common
One approach would be to set up separate accounts for privileged vs.
non-privileged users. That would give you two VOC files, and the paths
to the data could be different for some or all of the files.
Another approach is the following:
In UniData this could be done by using environment variables
Can someone tell me if it is possible?
I'll explain the scenario:
We need to hide some private data (customer personal data) in order to
fit with our Private Data Protection Law.
But only for some users, the others, they need to have full access.
Our app is complex enough to modify the source co
10 matches
Mail list logo