Verification Key Constraint Matching for Mobile Security
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile computing platforms lack appropriate limitations on the authorization power of verification keys, which can lead to unauthorized modifications and security compromises, particularly in regulated environments like radio frequency usage.
Innovation Solution
A method and apparatus that receive a verification key with an identifier of the parent key, determine if the constraint portion matches the parent key's constraint portion, and associate the verification key with a specific state update, thereby limiting its authorization power and ensuring secure state transitions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If verification keys are issued with broad authorization power, then parties can efficiently authorize state changes, but security risks increase due to potential unauthorized modifications
Solution Approach 1:
The verification key's authorization power is segmented into specific constraints that limit its scope. Instead of issuing broad authorization, the system divides authorization into discrete, constrained portions tied to specific state updates, parent keys, and usage conditions. This segmentation allows efficient authorization within defined boundaries while preventing unauthorized modifications outside those boundaries.
Solution Approach 2:
Each verification key is assigned local quality through specific constraints that define its precise authorization scope. The constraints portion of the verification key structure enables different keys to have different authorization characteristics tailored to specific purposes, parent keys, or state updates, rather than applying uniform broad authorization to all keys.
2Reliability
If verification keys are constrained with specific limitations, then security is improved by preventing unauthorized modifications, but complexity increases due to additional verification steps
Solution Approach 1:
The constraints are established in advance during verification key generation and issuance. The constraint portion is pre-configured with all necessary limitations, parent key identifiers, and authorization scopes before the key is put into use. This preliminary action eliminates the need for complex runtime verification logic, as the constraints are already embedded in the key structure itself.
Solution Approach 2:
The verification key structure is designed to be self-describing, with the constraint portion containing all necessary information about its authorization limits, parent key relationships, and valid usage contexts. This self-service approach allows the system to verify constraints directly from the key itself without requiring external metadata or complex lookup tables, reducing overall system complexity.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method, an apparatus, and a computer program product for enabling verification key handling is disclosed. Said handling is enabled by receiving a verification key including an identifier of the parent verification key of the verification key (40), wherein the verification key comprises a constraint portion, determining whether the constraint portion of the verification key corresponds to the constraint portion of the parent verification key (41), associating, in case the constraint portion of the verification key corresponds to the constraint portion of the parent verification key, the verification key with a particular state update (43), and storing the verification key associated with the particular state update (44).