Closed
Bug 661264
Opened 14 years ago
Closed 14 years ago
repack is returning the wrong secret key
Categories
(addons.mozilla.org Graveyard :: Add-on Builder, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
Builder 0.9.6
People
(Reporter: jbalogh, Unassigned)
Details
Comment 1•14 years ago
|
||
There are 2 keys
AMO_SECRET_KEY which is a proof for Builder the request came from AMO
and BUILDER_SECRET_KEY which is a proof for AMO the request came from Builder
| Reporter | ||
Comment 2•14 years ago
|
||
(In reply to comment #1)
> There are 2 keys
> AMO_SECRET_KEY which is a proof for Builder the request came from AMO
> and BUILDER_SECRET_KEY which is a proof for AMO the request came from Builder
It's easier if we maintain a single secret.
Target Milestone: Builder 0.9.7 → Builder 0.9.6
Comment 3•14 years ago
|
||
(In reply to comment #2)
> (In reply to comment #1)
> > There are 2 keys
> > AMO_SECRET_KEY which is a proof for Builder the request came from AMO
> > and BUILDER_SECRET_KEY which is a proof for AMO the request came from Builder
>
> It's easier if we maintain a single secret.
Having them separate is fine - If they are separate compromising one doesn't compromise both. I thought I saw a patch about this earlier today - is this bug closed or being worked on?
Comment 4•14 years ago
|
||
Closed, it's easy to back if needed
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
| Assignee | ||
Updated•11 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•