The current baking app, unlike the legacy app, has the screensaver enabled, which results in the ledger not signing anymore after a certain time.
During testing, disabling the screen saver from the settings resulted in the ledger prompting for the pin after a period of time, also locking the ledger.
We know that when the ledger is locked or in screensaver mode the derivation results in an error, but it's possible that other SDK functions behave similarly.
A branch of the legacy app has a patch to bypass this limitation, by caching the generated keypair, which has raised security concerns internally, and the effectiveness of this is to be tested as well.
Therefore, we need to investigate how to effectively and safely allow the screen to turn off to avoid burn-in, whilst maintaining the app operational so the ledger can be left unattended.
The current baking app, unlike the legacy app, has the screensaver enabled, which results in the ledger not signing anymore after a certain time.
During testing, disabling the screen saver from the settings resulted in the ledger prompting for the pin after a period of time, also locking the ledger.
We know that when the ledger is locked or in screensaver mode the derivation results in an error, but it's possible that other SDK functions behave similarly.
A branch of the legacy app has a patch to bypass this limitation, by caching the generated keypair, which has raised security concerns internally, and the effectiveness of this is to be tested as well.
Therefore, we need to investigate how to effectively and safely allow the screen to turn off to avoid burn-in, whilst maintaining the app operational so the ledger can be left unattended.
:link: zboto Link