Emacs - excessive permissions

Hi all,

I was quite excited to see a port of Emacs in the registry, although the list of permissions is much broader than I expected (eg. recording audio, WRITE_SMS, control Near Field Communication). These are not permissions I would expect stock Emacs to need. Some of the other permissions (reading contacts, reading text messages) also seem quite dangerous by default.

Does anyone know if this port of Emacs is safe from a data perspective? Any help would be greatly appreciated.

Wow that is AWFUL.
They appear to declare/request every permission possible: AndroidManifest.xml.in\java - emacs.git - Emacs source repository

Most of it was added here: emacs.git - Emacs source repository

They seem to do it purposely calling the Android security model as “fascist security restrictions”.

1 Like

Thanks for the links @SkewedZeppelin. The approach they took feels contrary to the spirit of Emacs. I suppose that users can go into their settings and disable unwanted permissions, but that would be quite an undertaking given that all permissions are requested.

It is not my project, so it is not my place to judge, but the term “fascist” is poorly placed here. I think that it is, in fact, more fascist to have the following enabled by default (and more):

  • READ_CALL_LOG
  • RECORD_AUDIO
  • BODY_SENSORS_BACKGROUND
  • BLUETOOTH_ADMIN

Ultimately it is the maintainers decision, but I feel quite disappointed with this.

1 Like

Obviously a clash of cultures. Ask eg Termux devs how they feel about Android restrictions (rhetoric Q)

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.