From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jean Louis Newsgroups: gmane.emacs.devel Subject: Re: Making default permissions on Android more restrictive Date: Thu, 14 Sep 2023 10:21:02 +0300 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33093"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/2.2.10+64 (b470a9a) (2023-06-05) Cc: emacs-devel@gnu.org To: Stefan Kangas Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Sep 14 09:22:34 2023 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 1qgggL-0008Qe-Sc for ged-emacs-devel@m.gmane-mx.org; Thu, 14 Sep 2023 09:22:33 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qggfZ-00023A-Nq; Thu, 14 Sep 2023 03:21:45 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qggfY-00022i-Ja for emacs-devel@gnu.org; Thu, 14 Sep 2023 03:21:44 -0400 Original-Received: from stw1.rcdrun.com ([217.170.207.13]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qggfW-0000o8-KU for emacs-devel@gnu.org; Thu, 14 Sep 2023 03:21:44 -0400 Original-Received: from localhost ([::ffff:41.75.170.180]) (AUTH: PLAIN admin, TLS: TLS1.3,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by stw1.rcdrun.com with ESMTPSA id 0000000000055D66.000000006502B463.00007771; Thu, 14 Sep 2023 00:21:06 -0700 Mail-Followup-To: Stefan Kangas , emacs-devel@gnu.org Content-Disposition: inline In-Reply-To: Received-SPF: pass client-ip=217.170.207.13; envelope-from=bugs@gnu.support; helo=stw1.rcdrun.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 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:310571 Archived-At: * Stefan Kangas [2023-09-13 15:10]: > [I couldn't find any previous discussion about this.] > > 1. > > a) I don't see why Emacs should be asking for these permissions on > Android 5.1 and earlier: > > RECORD_AUDIO > CAMERA > ACCESS_COARSE_LOCATION > REQUEST_INSTALL_PACKAGES > REQUEST_DELETE_PACKAGES > READ_SMS > RECEIVE_SMS > SEND_SMS > WRITE_SMS > RECEIVE_MMS > READ_CONTACTS > WRITE_CONTACTS I hope to see Emacs being able to do use all of the permissions on Android. > Are there any technical reasons why we need the above permissions? If > not, can we remove them, at least the ones in category (a) and (b)? Emacs has Emacs Lisp, I use it for running programs and Emacs on Android will hopefully get functions to use above permissions. 1. RECORD_AUDIO: Emacs could use this permission to enable voice commands or voice-controlled editing features within the editor. 2. CAMERA: Emacs could utilize the camera permission for functionalities such as capturing and inserting images directly into documents, visual recognition features, or scanning QR codes. 3. ACCESS_COARSE_LOCATION: Emacs could leverage this permission to provide location-based information or contextual features, such as displaying weather information or adjusting settings based on the user's location. 4. REQUEST_INSTALL_PACKAGES: Emacs may need this permission to facilitate the installation of additional packages or plugins from external sources to enhance its functionality. 5. REQUEST_DELETE_PACKAGES: This permission could be used by Emacs to uninstall packages or plugins when requested by the user. 6. READ_SMS, RECEIVE_SMS, SEND_SMS, WRITE_SMS, RECEIVE_MMS: Emacs could utilize these permissions to integrate SMS or MMS-based features, such as sending code snippets via SMS, receiving notifications or alerts through SMS, or extracting relevant information from received messages. 7. READ_CONTACTS, WRITE_CONTACTS: Emacs could use these permissions to access and modify the user's contact information, enabling features like autocomplete or inserting contact details into documents. > NFC > TRANSMIT_IR 1. NFC: Emacs could use the NFC permission to interact with Near Field Communication (NFC) tags or devices. For example, Emacs could read data from NFC tags containing programming instructions or use NFC for authentication purposes. 2. TRANSMIT_IR: Emacs could utilize the TRANSMIT_IR permission to control infrared (IR) devices. This could include using Emacs as a remote control for TVs, air conditioners, or other IR-enabled devices directly from within the editor. -- Jean Take action in Free Software Foundation campaigns: https://www.fsf.org/campaigns In support of Richard M. Stallman https://stallmansupport.org/