From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings via "Emacs development discussions." Newsgroups: gmane.emacs.devel Subject: Re: Re: Making GNUS continue to work with Gmail Date: Mon, 17 Aug 2020 12:30:41 +0000 Message-ID: References: <875z9p5hnc.fsf@mat.ucm.es> <87364pbkn0.fsf@gnus.org> <87lfihe0zf.fsf@mat.ucm.es> <874kp55l8t.fsf@gnus.org> <36ed8579.3c38.173fb016f00.Coremail.m_pupil@163.com> <20200817082315.GB13459@tuxteam.de> Reply-To: Gregory Heytings Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="32933"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Alpine 2.21 (NEB 202 2017-01-01) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Aug 17 14:31:44 2020 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 1k7eIi-0008UJ-69 for ged-emacs-devel@m.gmane-mx.org; Mon, 17 Aug 2020 14:31:44 +0200 Original-Received: from localhost ([::1]:52478 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1k7eIh-00083t-8C for ged-emacs-devel@m.gmane-mx.org; Mon, 17 Aug 2020 08:31:43 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38170) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k7eHy-0006uJ-GX for emacs-devel@gnu.org; Mon, 17 Aug 2020 08:30:58 -0400 Original-Received: from mx.sdf.org ([205.166.94.24]:58865) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1k7eHw-00070Y-Ct for emacs-devel@gnu.org; Mon, 17 Aug 2020 08:30:58 -0400 Original-Received: from sdf.org (IDENT:ghe@faeroes.freeshell.org [205.166.94.9]) by mx.sdf.org (8.15.2/8.14.5) with ESMTPS id 07HCUiAx002733 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits) verified NO); Mon, 17 Aug 2020 12:30:45 GMT Original-Received: (from ghe@localhost) by sdf.org (8.15.2/8.12.8/Submit) id 07HCUikp000677; Mon, 17 Aug 2020 12:30:44 GMT In-Reply-To: <20200817082315.GB13459@tuxteam.de> Received-SPF: pass client-ip=205.166.94.24; envelope-from=ghe@sdf.org; helo=mx.sdf.org X-detected-operating-system: by eggs.gnu.org: First seen = 2020/08/17 08:30:48 X-ACL-Warn: Detected OS = ??? 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 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:253876 Archived-At: > > He explains the drawbacks of this approach: Google doesn't *want* that > the app's users see the password. But the app is free software, so *we* > want that the users see everything in the app. > That's what Google's official terms of service state. But in practice this is not enforced, Google tolerates that free software projects violate that specific point of their TOS. Otherwise Kmail, Thunderbird and others would not work with Gmail. They do work with Gmail, because they include OAuth credentials in their source code. For that matter, Google knows very well that this is nothing but "security through obscurity", given that OAuth credentials are at least embedded in the program binary (or perhaps stored somewhere else and read by the program). Gregory