From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Tomas Hlavaty Newsgroups: gmane.emacs.devel Subject: Re: gmail+imap+smtp (oauth2) Date: Fri, 06 May 2022 10:34:41 +0200 Message-ID: <87r157qcta.fsf@logand.com> References: <871qxbdulc.fsf@mat.ucm.es> <877d72nf3h.fsf@gmail.com> <87v8ul4ad4.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="16815"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Richard Stallman , jostein@kjonigsen.net, emacs-devel@gnu.org To: Thomas Fitzsimmons , Tim Cross Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri May 06 10:35:51 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 1nmtRH-0004Bs-GY for ged-emacs-devel@m.gmane-mx.org; Fri, 06 May 2022 10:35:51 +0200 Original-Received: from localhost ([::1]:34296 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nmtRG-0000mR-2R for ged-emacs-devel@m.gmane-mx.org; Fri, 06 May 2022 04:35:50 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56140) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nmtQF-0008Tl-7G for emacs-devel@gnu.org; Fri, 06 May 2022 04:34:47 -0400 Original-Received: from logand.com ([37.48.87.44]:40678) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nmtQD-0001t0-IZ; Fri, 06 May 2022 04:34:46 -0400 Original-Received: by logand.com (Postfix, from userid 1001) id 7C67E19FEAD; Fri, 6 May 2022 10:34:43 +0200 (CEST) X-Mailer: emacs 27.2 (via feedmail 11-beta-1 I) In-Reply-To: Received-SPF: pass client-ip=37.48.87.44; envelope-from=tom@logand.com; helo=logand.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-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:289300 Archived-At: On Wed 04 May 2022 at 11:41, Thomas Fitzsimmons wrote: >>> One issue with OAuth2 schemes is that they periodically force the user >>> through a web-browser-only authentication process that requires non-free >>> JavaScript, in order to get a refresh token. [...] >> There is nothing which requires oauth2 be implemented in Javascript or >> that requies it to use non-free software. exactly getting the bearer token is just a few https requests > So can you describe how to get an OAuth 2.0 gmail.com refresh token > without the use of non-free JavaScript? i don't use gmail so i cannot answer this specific question but as pointed out, the real issue is not so much on the client side but on the server side