Lets say I use pycrypto with AES, like this.
obj = AES.new('mykey', AES.MODE_CFB)
mytext = "Big secret"
cipher = obj.encrypt(mytext)
Can I use the same key or I have to change it everytime?
Would this be sufficiently secure?
Francis
On 23 jan, 11:25, Francis <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Emanuele, your said : As for safety, nothing is safer than OTP, but
> are we sure that your customer
> is able to go to great lengths to distribute long key streams over a
> perfectly safe channel to the sales representatives?
>
> Isn't the encrypted string secure?
>
> The method to send the s
Hi,
Thank you for all the information, it seems like you think it easy to
do, as everyone accept to help me for free :-)
The solution used before was to send to encrypted string in clear in a
email. It used a perl impletation of the one-time pad.
Emanuele, your said : As for safety, nothing is
Dear Francis,
> Only one person (or very limited group) will receive the encrypted
> message by email. It will hold customer information need by the sale
> rep. So no user will have to deal with the encrypted data.
>
> Server receive customer info -> encrypt critical info -> sent email to
> sales
> i'll be honest, i don't know anyone who's ever used a one-time-pad
ooh...terminology clarification:
OTP = one-time password
OTP = one-time pad
The former is a common tool used for safely logging in over an
insecure channel (such as using S/Key when logging into my
OpenBSD box over telnet).
i'll be honest, i don't know anyone who's ever used a one-time-pad
outside of some military applications before we had computers
everywhere. while the security is mathematically "perfect", it's so
encumbering to implement that i consider it overall riskier. having to
pass by courier gigs upo
Only one person (or very limited group) will receive the encrypted
message by email. It will hold customer information need by the sale
rep. So no user will have to deal with the encrypted data.
Server receive customer info -> encrypt critical info -> sent email to
sales rep.
sales rep. decrypt t
>>> - 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,
Tim Chase wrote:
>> What's need to be done :
>> - 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.
al
> I'm building a web application for one of my clients with django. But
> I need to do something that I have never did before and I am somehow
> really short on time to learn it.
>
> So I am looking for someone who has experience with encryption/
> security in python. It is to be incorporated int
Hi,
I'm building a web application for one of my clients with django. But
I need to do something that I have never did before and I am somehow
really short on time to learn it.
So I am looking for someone who has experience with encryption/
security in python. It is to be incorporated into my dj
11 matches
Mail list logo
