Describe the bug

If PX4_CRYPTO is defined and the param SDLOG_ALGORITHM is set 0 (Disabled), the logging does not start due to file not found error. If crypto algorithm is not given the symmetric key is not created and not stored into the beginning of the log file, so the file is not found when log data is tried to be appended after the key data.

To Reproduce

1. Build px4_fmu-v5_cryptotest image and flash it
2. Boot up the device
3. Set param SDLOG_ALGORITHM -> 0
4. Reboot the device
5. command: logger on

Expected behavior

Logging is started without encryption. Afters logging is stopped the log file will containsplain text ulog data.

Screenshot / Media

No response

Flight Log

No response

Software Version

PX4-Autopilot main branch. Bug noticed with commit b765769 (Note! This commit did not break the logging, but it is just one commit with which the bug was detected. The breaking change is this one: 2da944a)

Flight controller

px4_fmu-v5

Vehicle type

None

How are the different components wired up (including port information)

No response

Additional context

No response