From: Po Lu <luangruo@yahoo.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: emacs-devel@gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: Re: Making default permissions on Android more restrictive
Date: Wed, 13 Sep 2023 21:35:10 +0800 [thread overview]
Message-ID: <87zg1q42nl.fsf@yahoo.com> (raw)
In-Reply-To: <CADwFkm=CA_hTRLGxyo9g7gpnaucnM+E=jJxR9J1Jp_HDhAt7Dg@mail.gmail.com> (Stefan Kangas's message of "Wed, 13 Sep 2023 06:29:35 -0700")
Stefan Kangas <stefankangas@gmail.com> writes:
> Does this mean that if we want users to be able to enable these
> capabilities on Android 6.0 or later, they must also be enabled
> unconditionally on Android 5.1? I guess we can live with that.
Yes.
> That said, I still see no need for these capabilities, so I suggest we
> simply remove them:
>
> RECORD_AUDIO
> CAMERA
> ACCESS_COARSE_LOCATION
ACCESS_COARSE_LOCATION, RECORD_AUDIO and CAMERA are in fact useful. I
am aware of one package which refers to location, microphone and camera
data, the Telegram client:
https://github.com/zevlg/telega.el/
> REQUEST_INSTALL_PACKAGES
> REQUEST_DELETE_PACKAGES
These are harmless from a security perspective, as they only entitle
Emacs to display an installation dialog from the package manager itself.
They're also useful for debugging and perhaps updating Emacs from within
itself, if we eventually get to that.
next prev parent reply other threads:[~2023-09-13 13:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 12:07 Making default permissions on Android more restrictive Stefan Kangas
2023-09-13 12:34 ` Po Lu
2023-09-13 13:29 ` Stefan Kangas
2023-09-13 13:35 ` Po Lu [this message]
2023-09-13 13:31 ` Stefan Kangas
2023-09-13 13:36 ` Po Lu
2023-09-13 13:52 ` Stefan Kangas
2023-09-14 7:21 ` Jean Louis
-- strict thread matches above, loose matches on Subject: below --
2023-09-15 17:40 Ant
2023-09-16 0:53 ` Po Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zg1q42nl.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=stefankangas@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.