It ain't your data, it's the bank's data about you. Banks are shitty about access, APIs because they are perpetually in CYA mode from KYC/AML rules from the US (also on most foreign banks) and GDPR and cousins in Europe.
I was actually surprised how many bank apps will work under GrapheneOS even if only partially.
Web banking means you need the card reader gadget as well for the authentication. The app uses secure features of the OS to aid authentication so you don't need to read the card. Web access on your phone still needs the card reader gadget.
Depends on where in the world you are, Norway for instance has not been using card chips for 2fa consumer auth for banking. Instead the 2fa has been a separate code generating gadget, and now also alternatively an app (which I do get the feeling the company that the banks set up handle auth for all of them are kinda pushing everyone into, but for now there thankfully is an option where you only need 1 online device with nothing more than a functioning browser).
Modern cards and phones support NFC, so you would only need a "gadget" (NFC reader) when using a PC that doesn't already have one, and a USB one is ~$20.
What this really needs is better browser support for NFC:
It's RFID communication with a smart card. The bank would have to transmit keys to your computer to be able to interface with it, which they probably won't want to do for security reasons.
The way chip cards work is that a challenge is issued to the card and it sends back a response. The challenge is just a random number that makes it so you can't replay a previous response to a future challenge. The bank can then verify that the response came from the card, i.e. that you have the card right now.
Your computer doesn't need to have any keys to do this. The card has a secret key, but it doesn't give it to the reader, it just responds to the challenge. The challenge often comes from a point of sale terminal, but it could just as easily come from the bank's web servers, and it isn't really a secret.
The only thing which resembles a secret here is the response from the card, which is the thing anyone can get regardless when have the card. Also, the entire premise of the card is that the attacker doesn't have it, so if they do then you've already lost that part of the game.
It's not the NFC the bank is interested it, it the MFA provided by your phone PIN, fingerprint or face unlock.
When you open the app on your phone, the phone probably needed to be unlocked first, though not everyone sets a PIN or biometric lock on their phone.
Then you will be prompted for a separate PIN or your fingerprint within the banking app. This provides a stronger signal to the bank that you are the legitimate account holder. If your phone is lost or stolen, the chances of someone else being able to authenticate to your banking app are considerably reduced.
With the web app, people will often save their bank website login credentials in the browser. So now someone nefarious only needs to access the unlocked computer or phone the go to the bank's website to gain unauthorised by still authenticated access to the customer's accounts.
Yes, there are now laptops and tablets with biometric authentication, so the potential is there for adding biometric authentication for banking website. However, when you look at the demographics of banking app vs website use, a strong majority of Millennials and Gen-Z do all their banking via the phone app. Gen-X also slightly favour the phone app whereas Boomers strongly prefer the website. So banks focus their development efforts where the majority of users are.
> When you open the app on your phone, the phone probably needed to be unlocked first, though not everyone sets a PIN or biometric lock on their phone.
The same is true for PCs. They've supported that sort of thing for decades, and it's optional for both the phone and the PC.
On top of that, a phone that people carry around everywhere is dramatically more likely to be lost or stolen than a desktop PC that never leaves their house.
> With the web app, people will often save their bank website login credentials in the browser.
If the bank actually cares about this then there are various ways to disable or impede it.
> However, when you look at the demographics of banking app vs website use
This is just the thing where you make something worse so fewer people use it and then use that as an excuse to keep making it worse. Nobody needs an app that could have been a web page, people use them because it's what get shoved down their throat if they don't go out of their way to do something else.
+1
I put as much as I can on wired ethernet. The WiFi is mostly for laptops & phones. I have a couple of APs (OpenWRT) that aren't meshed but I run 802.11r on them.
It's not really about the compilers ever since C99's restrict (you can almost always equal fortran performance now), it's how much more you have to think and validate about how to write the C/C++ plus the compiler and linker options to use.
Also with C99 you get many of the convenient aspects of fortran ( and vardim array function args) and with C11 you also get now.
But you are still missing fortran's ** operator and it's more than just syntactic sugar, it accepts more types.
I'd disagree. Most religions don't love apostasy but they also don't actively tell their members to go out of their way to punish or avoid non-believers.
The reason cults severely punish ex members is to protect the flock. They don't want their members to learn from ex members real criticisms of the cult.
It's precisely so when books like mentioned in this thread come up, the cult can say "oh, that's just a bad ex member who's lying".
The idea of "forbidden knowledge" is pretty unique to cults. You won't find, for example, a Methodist church that tells you not to read exmethodist books (do they even exist?). Heck, they probably wouldn't even get upset if you read something like "The god delusion".
This is hardly unique to Islam, many of the more hard-line Christian sects (Jehovahs, Christian Brethren, etc) as well as Haredi Jews also shun apostates.
The main difference is that in countries with shariah, apostasy is not just a sin, it's a criminal offense.
There's very few Muslim countries without legal Shariah... Turkey, 4 stans, Albania/Bosnia, and that's about it. Many of them are only "Muslim" as far as majority religion, locals might not even agree with that classification
There's a bunch of Muslim countries with Sharia not in criminal law but in marriage, maybe that's what you mean.
If your very own brother, or your son or daughter, or the wife you love, or your closest friend secretly entices you, saying, "Let us go and worship other gods" (gods that neither you nor your fathers have known, gods of the peoples around you, whether near or far, from one end of the land to the other), do not yield to him or listen to him. Show him no pity. Do not spare him or shield him. You must certainly put him to death. Your hand must be the first in putting him to death, and then the hands of all the people. Stone him to death, because he tried to turn you away from the LORD your God, who brought you out of Egypt, out of the land of slavery. Then all Israel will hear and be afraid, and no one among you will do such an evil thing again.
Do I know them by name? No I don't. It's a quote from wikipedia. Feel free to dispute it if you feel it's incorrect. I was commenting on the wiki link content GP posted.
I quoted the wikipedia page about it. There is a link there what source it came from. Just because I can't name imam Bob, Joe and Steve doesn't mean anything. I am not that interested in the topic but if you are feel free to dispute the source in the Wikipedia page and update it with better information.
Yes, we travelled to Cornwall in 1999 but it was cloudy. Got a marvellous view in Oregon in 2017 though. A friend of mine travels to all the solar eclipses he can wherever they are in the world. That's a bit too obsessive for me though. I'm in Devon this time but only 95% cover.
reply