The best thing would be if some forks got merged into pm3-master. Its the main reason why I started my fork, with all kinds of stuff, that never got into pm3. The stuff in my fork usually gets in to pm3 master after some months. Thats voluntary open source development in a nutshell. It is a different discussion.
Back to apple pay instead. Which modell supports it? iphone 6?
]]>You can atleast emulate Mifare Classic / desfire tags and apple pay must support crypto1, des, 3des, aes support.. cool.
All of a sudden I want to jailbreak... or at least try coding an app...
]]> UID : 08 eb 84 xx
ATQA : 00 04
SAK : 20 [1]
TYPE : NXP MIFARE DESFire 4k | DESFire EV1 2k/4k/8k | Plus 2k/4k SL3 | JCOP 31/41
ATS : 05 78 80 70 02 a5 46
- TL : length is 5 bytes
- T0 : TA1 is present, TB1 is present, TC1 is present, FSCI is 8 (FSC = 256)
- TA1 : different divisors are NOT supported, DR: [], DS: []
- TB1 : SFGI = 0 (SFGT = (not needed) 0/fc), FWI = 7 (FWT = 524288/fc)
- TC1 : NAD is NOT supported, CID is supported
Answers to chinese magic backdoor commands: NO
proxmark3> hf 14a read
UID : 08 4f cb xx
ATQA : 00 04
SAK : 20 [1]
TYPE : NXP MIFARE DESFire 4k | DESFire EV1 2k/4k/8k | Plus 2k/4k SL3 | JCOP 31/41
ATS : 05 78 80 70 02 a5 46
- TL : length is 5 bytes
- T0 : TA1 is present, TB1 is present, TC1 is present, FSCI is 8 (FSC = 256)
- TA1 : different divisors are NOT supported, DR: [], DS: []
- TB1 : SFGI = 0 (SFGT = (not needed) 0/fc), FWI = 7 (FWT = 524288/fc)
- TC1 : NAD is NOT supported, CID is supported
Answers to chinese magic backdoor commands: NO
For security reason, I have eliminated last two UID bits
It seems that, apple pay simulate uids randomly, and the uid begins with 08
So my question is, is it possible that, we can control the uid generation, so our apple pay could be any kind of mifare card, it is useful for many purpose, we could migrate our M1 cards into apple
]]>