From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Brian Cully via "Emacs development discussions." Newsgroups: gmane.emacs.devel Subject: Re: gmail+imap+smtp (oauth2) Date: Thu, 05 May 2022 17:34:01 -0400 Message-ID: <87sfpnk66z.fsf@ditto.jhoto.spork.org> References: <871qxbdulc.fsf@mat.ucm.es> <877d72nf3h.fsf@gmail.com> <87zgjx9upa.fsf@telefonica.net> <87zgjx5mek.fsf@gmail.com> <87v8ul9tho.fsf@telefonica.net> Reply-To: Brian Cully Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="8597"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: mu4e 1.6.10; emacs 28.1 Cc: =?utf-8?B?w4PCk3NjYXI=?= Fuentes , emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu May 05 23:43:30 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nmjFx-00028f-AT for ged-emacs-devel@m.gmane-mx.org; Thu, 05 May 2022 23:43:29 +0200 Original-Received: from localhost ([::1]:38748 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nmjFw-0007rF-2u for ged-emacs-devel@m.gmane-mx.org; Thu, 05 May 2022 17:43:28 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:55108) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nmjEy-0007AK-3B for emacs-devel@gnu.org; Thu, 05 May 2022 17:42:28 -0400 Original-Received: from coleridge.kublai.com ([166.84.7.167]:52681 helo=mail.spork.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nmjEw-0005S8-Ij; Thu, 05 May 2022 17:42:27 -0400 Original-Received: from ditto (unknown [IPv6:2001:470:1f07:1b9:8650:a942:ec5e:856b]) by mail.spork.org (Postfix) with ESMTPSA id 8D0735ACB; Thu, 5 May 2022 17:41:59 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=spork.org; s=dkim; t=1651786924; bh=O9fAieI24Wt/aeY8Hh6S9KjMumLze9Grsc9sisE5fUk=; h=References:From:To:Cc:Subject:Date:In-reply-to; b=LrMIB+R2ZzkGHg1GeMxUluXoA7EuvST4lg/zEVdrLPA0vilvVavtker87eBVwWpIR YiQVa0Z2IIeiOVp0ywt0omfQU9YBuYkI2Bz0043fJVno86nV4zs4nTGSkizIVrNuKf K5epjT5kDM5k49Nz65MbWXsKYqORwnw0gc5kGBHo= In-reply-to: Received-SPF: pass client-ip=166.84.7.167; envelope-from=bjc@spork.org; helo=mail.spork.org X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:289283 Archived-At: Richard Stallman writes: > Does it have to be _your_ phone number, or can it be any phone > that you can answer at the time of creating the app password? > Will Google ever phone you again on the same number? > > Another question is, does setting up the app password require > a computer running nonfree software? (For instance, a mobile=20 > phone.) > Can you do this with a landline? It does not have to be your phone number, no. They will send an=20 SMS to whatever number you choose (so long as its not on a=20 blacklist somewhere). You do not need to run non-free software,=20 presuming you can receive SMS with non-free software (there are=20 services for such things). However, you have the choice of using TOTP for 2FA[1], in which=20 case you can use any number of free applications to generate codes=20 for you. If you use SMS as your 2FA, Google will send messages to=20 you periodically as you attempt to log in to services (though only=20 with your main password - not app passwords). Once converted to=20 TOTP, though, I do not believe Google will ever try to contact you=20 again. I have set up Google accounts using burner numbers and=20 converted them to TOTP without any issue over the years. However,=20 there=E2=80=99s obviously no guarantee that Google will continue to allow=20 this in the future. -bjc [1] There may be restrictions I=E2=80=99m not aware of when using TOTP, as= =20 I=E2=80=99d set mine up a long time ago. You may, for instance, need to be= =20 able to receive SMS in order to do the initial TOTP setup. You=20 definitely need to use SMS to do initial account setup.