Status

P2
normal
RESOLVED FIXED
6 years ago
6 years ago

People

(Reporter: andy+bugzilla, Assigned: andy+bugzilla)

Tracking

2013-06-27
x86
Mac OS X
Points:
---

Details

(Whiteboard: [qa-])

(Assignee)

Description

6 years ago
In bug 863416 we wrote a payments logs. After chatting to oremj, he'd like it pushed to S3 by solitude once complete. This means adding in boto as a solitude dependency and then adding the code to push in that cron.
(Assignee)

Updated

6 years ago
Assignee: nobody → amckay
Priority: -- → P2
Target Milestone: --- → 2013-06-27
(Assignee)

Comment 1

6 years ago
https://github.com/mozilla/solitude/commit/72cec0
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
it would not be a bad idea to encrypt this log since it's going on S3. Even though it doesn't contain personal info, it contains opaque user hashes which can allow someone to create a purchase history.

Comment 3

6 years ago
(In reply to Kumar McMillan [:kumar] from comment #2)
> it would not be a bad idea to encrypt this log since it's going on S3. Even
> though it doesn't contain personal info, it contains opaque user hashes
> which can allow someone to create a purchase history.

has this been addressed?

Updated

6 years ago
Whiteboard: [qa-]
You need to log in before you can comment on or make changes to this bug.