>>> - Take a message, encrypt it using a secure method (should be better >>> or equal than OTP), return the encrypted message. > > >> parties, Blowfish and DES3 are popular choices and likely to be > > just a point of fact: neither of these are >= to OTP.
They're all strong cryptographically, but all shared-secret solutions suffer the same fate of having to figure out how to securely share your key/OTP if you aren't both the sender and the recipient. I do like OTP for logins over insecure connections if absolutely needed, but otherwise, I don't see non-public-key as a great win :) > also, on a side note, i wouldn't use 3DES for any new implementations. [snip] > i'd highly recommend AES instead. Good point...I remember hearing something about that a while back, but I tend to use public-key for just about everything so it didn't register in my active memory. -tim --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
