“nfc”

Yes, I configured the NFC capability. Here is my entitlements file: com.apple.developer.nfc.readersession.formats NDEF TAG And my info.plist: com.apple.developer.nfc.readersession.iso7816.select-identifiers 315449432E494341 NFCReaderUsageDescription NFC reason

macOS does have a setting to disable debugging: https://developer.apple.com/library/archive/qa/qa1361/_index.html (and which itself can be circumvented) and does offer hardened run-time: https://developer.apple.com/documentation/security/hardened_runtime If you're already using that and want more... There are papers and write-ups on reverse-engineering and anti-reverse-engineeringposted around the 'net. Some folks will use a licensing dongle, whether USB or NFC or otherwise. Some vendors will use a support-based licensing scheme, and which requires periodic contact with servers you control. If the crack is loading exploit code at run-time (and somehow the hardened run-time isn't an option or isn't working for your case), you could submit known-bad license keys from various spots in the code (after the first real check, and fail (and preferably failing well after the good and bad checks, and preferably failing with an obscure run-time error selected from a list of reserved-for-cracks error codes, and

I see very limited documentation on how exactly CryptoTokenKit can detect the readers and fetch certificates from smart card. That’s because detecting the reader and fetching the certificates is done by the CTK appex, and how it does that is entirely up to it. Consider my YubiKey 5 NFC. It has multiple hardware interfaces, including USB and NFC. If I plug it into the USB-C port on my iPad, using a standard USB to USB-C adapter, it Just Works™. The token supports PIV and iOS has built-in PIV support. OTOH, if I try to use it over NFC, I must install Yubico’s app so that its CTK appex can route the request to the token’s NFC interface. If we want to fetch the certificates from smart cards connected via Bluetooth/lighting port, do we have to write an CryptoTokenKitExtension app? That depends on the token’s vendor: If the vendor has already written a CTK appex, your app can talk to the token that way. This is exactly what happens when I use my YubiKey over NFC. If not,

Does Apple support lighting port readers? Depends on what you mean by “support”. The iOS security infrastructure is able to work with smart card readers connected via Lightning, USB, NFC, and others. The exact mechanics of how that works, and who supports it if it fails!, depends on the connection type. What is the need of crypto token kit extension if we are able to list the certificates from key chain just by adding com.apple.token in the entitlements file. The built-in infrastructure can work the SE and with PIV hardware token. If your hardware token needs custom support, or you want to create a virtual token that’s not backed by directly connected hardware, you create a CTK appex. For example, my Yubikey 5Ci has NFC support. That only works if Yubico’s app is installed, because the app contains the CTK appex that bridges to NFC [1]. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Via a very convoluted path,

I have a field RFID Detector, decided to try it out on my phone and my friend’s phone. I put the detector to my phone, and it was blinking, so the nfc was trying to find a tag, but the light was very dim. Tried it on my friend’s phone. Light was brighter than ever, meaning a really high field of nfc. Maybe it’s a power issues, and there isn’t enough power going to the nfc chip?