[英]Mifare Plus vs Mifare DESfire (Android)
Apart from what is shown in the NXP websites regarding mifare plus and mifare desfire, considering the following factors: 除了在NXP网站上显示的有关mifare plus和mifare desfire的内容外,请考虑以下因素:
Thanks 谢谢
MIFARE Plus is really meant as an upgrade for existing MIFARE Classic-based systems. MIFARE Plus实际上是对现有的基于MIFARE Classic的系统的升级。 It has a mode which is backward compatible with MIAFRE CLassic. 它具有与MIAFRE CLassic向后兼容的模式。 It has the same fixed memory structure as MIFARE Classic: sectors with 3 blocks of 16 bytes of data and a block for the 2 access control keys. 它具有与MIFARE Classic相同的固定内存结构:扇区包含3个16字节数据块,以及2个访问控制密钥的块。 It is not ISO 14443-4 compliant. 它不符合ISO 14443-4。
MIFARE DESFire has a flexible memory structure: up to 28 "applications" (a kind op directories) with up to 32 files each. MIFARE DESFire具有灵活的内存结构:最多28个“应用程序”(一种op目录),每个最多32个文件。 Access control is very flexible, too. 访问控制也非常灵活。 It is ISO 14443-4 compliant and it can communicate in an ISO 7816-4 compliant mode. 它符合ISO 14443-4,并且可以以符合ISO 7816-4的模式进行通信。 It can be configured as an NFC Forum Type 4 Tag, so that compliant systems (such as Android devices with NFC) will automatically read out the NDEF message. 可以将其配置为NFC论坛4类标签,以便兼容的系统(例如具有NFC的Android设备)将自动读出NDEF消息。 It is used in some payment systems. 它在某些支付系统中使用。
EDIT: 编辑:
The 2 products strive for somewhat different security goals, I would say. 我要说的是,这两种产品都在争取一些不同的安全目标。 DESFire offers AES and 3DES for maximum flexibility, with encrypted, MACed or plain communication: your choice. DESFire提供AES和3DES,可通过加密,MAC或普通通信提供最大的灵活性:您的选择。 Each application and file can be configured with its own access control keys. 每个应用程序和文件都可以配置有自己的访问控制键。 While MIFARE Plus aims to improve the security of MIFARE Classic, but its functionality is for the rest very similar to it. 虽然MIFARE Plus旨在提高MIFARE Classic的安全性,但其余功能与其非常相似。 In addition, MIFARE Plus has a proximity check feature, while DESFire has no such thing. 此外,MIFARE Plus具有接近度检查功能,而DESFire没有。
They both support the same reading speeds (check the specs!). 它们都支持相同的读取速度(请检查规格!)。 They will both perform OK on a ferrite layer and an antenna size of 35mm sounds OK. 他们都将在铁氧体层上执行“确定”,并且天线尺寸为35mm听起来不错。 I have such DESfire tags, with and without ferrite, that work fine with an Android phone. 我有带或不带铁氧体的DESfire标签,可以在Android手机上正常工作。
For ease of development, my preference is with DESFire. 为了便于开发,我更喜欢使用DESFire。 It is more flexible, both in communication options and data storage configuration. 在通信选项和数据存储配置上,它都更加灵活。 If you have an Android device with NFC capability, you can even configure DESFire as Type 4 Tag, which means that Android will read out any NDEF data automatically and deliver it to your app in an intent. 如果您拥有具有NFC功能的Android设备,则甚至可以将DESFire配置为Type 4 Tag,这意味着Android将自动读取所有NDEF数据,并有意将其发送到您的应用程序。
You seem to have an awful lot of questions here, some of which may not actually be relevant, but here goes: 您似乎在这里有很多问题,其中一些可能实际上并不相关,但是这里有:
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.