15 messages in com.googlegroups.django-usersRe: ordinal not in range(128) + ezPyC...
FromSent OnAttachments
elementalMay 13, 2007 4:14 am 
Malcolm TredinnickMay 13, 2007 4:32 am 
elementalMay 13, 2007 5:07 am 
Benjamin SlavinMay 13, 2007 10:55 am 
elementalMay 14, 2007 12:17 am 
elementalMay 14, 2007 1:59 am 
Malcolm TredinnickMay 14, 2007 2:10 am 
elementalMay 14, 2007 2:40 am 
elementalMay 14, 2007 5:01 am 
Benjamin SlavinMay 14, 2007 6:27 am 
Forest BondMay 14, 2007 7:02 am 
Benjamin SlavinMay 14, 2007 7:21 am 
Forest BondMay 14, 2007 8:06 am 
elementalMay 14, 2007 6:33 pm 
Forest BondMay 14, 2007 6:54 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: ordinal not in range(128) + ezPyCryptoActions...
From:Benjamin Slavin (benj@gmail.com)
Date:May 14, 2007 7:21:05 am
List:com.googlegroups.django-users

On 5/14/07, Forest Bond <for@alittletooquiet.net> wrote:

You mean:

decrypted_passport = k.decString(base64.b64decode(self.passport)) self.passport = decrypted_passport

Right?

Yeah... that's the one ;-) Thanks for catching that, Forest.

elemental: Looking at this again, I'm still concerned by the fact that it's being put back into self.passport. If you call save() after decrypting, it will be stored in the database unencrypted.

I'd recommend doing: def get_passport(self) .... return k.decString(base64.b64decode(self.passport))

That way the value of self.passport is always encrypted and you won't accidentally save unencrypted data to the database.

- Ben