75
edits
Phabricator/FAQ: Difference between revisions
Rework security patches question
No edit summary |
(Rework security patches question) |
||
| Line 4: | Line 4: | ||
== Phabricator == | == Phabricator == | ||
=== Can I use Phabricator for patches to security bugs? === | |||
Yes. Only people who are CC'd on the Bugzilla bug will be able to see your revision. | |||
Note there may be a short delay after submission before the revision is visible to other users. | |||
Reviews are connected with the BMO security groups. All revisions on Phabricator are initially non-public; when Bugzilla sees a new revision it checks the visibility of the bug and will update the revision to match: revisions referencing public bugs will be made public, and non-public bugs result in the BMO security group and CC list being mapped to the revision's policies. These are kept in sync as the bug changes. | |||
=== When I clicking the Phabricator “Log In or Register” button, why is a new tab is opened with the exception ‘Unhandled Exception(“AphrontMalformedRequestException”) Your browser did not submit a “phcid” cookie with client state information in the request’ === | === When I clicking the Phabricator “Log In or Register” button, why is a new tab is opened with the exception ‘Unhandled Exception(“AphrontMalformedRequestException”) Your browser did not submit a “phcid” cookie with client state information in the request’ === | ||
| Line 66: | Line 74: | ||
See [https://groups.google.com/forum/#!msg/mozilla.dev.platform/Y8kInYxo8UU/tsF7UfxvBgAJ this dev-platform post] for more information. | See [https://groups.google.com/forum/#!msg/mozilla.dev.platform/Y8kInYxo8UU/tsF7UfxvBgAJ this dev-platform post] for more information. | ||
=== Can I block review requests in Phabricator like I can in BMO? === | === Can I block review requests in Phabricator like I can in BMO? === | ||