From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: gmail+imap+smtp (oauth2) Date: Fri, 06 May 2022 07:38:12 -0400 Message-ID: References: <871qxbdulc.fsf@mat.ucm.es> <87k0b2tkg1.fsf@mat.ucm.es> <87zgjx4qhs.fsf@gmail.com> <87bkwcgmr3.fsf@mat.ucm.es> <87levfzqj2.fsf@yale.edu> <871qx7scvi.fsf@gmail.com> <87v8ujqec5.fsf@logand.com> <87ee172fjz.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="11245"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: Tomas Hlavaty , "Jorge A. Alfaro-Murillo" , emacs-devel@gnu.org To: Tim Cross Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri May 06 13:44:32 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 1nmwNs-0002mA-8v for ged-emacs-devel@m.gmane-mx.org; Fri, 06 May 2022 13:44:32 +0200 Original-Received: from localhost ([::1]:42082 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nmwNr-0007w1-6B for ged-emacs-devel@m.gmane-mx.org; Fri, 06 May 2022 07:44:31 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34020) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nmwHr-0003FX-6m for emacs-devel@gnu.org; Fri, 06 May 2022 07:38:20 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:26031) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nmwHn-0006Y7-MA for emacs-devel@gnu.org; Fri, 06 May 2022 07:38:16 -0400 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 9A9E710029F; Fri, 6 May 2022 07:38:14 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 4A2FA10012C; Fri, 6 May 2022 07:38:13 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1651837093; bh=GiR+03R9JQSj/M1phaKwl+BMaLQUDe2/VgY9n2Eqgq0=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=AVHMlQh9W3lKVRP5DrVx1yvFsa8i6qch8oaJ0hlKzjsG33TEEoqd5KZJBDNr87S5s lBEpZMg/S8zenMCRWkmjsoKcOJ+ns+ItYEAzjayrVMTcY9J0rNzmGmLHPtaKBM3/wy jjF/NzMIcp5ApqgTwfgTKYIdT07FfZB2HR1Sbo7XCyUxh+EbZBD+O4emhbuY4Zp2JW b2FmwjNqTsBB5dM/uO7fAPlhi+XNUI6iKoSdHKWzgzcZPlXfwhDHUBUt48a3MTUczB vMvQFduUgHjduwPiGxz+NqIqNVVt47tsVEiewRrkb5c8/vNfTuLDYG89i6Z+gPoNIk wfI5ZFAdmYrYg== Original-Received: from pastel (unknown [45.72.221.51]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 0F46F120247; Fri, 6 May 2022 07:38:13 -0400 (EDT) In-Reply-To: <87ee172fjz.fsf@gmail.com> (Tim Cross's message of "Fri, 06 May 2022 19:04:20 +1000") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, 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:289311 Archived-At: > Problem is, Google T&C require that the application ID is kept secret. > For open source, this is a problem because we cannot add the applicaiton > ID and keep it secret while making the code open source. FWIW, it's also a problem for proprietary applications since the secret will necessarily be somewhere inside the executable as well. It's a bit harder to find, and can be obfuscated to some extent, but as long as you can run the code inside a debugger and you have enough time on your hands to reverse engineer the workings of that part of the code you can also extract the application ID. Stefan