mirror of
https://github.com/RfidResearchGroup/proxmark3.git
synced 2026-11-14 09:38:50 +00:00
iceman1001andClaude Opus 5
94e842fb68
configure_environment.sh only modelled the USB serial link, so on a PM5 driven over wifi or BLE it printed "plug the Proxmark3 in" and checked nothing that applied. The udev rule and dialout membership stay flagged exactly as before, since every Proxmark gets flashed over USB sooner or later; what was missing was everything else: - the bluetooth group, which 'make accessrights' already adds when the group exists, and which 'pm3 -p bt:' / 'ble:' need. A warning on PM5 or BTADDON, a note elsewhere so a plain PM3 build stays quiet. - cap_net_raw on an installed client. ble_resolve_name() opens a raw HCI socket, so without it 'pm3 -p ble:<name>' needs sudo while 'ble:<MAC>' does not; client/Makefile grants it on install unless SKIP_SETCAP=1. - an absent /dev/ttyACM* no longer reads as an absent Proxmark. Adds client/requirements.txt, since nothing listed the packages the scripts in client/ import: bleak for the BLE roles of pm5_ble_bridge.py (lazy import, the native ble:<MAC> and tcp: transports and the --relay role do not need it), and Unidecode and jq for the two maintenance scrapers. The bleak floor is 0.19 because the API the bridge uses is present in 0.19.5, 0.22.3 and 3.1.0 alike. --extras now checks it too. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
