Support bundle verification with multiple public keys #826
Labels
status:new
New issue, not reviewed by the team yet.
type:feature
Proposal or idea for a new feature or enhancement.
Description
The situation we're facing is as follows:
We have multiple independent MiniApp development teams, and we want each team to use their own unique private key.
This means that when verifying a bundle, we need to pass in the public key of the respective team (which is fetched from the server).
However, when examining the repack source code, we found that the 'verify' function is currently ONLY allowing for a single public key that is hardcoded into the source code, as shown below."
Suggested solution
It would be much better if the verify bundle function could accept an additional public key as a parameter, instead of hardcoding it as it is now, such as:
With this approach, we can have multiple mini-app development teams, each with their own private key for signing their mini-apps. We can authenticate development teams using their keys, allowing them to join the ecosystem or rejecting teams without relying on the main app's private key.
Furthermore, if the main app's private key is lost or compromised, mini-apps created by various development teams can still operate. We have the flexibility to re-sign them whenever needed,(similar Google's Play App Signing approach)
Would you please consider this proposal
Thanks & BestRegard,
Additional context
No response
The text was updated successfully, but these errors were encountered: