5 ms·

And that's not going to happen. Apple have tied their NFC chip closely to their secure enclave; there's no freaking way Apple are going to let a bunch of third

And that's not going to happen. Apple have tied their NFC chip closely to their secure enclave; there's no freaking way Apple are going to let a bunch of third rate subcontractors go anywhere near it.

darawk 10y ago
It would be trivial to create an API for the secure enclave and the NFC chip that sandboxed apps to prevent them from manipulating each other's data. Apple is simply choosing not to do it.
- pilif 10y ago
  It's definitely not trivial to do this in a secure way. Every bit of additional code is code that could contain security flaws. Also, looking at how the banks are doing over here ("your password can't be longer than 16 characters and can't contain the following symbols: " ' %"), I'm trusting apple more than the banks.
  - tmd83 10y ago
    It can very well be that Apple is or will design a more secure system than most back. They are after all good at security and one of the largest technology company. But the question here is that there are generic hardware in iPhone that can be used by anybody to make contactless payment good/bad. Apple is not giving them the access not just because of security but to reduce competition. If you don't trust your bank but apple the bank is not forcing you to use their app so that point doesn't really apply. What if Intel/AMD or any processor company was saying the the encoding hardware of their device was only accessible to their own app and not to other application in your device since others wouldn't know how to use it properly?
    - caspianm 10y ago
      Here is a discussion of Intel limiting the code that can run in security subsystems in their processors: https://news.ycombinator.com/item?id=11007060 https://news.ycombinator.com/item?id=11007060 I'm not saying this is acceptable, but it seems to be happening.

5 ms·

And that's not going to happen. Apple have tied their NFC chip closely to their secure enclave; there's no freaking way Apple are going to let a bunch of third

by sjwright 10y ago

darawk 10y ago
It would be trivial to create an API for the secure enclave and the NFC chip that sandboxed apps to prevent them from manipulating each other's data. Apple is simply choosing not to do it.
- pilif 10y ago
  It's definitely not trivial to do this in a secure way. Every bit of additional code is code that could contain security flaws. Also, looking at how the banks are doing over here ("your password can't be longer than 16 characters and can't contain the following symbols: " ' %"), I'm trusting apple more than the banks.
  - tmd83 10y ago
    It can very well be that Apple is or will design a more secure system than most back. They are after all good at security and one of the largest technology company. But the question here is that there are generic hardware in iPhone that can be used by anybody to make contactless payment good/bad. Apple is not giving them the access not just because of security but to reduce competition. If you don't trust your bank but apple the bank is not forcing you to use their app so that point doesn't really apply. What if Intel/AMD or any processor company was saying the the encoding hardware of their device was only accessible to their own app and not to other application in your device since others wouldn't know how to use it properly?
    - caspianm 10y ago
      Here is a discussion of Intel limiting the code that can run in security subsystems in their processors: https://news.ycombinator.com/item?id=11007060 https://news.ycombinator.com/item?id=11007060 I'm not saying this is acceptable, but it seems to be happening.