cederom commented on issue #16822: URL: https://github.com/apache/nuttx/issues/16822#issuecomment-3948682257
I think before implementation we could have a discussion to find the best solution and talk if this is really a problem: * In default case there is no password. * Password needs to be enabled by hand. Then user can and usually changes the password. * Any generated password will be visible in the firmware image anyways. It will be encrypted true, but the hash will look the same right? Maybe even at the same offset? So we are back in the same problem :-P * Instead we may work out option that random password is generated using current encryption method on each build. In that case we would have truly random password that would be printed out during build phase or better appended to some file not to be revealed in build logs. Unless the same image is not flashed into multiple devices. And we are back. * Alternatively we may consider some algorithm that will produce different storage hash for the same password. Then every device would be provisioned with different firmware image even if having the same password. * The only sensible solution here that I can see is fully encrypted firmware image with decryption keys stored in the hardware. But this is different story. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
