loadApp module returns Invalid Status 6986 when using --signature
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
Research direction
Start with the CLI handling for --signature and compare it with the one-step --signApp --signPrivateKey path. Reproduce the separate signing and loading commands from the report, then verify that the provided application signature loads without Invalid Status 6986 while preserving the genuine-application check.
Written by the indexing model from the issue text.
Description
So i have generated a new key pair with genCAPair and load it with setupCustomCA. All good. I generate a signature for the app with
loadApp --offline --signApp --signPrivateKey with the private key returned from genCAPair.
After this i try to load the app with loadApp. It works and loads if i do not specify anything for the --signature flag. It loads and gives the expected not genuine warning. However if i attempt to provide the app signature with the --signature flag, the load fails and returns an error of "Invalid Status 6986".
However, if i sign and load the app in one step with
loadApp --signApp --signPrivateKey
it will sign it and load it and no error is returned and the not genuine warning is no longer present.
So to summarise, I can get the desired behaviour of loading a signed application on a custom CA by specifying
loadApp --signApp --signPrivateKey
but i get an invalid status error 6986 if i attempt to load a signature generated in a seperate step with
loadApp --offline --signApp --signPrivateKey <private_key>
loadApp --signature <app_signature>
- Dominant language
- Python
- Stars
- 125
- Forks
- 75
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from LedgerHQ/blue-loader-python
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
LedgerHQ/blue-loader-python#130 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
LedgerHQ/blue-loader-python#111 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
LedgerHQ/blue-loader-python#98 · 3 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
LedgerHQ/blue-loader-python#96 · 4 comments · 3 reactions ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
LedgerHQ/blue-loader-python#83 · 1 comment ·
All issues in LedgerHQ/blue-loader-python
Similar issues
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100