Hello Chromium developers,
The Infrastructure Team is planning to make 2-Step Verification mandatory for all chromium.org accounts. This is part of an effort to strengthen security of the infrastructure.
To make this process smooth, we’re starting with at least a 2 week voluntary dogfood.
Note that I’ve personally verified the typical developer workflow (i.e. accessing codereview.chromium.org, uploading patches, triggering tryjobs, landing changes etc) works when using 2-Step Verification. It doesn’t guarantee it’ll work for you though, or that less common tasks work, which are the reasons why we’re starting with an opt-in dogfood.
Please see https://support.google.com/accounts/answer/185839?hl=en for instructions how to enable 2-Step Verification for your account. Also see https://www.google.com/landing/2step/ for more general context.
Once you enable it, consider switching from SMS codes to a security key (https://support.google.com/accounts/answer/6103534?hl=en) or an app (https://support.google.com/accounts/answer/1066447?hl=en).
If you’re a Googler, you can reuse your existing security key. Otherwise, see https://support.google.com/accounts/answer/6103523?hl=en for possible ways to get one, and note that it’s optional and you can still use SMS codes or the app instead.
You can see the list of currently known issues at https://code.google.com/p/chromium/issues/list?can=2&q=Proj%3D2FactorAuth .
Report any issues using the following link: https://code.google.com/p/chromium/issues/entry?labels=Infra,Proj-2FactorAuth .
It’s totally fine if you opt out after encountering a blocking issue. Make sure to file a bug for it using above link, and use https://support.google.com/accounts/answer/1064203?hl=en to disable 2-Step Verification for your account.
Please don’t hesitate to ask any questions about this process, or related comments or concerns.
Paweł
--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
--
You received this message because you are subscribed to the Google Groups "infra-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to infra-dev+...@chromium.org.
To post to this group, send email to infr...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/infra-dev/CAMeTaZfvrZjNG-HNKbNTmSUz5SkQuLy-Mgrpnvm5Erc6CLoZUg%40mail.gmail.com.
depot_tools has been using oauth2 for a while now. I believe that the command that you'd need to run is `depot-tools-auth logout` to remove the cookies, and `depot-tools-auth login` to log in again. The cookies live in your homedir.
it makes sense to me. enabling 2FA means when you want to get new credentials, you need to use 2FA. the process shouldn't (at least silently) expire all existing authentications. think how many places you have that are logged in now ... it'd be a pretty bad experience to force a sync on them all. it also wouldn't really make sense as there is already an existing page for doing this.
-mike
Wrt security, it might be related to the scope of the oauth2 token. For example, chrome itself uses an all encompassing login scoped token, and this is silently invalidated when 2sv is turned on. I'll ask the lso folks.
Thanks,
Roger
Wrt security, it might be related to the scope of the oauth2 token. For example, chrome itself uses an all encompassing login scoped token, and this is silently invalidated when 2sv is turned on. I'll ask the lso folks.
Thanks,
Roger
I think we also discovered that the setting doesn't seem to enable users who didn't have 2FA enabled to enroll once enforcement is in place.We're discussing possible solutions to this.