RFID Guardian Sub-Projects
From RFID Guardian
This is a Museum page
RFID Guardian Overview:
- RFID Guardian Security Protocols
- RFID Guardian ACL Testing
- ACL regression suite for 14443-A The current ACL tests are for 15693. Now that ACL'ing for 14443-A is being implemented, we need tests for that protocol.
- Extended ACL testing The current ACL tests treat the ACL inference engine as a black box. Examination of the algorithms and implementation of the ACL inference engine will undoubtedly reveal a number of very useful unit tests.
- Software documentation The documentation status currently is patchy. The public API is fully Doxygen-ed, but we sorely need a high-level overview, and in-depth documentation of nontrivial modules.
- Global regression test suite A regression test suite for all of the software is a necessary tool for any further development. Anybody who adds or modifies anything can convince themselves that nothing is broken. Ideally, any addition or modification would validate one or a few unit tests. The regression test suite must be split into parts that can be run on the simulators and parts that require running on the Guardian hardware.
RFID Guardian - Extending the OS and devices
- Add USB slave
- Add USB host We might want to connect a USB disk to RF40
- Add USB OTG
- BlueTooth stack in software Currently, the BlueTooth stack runs on a smart BlueTooth module. Can we switch to a dumb BlueTooth module and run the stack in software?
- BlueTooth protocols Currently, we only use BlueTooth serial line emulation. We might want more modules, e.g. object transfer. But, if we have Ethernet, will we really need this?
- LCD and Touchscreen RF40 will have a different LCD and touchscreen than our current prototype. We need to write drivers for it.
- Graphics library for LCD We need to port a graphics (widget) library like Nano-X. There is a port of Nano-X to eCos. We need to check its status.
- Drivers for frequencies other than 13.56MHz With the advent of RFA40, we will support lower and higher RF bands. We need device drivers for that. The strategy will be to implement the stack in software, then extend the simulator to understand that protocol, debug it; then write a device driver for the Guardian, and test in vivo.
- I2C It's called TWI by BlackFin. We don't know yet what this will be needed for.
- I2S We don't know yet what this will be needed for.
- Sound devices We don't know yet what this will be needed for.
- Smart memory modules RF40 will have hardware support for MMC/SD.
RFID Guardian - Extending the Core Software
- ACL for MiFare Currently, the ACL speaks 15693 and base 14443-A only. We need to extend its input grammar to understand at least some MiFare dialects.
- Integrate Crapto We integrated Crapto, a software re-engineering of the MiFare Classic cryptography, but the attacks need to be accessible from the User Interface. We need to implement one or more tag-only attacks, as in Courtois.
- Java on the Guardian Can we port a lean JVM to the Guardian, like mika? This is an open-source JVM targeted to micro devices. Mark: eCos has no process notion, although it has threads. The BlackFin has no address translation, although it has address protection. Is this sufficient to implement a sandbox? Do we need sandboxing of MidLets?
- GUI on the LCD/touchscreen The current GUI implementation runs on a smartphone. It is implemented in J2ME (Java Micro Edition), and uses serial-line BlueTooth to communicate with the Guardian. We need something comparable on the Guardian itself. Can the smartphone GUI be ported?
RFID Guardian - Extending the High Level Functionality
RFID Guardian - Beyond the Current Platform
- Port uCLinux to RFB40 There is a thriving uCLinux community around the BlackFin. A port of uCLinux to our hardware may extend the user base a lot.
Website and Project Management
