Android
DROID DOES
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
view the rest of the comments
I work for a company that builds an app /sdk that handles credit cards / payments. It's one of the (many) requirements for getting an industry standard certification (like PCIDSS / MPOC). The app Must block screenshots, and Must disable the camera while using it...
What on earth are those in charge of certification standards thinking they'll achieve with requirements like this?
It's probably to stop third party apps from screenshoting the banking app.
Why is this only a problem on mobile? Why doesn't desktop have similar requirements?
tbh the security settings on desktop devices tend to be more lax in general; for example almost any desktop pc has an open bootloader, means you can sideload an operating system from usb. The consequence is that no password-at-login will protect your private data; only full disk encryption can.
Smartphones on the other hand often have a fully-locked bootloader, which means it's totally non-trivial to install an alternative operating system. especially, it often contains wiping any data on the smartphone, so an attacker with access to the device can't simply install their own OS and read the internal storage.
I don't know.
The same functionality that you use to take screenshots can be hijacked by bad actors to get access to your stuff. It's especially bad if they can see your MFA apps or other sensitive info.
Not saying the functionality is always used for the best of intentions, but there are many situations where I see it as necessary.
Accidentally screenshotting your bank acct and routing number is the only one I can really think of.
Or your "time clock earth sounds" app from the not so well policed appstore takes silent background screenshots, grayscales them and sends them to their host for OCR.
I agree this permission is annoying. But I differ in I feel it should be system controlled and can be invoked by apps that identify specific fields to be blocked, instead ofnjusy disabling it outright.
Not sure how this is relevant, these numbers are routinely shared with clients and suppliers.
Why did you capitalize "must"?
Probably a nod to the written style of RFC definitions, which have the word entirely in capital letters, as in... the implementation MUST do such and such, and SHOULD do this other thing. In this case, the relevant security standard(s)
We have italics and bold characters for that.
RFCs were being written back when line printers couldn't do either.
I misread your comment and thought you said "RFK". I have no idea what an "RFC" is. Some sort of teletype thing?
RFCs are Requests For Comment, published technical documents describing proposed standards.