secplus VS flipperzero-firmware

For Chamberlain brands [0] there is some research that shows that their rolling code system (Security+ and Security+ 2.0) is quite easy to decode/decrypt [1]. This feature is supported in the flipper firmware, but is restricted (you can't create a custom remote, only clone is supported) without custom firmware. However, I'm sure you could decode a raw capture file if needed in a pinch.

[0] https://chamberlaingroup.com/our-brands

[1] https://github.com/argilo/secplus

A gentle reminder that the Security+ and Security+ 2.0 RF protocols have been reverse engineered (https://github.com/argilo/secplus). While they are not the most secure thing in the world, you can build a custom RF transmitter (remote) that is network connected.

Having done some research into Chamberlain's products, I don't recommend anyone to use them if they have the choice.

This is not an attempt to break the RF Security+ encryption that this, and other garage doors utilize. That has already happened. https://github.com/argilo/secplus

Here is the rolling code project: https://github.com/argilo/secplus

Man I got really excited thinking this was about the Flipper Zero device https://flipperzero.one/

We use littlefs in Flipper Zero's firmware[1] for storage in leftover flash space after the main firmware image. Flipper implements a virtual FS, where both external SD card and internal storage have own mount points. SD card is used for storing apps and user-created data, and internal littlefs contains persistent data like BLE pairing, system services configs and such.

We never had any issues with littlefs - however, it cannot be easily repartitioned when amount of available leftover space changes with firmware updates. So on installing an update, it gets fully backed up to SD card, reformatted and later restored.

1- https://github.com/flipperdevices/flipperzero-firmware/blob/...

Issue opened.

It is used in FlipperZero with FreeRTOS to handle the data structure.