Re: Encrypt data before inserting into DB
Posted in 1998
Topics: Stored Procedures & SPL, Security, Permissions & Auditing, Java & JDBC Development
If after following Cowboy's suggestions you still need to encrypt the data, you can go to http://www.webf1.com/tips and do a search on 'crypt' (no quotes) for a routine which you can use to encrypt your data. -- Visit our Tutorials: http://www.webf1.com/tutorials Create your own FREE private chat room at http://www.webf1.com/chat/ Oscar J. Meszar (ojm@ojmnet.com) Start/Stop NT Services (http://www.webf1.com/startstop Cowboy wrote in message <35c009a6.198998414@news>... >On Thu, 30 Jul 1998 08:46:32 +0800, norli <norli@asiapac.net> wrote: > >>Hi all, >> >>I'm working on an intranet Payroll System. Since salary information are >>confidential, I'd like to have it encrypted before inserting it into the >>database, and decrypted before displaying on the screen. I'm developing >>my apps using Informix 7.22 & SQL Server 6.5 db, using html, javascript >>& vbscript. Is there a way around it? >> >>Thanks in advance! >> >>- norli - >> > >The easiest way around this would be to restrict database access to >that particular table to a certain group. Authenticate the user to >ensure he is a member of that group before displaying it. To further >tighten security, you can use stored procedures and views and lock >down the actual database. The only people that will then be able to >see the salary data are those who are entitled and SQL dbo/sa >accounts. If you still feel the need to encrypt and decrypt the same >group will still be able to adjust security to give themselves >permission to view the data; to do this, you will need a component >that encrypts or find a way to code the encryption yourself (I would >favor finding a component unless you are comfortable with crypto). > >GB > >When you leave this place, you can only take your >name. That's why I am making this world a better >place, one promise at a time. > >Cowboy, >MCSE > >***************************************************** >To reply, remove the No Spam portion from both ends. >***************************************************** >