ijeff@lemdro.idcakeM to Android@lemdro.idEnglish · 8 months agoGoogle’s “Web Integrity” Android API could kill “alternative” media clientsarstechnica.comexternal-linkmessage-square45fedilinkarrow-up1239arrow-down16cross-posted to: news@lemmy.linuxuserspace.showdegoogle@lemmy.ml
arrow-up1233arrow-down1external-linkGoogle’s “Web Integrity” Android API could kill “alternative” media clientsarstechnica.comijeff@lemdro.idcakeM to Android@lemdro.idEnglish · 8 months agomessage-square45fedilinkcross-posted to: news@lemmy.linuxuserspace.showdegoogle@lemmy.ml
minus-square0xD@infosec.publinkfedilinkEnglisharrow-up2arrow-down6·8 months agoThat is just standard and a completely sensible security measure for preventing people from tampering with an application. It cannot replace proper, server-side security measures but is a big step. Especially for stuff like banking applications.
minus-squareBaldDude@sh.itjust.workslinkfedilinkEnglisharrow-up9·edit-28 months agoI never really understood that: If I’m using my browser to do banking via the website, Having root privileges and tampering with the Browser running the applications is not an issue. If i use the banking app, Having root privileges suddenly become a problem. –> To me, it doesn’t look like the problem is technical, but that users are accepting things on mobile that they wouldn’t accept on a PC.
That is just standard and a completely sensible security measure for preventing people from tampering with an application. It cannot replace proper, server-side security measures but is a big step. Especially for stuff like banking applications.
I never really understood that:
If I’m using my browser to do banking via the website, Having root privileges and tampering with the Browser running the applications is not an issue.
If i use the banking app, Having root privileges suddenly become a problem.
–> To me, it doesn’t look like the problem is technical, but that users are accepting things on mobile that they wouldn’t accept on a PC.