[rt-users] encrypting fields and email

[david.falkenburger at rbc.com]

I was thinking more along the lines of public and private key technology. If
I was to use the private key to encrypt all the data in one or more fields,
a key that I as developer generate, then having access to the database or
the server will not do you any good unless you have the corresponding
private key to decrypt. I could distribute the private key to authorized
individuals only. So now you would not only have to be authorized to access
RT, and the appropriate queue, but would also need the public key available
to your browser for decryption.

Something along the lines of what Lotus Notes is able to do. Not sure if
their Domino technology can do it as well.

Dave

-----Original Message-----
From: Vivek Khera [mailto:vivek at khera.org]
Sent: Thursday, September 30, 2004 10:37 AM
To: RT Mailing List
Subject: Re: [rt-users] encrypting fields and email


_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Be sure to check out the RT wiki at http://wiki.bestpractical.com

------------------------------------------------------------

This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. If you received this e-mail in error, please advise me (by return e-mail or otherwise) immediately. 

Ce courrier électronique est confidentiel et protégé. L'expéditeur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez ce courrier électronique par erreur, veuillez m'en aviser immédiatement, par retour de courrier électronique ou par un autre moyen.

============================================================ 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20040930/ceee62ae/attachment.htm>