Compare commits
2
Commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
e338e2a092 | ||
|
|
1bec7c0a51 |
@@ -1,18 +1,18 @@
|
|||||||
# RED_CRYPTO ver 0.7.3
|
# RED_CRYPTO ver 0.7.3-full
|
||||||
|
|
||||||
## Description
|
## Description
|
||||||
|
|
||||||
Password manager for (almost) any QMK-compatible keyboards.
|
Password manager for (almost) any QMK-compatible keyboards. It is full version of `RED_CRYPTO` lib.
|
||||||
|
|
||||||
There are two versions:
|
There are two versions:
|
||||||
- hard-coded passwords in `keymap.c`, change branch to `hard_coded_storage` or releases
|
- hard-coded passwords in `keymap.c`, change branch to [`hard_coded_storage`](https://github.com/redlineo/red_crypto/tree/hard_coded_storage) or releases
|
||||||
- storing passwords in EEPROM with adding and editing via `RED_MENU`, change branch to `eeprom_storage` or releases
|
- storing passwords in EEPROM with adding and editing via `RED_MENU`, change branch to [`eeprom_storage`](https://github.com/redlineo/red_crypto/tree/eeprom_storage) or releases (YOU ARE HERE)
|
||||||
|
|
||||||
## Alert
|
## Alert
|
||||||
|
|
||||||
> Now red_crypto supports STM32 EEPROM.
|
> Now red_crypto supports STM32 EEPROM.
|
||||||
>
|
>
|
||||||
> Tested on Keychron K9 Pro with STM32L4xx with virtual EEPROM
|
> Tested on Keychron K9 Pro with STM32L432xx with virtual EEPROM
|
||||||
|
|
||||||
See chapter about [Memory issue](#memory-issue) and [Memory usage](#memory-usage).
|
See chapter about [Memory issue](#memory-issue) and [Memory usage](#memory-usage).
|
||||||
I recommend using at the beginning internal FLASH or EEPROM, because you have some resources not to need external memory. Or you can do not change your passwords, if there are very strong one's.
|
I recommend using at the beginning internal FLASH or EEPROM, because you have some resources not to need external memory. Or you can do not change your passwords, if there are very strong one's.
|
||||||
|
|||||||
Reference in new issue
Block a user