Re: W3C Proposed Recommendation: Web Authentication

2019-02-08 Thread Joseph Lorenzo Hall
+1 and thank you for all the hard work on the spec and landing so much in FF, JCJ!!! On Fri, Feb 8, 2019 at 4:09 PM J.C. Jones wrote: > Out of all multi-factor authentication solutions I know of, Web > Authentication is our best technical response to the scourge of phishing. > Tying public-key c

Re: W3C Proposed Recommendation: Web Authentication

2019-02-08 Thread J.C. Jones
Out of all multi-factor authentication solutions I know of, Web Authentication is our best technical response to the scourge of phishing. Tying public-key cryptography into web logins, it dramatically raises the bar for phishing: From a simple confusable website and replay attack, to an HTTPS netwo

Re: Moving reviews to Phabricator

2019-02-08 Thread J.C. Jones
The NSS team still uplifts from https://hg.mozilla.org/projects/nss/ into m-c a few times per week (or as needed) using inbound .

Re: Moving reviews to Phabricator

2019-02-08 Thread Nathan Froyd
On Fri, Feb 8, 2019 at 9:08 AM Andreas Tolfsen wrote: > Whilst I don’t have first hand experience, Phabricator has been > known to struggle with large patches, such as the result of upgrading > cargo dependencies under third_party/rust. Was a bug ever filed > on this? Bug 1492214 was filed for l

Re: Moving reviews to Phabricator

2019-02-08 Thread Andreas Tolfsen
Also sprach Kim Moir: > Requiring Phabricator for code reviews will allow us to improve > code quality by running linters and static analysis tools automatically > on patches. It will also allow us to simplify and standardize our > engineering workflow by reducing the number of request queues tha