Path: ...!3.eu.feeder.erje.net!feeder.erje.net!news2.arglkargh.de!news.karotte.org!news.szaf.org!nntp-feed.chiark.greenend.org.uk!ewrotcd!.POSTED.chiark.greenend.org.uk!not-for-mail From: Theo Newsgroups: comp.mobile.android Subject: Re: ebook-reader permissions - no explanation given Date: 28 May 2024 11:34:15 +0100 (BST) Organization: University of Cambridge, England Message-ID: References: Injection-Info: chiark.greenend.org.uk; posting-host="chiark.greenend.org.uk:93.93.131.173"; logging-data="17536"; mail-complaints-to="abuse@chiark.greenend.org.uk" User-Agent: tin/1.8.3-20070201 ("Scotasay") (UNIX) (Linux/5.10.0-28-amd64 (x86_64)) Originator: theom@chiark.greenend.org.uk ([93.93.131.173]) Bytes: 1852 Lines: 22 R.Wieser wrote: > Theo, > > > This is the manifest file: [snip] > > > > which has the read storage permission, but not write or the phone > > status permission. Maybe the latter comes from some library it uses? > > I was trying to figure out the legit reasons for the permissions. They > could really be needed. > > But yes, thats something thats also something to consider. Third parties > which embed stuff neither the app-maker nor the user have asked for. > > By the way: that ebook reader program you referred to which only asks for > read permissions - Is there an APK available of it ? Maybe it already does > what I need from it. That is the app you downloaded. If you go to F-droid and download the sources tarball for this app you'll find they match the ones I linked to (it was easier to link to upstream sources on Gitlab than a tarball) Theo