Change Details

PHI979 is a specific issue where we could use better instance controls (around worker count) in the short term. An alternative approach is to hard-coded `if ($instance === 'X') { ... }` for now. `admin` could also probably use more workers, I think we get saturated by backups occasionally. See PHI857, which wants support for serial queues in repository operations. See PHI989, which notes some consistency issues with certain datasource queries, particularly when some components are empty. SSH key handling (mostly in T13123) is fairly ripe. Related are these HackerOne reports, which are primarily just informative, but solid reports: - https://hackerone.com/reports/474897 - Weak SSH keys should be detected and rejected. - https://hackerone.com/reports/475126 - The SSH key "comment" field is exposed via the API, but it turns out that a whole lot of users put their entire personal diary into the "comment" field of their "public" keys. PHI1051 wants support for overriding custom field behaviors in subtypes. See D17593, previously. PHI774 identifies an issue which can likely be mitigated in the short term by improving the "Welcome" flow for non-password installs. PHI1052 encountered a card issue with Stripe. This might be a problem with the card, but the workflow should be more clear. PHI912 would like auto-status ~~and auto-submit~~ for Duo. Phacility instances don't allow administrators to manage auth providers. This is good, but it also means that administrators can't manage MFA. We should either separate these permissions or maybe automatically create a TOTP MFA provider for now? --- PHI1050 identified some out-of-date documentation. D20080 has an instance service call which should receive jitter. PHI1047 notes an API inconsistency between `owners.search` and `owners.edit`. User renames show up in feed but don't have a feed-oriented rendering ("this user" instead of "<old username">): <https://secure.phabricator.com/feed/6654516638475651570/> The "Members" UI under instances still has a couple of issues: - Invites which were cancelled but ultimately registered (through automatic domain registration? Old invites? Is this just a bug?) show as "cancelled", but should show in a user bucket. - Users can be instance managers and in a lot of other states (Unregistered, Disabled). Our icon signaling isn't terribly clear in these cases. - Unregistered users should show up as "invited". D20093 fixes a mobile application menu in Mail. It would be very nice to fix this in a generic way instead. (This may also affect Instances.) See PHI1055, which would like more sophisticated Owners Audit behavior. PHI1034 is a cluster invoicing thing which should be sorted out.

PHI979 is a specific issue where we could use better instance controls (around worker count) in the short term. An alternative approach is to hard-coded `if ($instance === 'X') { ... }` for now. `admin` could also probably use more workers, I think we get saturated by backups occasionally. See PHI857, which wants support for serial queues in repository operations. See PHI989, which notes some consistency issues with certain datasource queries, particularly when some components are empty. SSH key handling (mostly in T13123) is fairly ripe. Related are these HackerOne reports, which are primarily just informative, but solid reports: - https://hackerone.com/reports/474897 - Weak SSH keys should be detected and rejected. - https://hackerone.com/reports/475126 - The SSH key "comment" field is exposed via the API, but it turns out that a whole lot of users put their entire personal diary into the "comment" field of their "public" keys. PHI1051 wants support for overriding custom field behaviors in subtypes. See D17593, previously. PHI774 identifies an issue which can likely be mitigated in the short term by improving the "Welcome" flow for non-password installs. PHI912 would like auto-status ~~and auto-submit~~ for Duo. Phacility instances don't allow administrators to manage auth providers. This is good, but it also means that administrators can't manage MFA. We should either separate these permissions or maybe automatically create a TOTP MFA provider for now? --- PHI1050 identified some out-of-date documentation. D20080 has an instance service call which should receive jitter. PHI1047 notes an API inconsistency between `owners.search` and `owners.edit`. User renames show up in feed but don't have a feed-oriented rendering ("this user" instead of "<old username">): <https://secure.phabricator.com/feed/6654516638475651570/> The "Members" UI under instances still has a couple of issues: - Invites which were cancelled but ultimately registered (through automatic domain registration? Old invites? Is this just a bug?) show as "cancelled", but should show in a user bucket. - Users can be instance managers and in a lot of other states (Unregistered, Disabled). Our icon signaling isn't terribly clear in these cases. - Unregistered users should show up as "invited". D20093 fixes a mobile application menu in Mail. It would be very nice to fix this in a generic way instead. (This may also affect Instances.) See PHI1055, which would like more sophisticated Owners Audit behavior. PHI1034 is a cluster invoicing thing which should be sorted out. PHI1052 encountered a card issue with Stripe. This might be a problem with the card, but the workflow should be more clear.

PHI979 is a specific issue where we could use better instance controls (around worker count) in the short term. An alternative approach is to hard-coded `if ($instance === 'X') { ... }` for now. `admin` could also probably use more workers, I think we get saturated by backups occasionally. See PHI857, which wants support for serial queues in repository operations. See PHI989, which notes some consistency issues with certain datasource queries, particularly when some components are empty. SSH key handling (mostly in T13123) is fairly ripe. Related are these HackerOne reports, which are primarily just informative, but solid reports: - https://hackerone.com/reports/474897 - Weak SSH keys should be detected and rejected. - https://hackerone.com/reports/475126 - The SSH key "comment" field is exposed via the API, but it turns out that a whole lot of users put their entire personal diary into the "comment" field of their "public" keys. PHI1051 wants support for overriding custom field behaviors in subtypes. See D17593, previously. PHI774 identifies an issue which can likely be mitigated in the short term by improving the "Welcome" flow for non-password installs. PHI1052 encountered a card issue with Stripe. This might be a problem with the card, but the workflow should be more clear. PHI912 would like auto-status ~~and auto-submit~~ for Duo. Phacility instances don't allow administrators to manage auth providers. This is good, but it also means that administrators can't manage MFA. We should either separate these permissions or maybe automatically create a TOTP MFA provider for now? --- PHI1050 identified some out-of-date documentation. D20080 has an instance service call which should receive jitter. PHI1047 notes an API inconsistency between `owners.search` and `owners.edit`. User renames show up in feed but don't have a feed-oriented rendering ("this user" instead of "<old username">): <https://secure.phabricator.com/feed/6654516638475651570/> The "Members" UI under instances still has a couple of issues: - Invites which were cancelled but ultimately registered (through automatic domain registration? Old invites? Is this just a bug?) show as "cancelled", but should show in a user bucket. - Users can be instance managers and in a lot of other states (Unregistered, Disabled). Our icon signaling isn't terribly clear in these cases. - Unregistered users should show up as "invited". D20093 fixes a mobile application menu in Mail. It would be very nice to fix this in a generic way instead. (This may also affect Instances.) See PHI1055, which would like more sophisticated Owners Audit behavior. PHI1034 is a cluster invoicing thing which should be sorted out. PHI1052 encountered a card issue with Stripe. This might be a problem with the card, but the workflow should be more clear.