Closed Bug 1200427 Opened 11 years ago Closed 11 years ago

tc-base: base.Entity support for signed entities

Categories

(Taskcluster :: Services, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jonasfj, Assigned: jonasfj)

Details

Attachments

(1 file)

We should have a feature to HMAC sign entities store in azure table storage. That way injection in azure won't compromise us. This reduces attack vectors.
Attached file Github PR for base —
Hi, take a look at this... Adding a signature to all entities such that gaining access to our azure account you can delete stuff, but you won't be able to fake entities. Hence, an attacker will be forced to compromise our heroku app, the reduces our attack surface. For auth, I will encrypt the accessToken, but also sign the entity so someone with access to azure can't insert extra scopes with the secret key (given to taskcluster-auth through env var).
Assignee: nobody → jopsen
Status: NEW → ASSIGNED
Attachment #8655090 - Flags: review?(amiyaguchi)
Comment on attachment 8655090 [details] [review] Github PR for base Looks good to me, the code is straightforward and the tests seem to cover all the common use-cases.
Attachment #8655090 - Flags: review?(amiyaguchi) → review+
merged... thanks for the quick review...
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Component: Platform Libraries → Services
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: