Brett McCoy wrote: > On Thu, Apr 24, 2008 at 1:53 PM, saqib irshad <[EMAIL PROTECTED]> wrote: > >> The application is like Trading applications used in stock exchange. >> Performence and security both are important. So kindly tell me about the >> encryption algorithm. > > Still pretty vague. It doesn't tell me what you are doing with the > data. Transmitting across a network? Storing data on tapes or > removable media to be transported somewhere off site? > > There are many kinds of data encryption algorithms, way more than what > we can tell you here on a mailing list. Writing your own code to > implement an algorithm may not be very secure, you should go with an > encryption library that you can just link against with your code. > > Openssl, as Thomas pointer out, is a good start for using in your > program for providing secure encryption. My company uses it to create > digital signatures for application licenses. The application won't run > unless the signature is present. SSL is ubiquitous in web page > encryption -- if you see a url that is https:// it is using SSL > (secure sockets layer). It should be noted that SSL itself is not an > algorithm, but is an application layer that uses various algorithms to > encrypt and decrypt data (much in the same way that audio and video > software use codecs to handle different kinds of media). > > I suggest you do some research. I'd start with http://www.openssl.org > and http://www.openssh.org. > > -- Brett > ------------------------------------------------------------ > "In the rhythm of music a secret is hidden; > If I were to divulge it, it would overturn the world." > -- Jelaleddin Rumi
And to clarify, the SSL components of OpenSSL are actually only a _small_ portion of OpenSSL. Every major PKI and hashing algorithm in use today is in OpenSSL. If you can't find it there, it probably isn't a good algorithm to begin with. -- Thomas Hruska CubicleSoft President Ph: 517-803-4197 *NEW* MyTaskFocus 1.1 Get on task. Stay on task. http://www.CubicleSoft.com/MyTaskFocus/
