From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ulrich Mueller Newsgroups: gmane.emacs.devel Subject: Re: oauth2 support for Emacs email clients Date: Thu, 05 Aug 2021 09:45:56 +0200 Message-ID: References: <52589.36892.953561.24840@gargle.gargle.HOWL> <871r7aubp5.fsf@ucl.ac.uk> <87v94m1fkg.fsf@gnu.org> <871r78lt57.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="13669"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) Cc: emacs-devel@gnu.org To: Tim Cross Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Aug 05 09:46:58 2021 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 1mBY5h-0003NX-HN for ged-emacs-devel@m.gmane-mx.org; Thu, 05 Aug 2021 09:46:57 +0200 Original-Received: from localhost ([::1]:42214 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mBY5g-00021s-7z for ged-emacs-devel@m.gmane-mx.org; Thu, 05 Aug 2021 03:46:56 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53732) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mBY55-0001Lk-54 for emacs-devel@gnu.org; Thu, 05 Aug 2021 03:46:19 -0400 Original-Received: from mail.gentoo.org ([2001:470:ea4a:1:5054:ff:fec7:86e4]:38673 helo=smtp.gentoo.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mBY52-0000IA-Gw for emacs-devel@gnu.org; Thu, 05 Aug 2021 03:46:18 -0400 In-Reply-To: <871r78lt57.fsf@gmail.com> (Tim Cross's message of "Thu, 05 Aug 2021 08:45:25 +1000") Received-SPF: pass client-ip=2001:470:ea4a:1:5054:ff:fec7:86e4; envelope-from=ulm@gentoo.org; helo=smtp.gentoo.org X-Spam_score_int: -41 X-Spam_score: -4.2 X-Spam_bar: ---- X-Spam_report: (-4.2 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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:272075 Archived-At: >>>>> On Thu, 05 Aug 2021, Tim Cross wrote: > Thomas Fitzsimmons writes: >> IMAP and SMTP can use OAuth2 for authentication. But to properly >> support OAuth2 in Emacs, the FSF needs to talk to big email providers >> like Microsoft and Google and get Emacs registered as an OAuth2 >> application (like Thunderbird has done), or advocate for some better >> solution than embedding keys in the application binaries. This was >> discussed in bug 41386 [1]; I hope the FSF is working on it. > but isn't this the issue - a 'registered' application is just one which > has a registered application id key, but the T&C for the major mail > providers does not allow that registered ID token to be public, which > means it cannot be put into Emacs source code. This means there is no > practical advantage in Emacs being registered. Where do proprietary clients store their ID token, if not in the application itself?