As has been commented, if you're on dbf's they are inherently insecure
(how sensitive is the data? if *very* then migrate to a dbms), but a
clear-text userId hashed and used as an index against a file of hashed
Id's seems pretty good to me.
I have done something similar (though for more users a
On 3/7/2016 9:43 AM, Stephen Russell wrote:
When they open the employee table and can read a SSN is when it gets shaky.
Or open the customer table and make a copy for themselves as they walk off
to a new job.
Or use their smart phone to take a picture of the screen full of
sensitive personal
Your comment: Yes, that is one area of concern. Is my way best, etc.
But my other concern is how the program receives that data of ID and
Access Level, and how is that data packaged. Is that process a security
risk. My usage is simple and often simple is easy to bypass.
Example: I have 10 s
On 07/03/2016 17:16, John R. Sowden wrote:
Let me address a few issues:
1) My question was regarding making the software association between
the user data in the user database, along with his/her authority
level and id, and the executing program.
Are you talking about a better way to limit/c
Let me address a few issues:
1) My question was regarding making the software association between the
user data in the user database, along with his/her authority level and
id, and the executing program.
2) The security issue of my .dbf files is another issue. First, I link
some data to ot
Want secure ? Don't connect to the net.
On Mon, Mar 7, 2016 at 3:43 PM, Stephen Russell
wrote:
> When they open the employee table and can read a SSN is when it gets shaky.
>
> Or open the customer table and make a copy for themselves as they walk off
> to a new job.
>
>
>
> On Mon, Mar 7, 2016
When they open the employee table and can read a SSN is when it gets shaky.
Or open the customer table and make a copy for themselves as they walk off
to a new job.
On Mon, Mar 7, 2016 at 7:48 AM, Ted Roche wrote:
> Well, nothing is secure, given North Korea has nuclear weapons. But
> that's
Well, nothing is secure, given North Korea has nuclear weapons. But
that's not the question, really.
"Secure against what?"
If the curious can read your DBFs in Excel, they may gain information
that you have a column named FooBar that holds integer values. If the
significance of FooBar isn't obvi
IMO if your data is in DBF files, it's not secure.
--
Alan Bourke
alanpbourke (at) fastmail (dot) fm
___
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http:/
>
> I encrypt entered passwords, compare them to encrypted stored passwords,
> ala linux. I am comfortable with that.
I hope you mean hashed... Encrypting passwords is not a lot more secure
than storing passwords unencrypted, especially considering the lack of
libraries with modern encryption ro
applications that I use need to be secure and have an audit trail. I
encrypt entered passwords, compare them to encrypted stored passwords,
ala linux. I am comfortable with that. My concern is relating the
authorized user, with their access level to the actual programs.
Currently I use the:
11 matches
Mail list logo
