Storage Device Authentication Without Master Private Key
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing storage devices, such as SSDs, face challenges in authenticating debugging devices in environments where communication with an authentication server is impossible, particularly when sensitive data is involved.
Innovation Solution
The proposed solution involves a storage device equipped with an authentication device that can authenticate debugging devices without requiring a master private key. This is achieved through a process where the authentication device receives a certificate and public keys from the debugger, verifies them, and outputs a debugging enable signal, allowing the processor to perform debugging operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If authentication server communication is required for debugging authentication, then authentication security is improved, but system adaptability to offline environments deteriorates
Solution Approach 1:
The authentication device pre-stores verification data (hash values of public keys and product information) in its memory before offline debugging is needed. This preliminary storage of authentication credentials enables the device to perform security verification independently without real-time server communication, resolving the contradiction between security and offline adaptability
2Reliability
If master private key is used for authentication, then authentication authority is improved, but security risk deteriorates
Solution Approach 1:
The invention extracts and removes the master private key from the authentication process. Instead of using the master private key directly, the system uses only public keys and their hash values for verification. This extraction of the sensitive private key eliminates the security risk while maintaining authentication authority through the remaining public key infrastructure
Solution Approach 2:
The invention introduces hash values of public keys as an intermediary verification mechanism. Rather than directly using the master private key, the system verifies debuggers through hash value comparison. This intermediary approach maintains authentication authority while eliminating the need to handle or transmit sensitive private keys
3Reliability
If multiple verification steps are performed for debugging authentication, then authentication reliability is improved, but device complexity deteriorates
Solution Approach 1:
The invention merges multiple verification operations into a unified hash value comparison process. The authentication device combines verification of public key authenticity and product information validation into a single hash value matching operation. This merging maintains comprehensive verification reliability while simplifying the overall authentication process structure
Data Source
AI summary
A storage device includes: authentication device for receiving a certificate generated based on a first private key that corresponds to a first public key, the first public key, and a second public key from a debugging device, authenticating the first public key, authenticating the second public key when the authentication of the first public key is successful, and outputting a debugging enable signal when the authentication of the second public key is successful; a processor for receiving a debugging signal from the debugging device in response to the debugging enable signal, and performing debugging based on the debugging signal.