at-cryptoauth
| Crates.io | at-cryptoauth |
| lib.rs | at-cryptoauth |
| version | 0.4.0 |
| source | src |
| created_at | 2021-01-26 13:41:11.668017 |
| updated_at | 2021-12-30 08:16:29.843564 |
| description | Driver for ATECC608 Crypto Authentication secure elements |
| homepage | |
| repository | https://github.com/BlackbirdHQ/at-cryptoauth-rs |
| max_upload_size | |
| id | 346872 |
| size | 128,755 |
hardware-development (github:blackbirdhq:hardware-development)
documentation
README
ATECCx08 CryptoAuth
Existing works
The chip vendor open-sources CryptoAuthLib, the official driver library. It is firmly coupled with the Harmony framework and well suited for SAM families.
Rusty_CryptoAuthLib is an implementation in Rust that maintains API compatibility with the CryptoAuthlib.
Limitations
This driver only supports ATECC608 over an I2C bus and on its host side, STM32-L4 family or RaspberryPi. As a matter of fact, tests have been running only on these combinations.
By design, the driver does not conform to the vendor’s authentic library implementation. Instead, it provides with just a tiny subset of APIs, which is necessary and sufficient for implementing traits proposed by Rust Crypto.
Prior to finalize the device, a user has to plan how to deploy or generate keys and which API operates on them. The driver imposes a fixed usage model called TNG-TLS. At the cost of the users’ degree of freedom, the limited scope helps them provision the device.