smart-car | a pygame interface for the freenove smart car | Game Engine library

It's not necessary to reimplement algorithm to find differences, you can use difflib.ndiff(), just some preparation required. We need to pass to ndiff() only lines which belongs to interface.

We can use generator function which returns interface name and all lines belongs to this interface:

More concretely, what would a CLA of "80" mean?

CLA=80 corresponds to the proprietary class, because "Bit b8 set to 1 indicates the proprietary class". Table in section 5.4.1 specifies interindustry class, i.e. where bit 8 set to 0.

What do the symbols "x" (lowercase) and "-" imply in terms of the value of the bit at that position?

You can treat mark 'x' as wildchar (any value), mark '-' as "bit is not used in this case", and 0 and 1 as exact values for bit place. So, xx-- is just a bit mask. It tells that bit 4 and bit 3 indicate what SM format is used int the command and bit 2 and bit 1 are used for something different .
0x-- can be 00-- or 01--.

Bits 2 and 1 are described with an other line of the table.

PKCS#11 is an API standard. It describes an API for software that wants to use a smart card or other crypto 'device'. It does not describe how a vendor should do anything underneath that API. And, it does not expect you (as the software programmer) to know how to access all the hardware out there.

Your app says "C_Login" because that's PKCS#11. P11 states what C_Login expects, and what the state of the environment should be after that call is made -- it does not tell the vendor how to get to that state, only what end-state is expected, not the path how to get there.

Now: ...multi-platform Python package... Absolutely possible, assuming you had access to EVERY device binary protocol, communications protocol and programming methodology, for everything out there that provides a crypto-card interface.

Every smart-card, HSM, soft-HSM etc that supplies a P11 library knows what your application will ask for, but how it goes about making that object or state available is entirely up to the actual device/pseudo-device. This is why a vendor-specific library is needed -- because the vendor knows the vendor's devices and protocols.

Or you could provide an API standard that defines a standardized way for software to access hardware, making the binary protocol, communications protocol and programming methodology abstract... ie, you'd be recreating PKCS#11, but one specific to Python.

Faster to use the Py lib that talks PKCS#11, and connects to any of the P11 vendor-provided libraries, to talk to that vendor's equipment.

The problem that Django handles form elements based on name attribute and not the id attribute so this means you need to change name per request and on the view side you loop on all keys in request.POST like

Please look at official documentation from postman to get their recommendation on which image to use that is stable.

This is an error coming from postman's "Tests" tab, we have put some code in there to extract data from response body in order to set environment variables. If you are getting a 200 OK response with your devices showing you can simply ignore this error. You can also comment out the code in "Test" tab and you will not see the error for that call again. Please periodically check here for new updates to the collection that will fix these issues in the future.

Please revisit this page and reload. We have updated said page to include the missing files that are required.

https://developer.mimik.com/smart-car-use-case/

Please make sure that the deployment of all microservices are successful. You can verify deployment by running GET http://{{YOUR_IP_ADDRESS}}:{{PORT}}/mcm/v1/images (or [B4-1] in Postman collection) and looking at the response. Your response should contain the names of all the required microservices (miot-v1, msuperdrive-v1 and mbeam-v1). If the microservices are missing; you will need to deploy them again.

NOTE: edgeengine must be running at all times in order to complete everything correctly

I think your problem is that the MFRC522 RFID reader is a very basic/old design and really only supports MIFARE type cards (which are the non standardised original card format). While Host Card emulation uses ISO/IEC 14443A (mostly) as a base it uses other higher level protocols to emulate a NFC Type 4 card which is not supported by that card reader.

If you look at an Arduino library for the reader https://github.com/miguelbalboa/rfid#troubleshooting

My mobile phone doesn't recognize the MFRC522 or my MFRC522 can't read data from other MFRC522
Card simulation is not supported.
Communication with mobile phones is not supported.
Peer to peer communication is not supported.

As the library suggest if you want more feature use a PN532 based modules instead.

If you look at an Arduino library for the PN532 https://github.com/Seeed-Studio/PN532#Features

Communicate with android 4.0+(Lists of devices supported)