63db10d400
- app_net.c: replace bare httpd_req_recv with recv_body_capped/alloc helpers (TCP-safe, full-body reads); add OPTIONS/* CORS preflight handler; bump WS broadcast buffer to 2048; add CORS Allow-Methods - CMakeLists (net_service): add http_parser dep for HTTP_OPTIONS - nfc_engine/pn532_core: add nfc_access_lock/unlock mutex, board-RGB quiet helper, UL type detection, general-status improvements - pn532_transport: minor cleanup - main.c: call board_rgb_led_quiet() at boot to kill onboard LED - sdkconfig.defaults: add board RGB Kconfig defaults - README, docs/LIMITATIONS, docs/PINOUT: expand and correct Made-with: Cursor
1.0 KiB
1.0 KiB
Capabilities & limitations
The PN532 is a hosted NFC controller, not a low-level RF lab instrument. This project exposes PN532 features honestly:
- ISO14443-B: reader support exists with chip-level caveats (anticollision / stack-dependent behavior). No promises of full mobile/PICC coverage.
- Card emulation / TG modes: PN532 firmware supports target commands and this repo now exposes a structured target-mode API, but real-world mimicry still depends on timing, UID size, ATS/general bytes, and reader expectations. Treat it as a controllable subsystem, not magic full-card impersonation.
- Key recovery: on-device “brute force” at Proxmark scale is infeasible. The UI provides dictionary / manual key workflows.
- Signal / RF metrics: diagnostics use PN532 status / timings / retries, not calibrated dBm.
- OTA via UI:
POST /api/otanow performs real HTTPS OTA with the ESP-IDF certificate bundle. For production fleets, add your own release signing, manifest control, and hardware validation gates before broad rollout.