Andy McKay Assignee
	Description • 12 years ago

Should we be encrypting key fields?

Things include: pre-approval key, paypal_id of the seller.

If so how?

	Kumar McMillan [:kumar]
	Comment 1 • 12 years ago

rforbes: last time I remember talking about this we discussed using a key file on disk and doing AES encrypt/decrypt with the MySQL function. This is what we do for the in-app payment secrets: bug 742751

	Raymond Forbes[:rforbes]
	Comment 2 • 12 years ago

sounds good to me.

	Andy McKay Assignee
	Comment 3 • 12 years ago

I'd like to encrypt the following fields:

Buyers: key (< preapproval key)
Sellers: paypal_id (< paypal_email), token (< permissions token), secret (< permissions secret)

Is it possible to abstract that AES field a little so we just say models.AESField? Would be a nice library to have lying around for this stuff.

	Kumar McMillan [:kumar]
	Comment 4 • 12 years ago

(In reply to Andy McKay [:andym] from comment #3)
> Is it possible to abstract that AES field a little so we just say
> models.AESField? Would be a nice library to have lying around for this stuff.

Yeah, that's exactly what I'm thinking too. I think we can expand the implementation here https://github.com/mozilla/zamboni/commit/32883fe58a89b3f429a0512fd1f9ea50c4e33c66#L0R370 to be more like http://djangosnippets.org/snippets/2489/

	Andy McKay Assignee
	Comment 5 • 12 years ago

That would be awesome.

	Andy McKay Assignee
	Comment 6 • 12 years ago

@rforbes: does this encryption remove the requirement for bug 759021 or should that requirement be part of this bug?

	Andy McKay Assignee
	Comment 7 • 12 years ago

For the record, encryption of data using a PIN is not required. That will be seperate.

	Andy McKay Assignee
	Comment 8 • 12 years ago

https://github.com/mozilla/solitude/commit/aa971a