# US 2022/0045848 A1 · Password security hardware module

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2022/0045848 A1
- Document ID: US20220045848A1
- Status: Published application
- Kind: A1
- Application number: 16/988,583
- Filed: 2020-08-07
- Published: 2022-02-10
- Earliest claimed: 2020-08-07
- Assignees: Charter Communications Operating, LLC
- Applicants: Charter Communications Operating, LLC
- Inventors: Robert Hulshof
- Web page: https://patentgrep.com/patent/US20220045848A1

## CPC

- H04L 9/085: {Secret sharing or secret splitting, e.g. threshold schemes}
- G06F 12/1408: {by using cryptography (for digital transmission H04L9/00)}
- G06F 21/31: User authentication
- G06F 21/602: {Providing cryptographic facilities or services}
- H04L 9/0822: {using key encryption key}
- H04L 9/0836: {using tree structure or hierarchical structure}
- H04L 9/0861: {Generation of secret information including derivation or calculation of cryptographic keys or passwords}
- H04L 9/0891: {Revocation or update of secret information, e.g. encryption key update or rekeying}
- H04L 9/3226: {using a predetermined code, e.g. password, passphrase or PIN (network architectures or network communication protocols for supporting authentication of entities using passwords in a packet data network H04L63/083)}
- H04L 9/3236: {using cryptographic hash functions}
- H04L 9/3271: {using challenge-response}
- H04L 2209/127: Trusted platform modules [TPM]
- H04L 2209/16: Obfuscation or hiding, e.g. involving white box
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Establish a secure connection from a device to a server by, at the device: sending a shared secret request (SSRq) and an obfuscated secret value of the device to the server, wherein the SSRq is encrypted by a symmetric rolling key known to the device and to a trusted authority but not known to the server and the SSRq incorporates a symmetric key for decrypting the device's obfuscated secret value; receiving a shared secret response (SSRs) and an obfuscated secret value of the server, wherein the device's symmetric rolling key encrypts the SSRs and the SSRs incorporates a symmetric server obfuscation key for decrypting the server's obfuscated secret value; calculating a shared secret by hashing a concatenation of the device's secret value and the server's secret value; generating a symmetric session key based on the shared secret; and establishing the secure connection using the symmetric session key.

## Claims

### Claim 1

A method for securely entering an access code using an insecure device, the method comprising:
generating a random code;
displaying the random code at a display;
selecting a digit of the random code in response to a first input from the insecure device;
adjusting the selected digit of the random code in response to a second input from the insecure device; and
repeating the steps of selecting and adjusting digits of the random code until the incremented digits of the random code match all digits of the access code.

### Claim 2 (depends on 1)

The method of claim 1 wherein the display is a display of the insecure device.

### Claim 3 (depends on 1)

The method of claim 1 wherein the access code is a code of a secure device that is connected in communication with the insecure device.

### Claim 4 (depends on 3)

The method of claim 3 wherein the display is a display of the secure device.

### Claim 5 (depends on 3)

The method of claim 3 wherein the secure device performs the steps of generating, displaying, selecting, and incrementing.

### Claim 6 (depends on 1)

The method of claim 1 further comprising denying access to a memory of a secure device in response to the incremented digits of the random code not matching all digits of the access code.

### Claim 7 (depends on 1)

The method of claim 1 further comprising granting access to a memory of a secure device in response to the incremented digits of the random code matching all digits of the access code.

### Claim 8 (depends on 1)

The method of claim 1 further comprising, in response to selecting a subsequent digit of the random code has been selected, prohibiting re-selection of a previous digit.

### Claim 9

A secure device comprising:
a main processor;
a first interface that is adapted to connect an external visual display in communication with the main processor;
a second interface that is adapted to connect a keyboard in communication with the main processor;
a third interface that is adapted to connect an insecure device in communication with the main processor;
a secure microprocessor that is connected in communication with the main processor, wherein the secure microprocessor includes a tamper-proof central processing unit (CPU) that is adapted to provide a password manager module and includes a tamper-proof memory that embodies a plurality of passwords and computer executable instructions for adapting the tamper-proof CPU to provide the password manager module; and
an internal visual display connected in communication with the main processor,
wherein the main processor is configured by the computer executable instructions to:
securely enter a server password from the keyboard to the password manager module; and
securely deliver the server password to the server via an insecure device.

### Claim 10 (depends on 9)

The secure device of claim 9 wherein securely entering the server password comprises:
displaying a user interface to the external visual display via the first interface;
receiving a password manager password from the keyboard via the second interface;
enabling the password manager module in response to the password manager password;
displaying a password entry dialog at the user interface;
receiving the server password and a server password name from the keyboard via the second interface; and
storing the server password and the server password name in the password manager module.

### Claim 11 (depends on 9)

The secure device of claim 9 wherein securely delivering the server password comprises establishing a secure connection with the server via the insecure device.

### Claim 12 (depends on 11)

The secure device of claim 11 wherein establishing a secure connection comprises:
sending a shared secret request and an obfuscated secret value of the secure device from the secure device to the server via the insecure device, wherein the shared secret request is encrypted by a rolling key known to the secure device and to a trusted authority but not known to the insecure device or to the server and the shared secret request incorporates a secure device obfuscation key for decrypting the secure device's obfuscated secret value;
receiving a shared secret response and an obfuscated secret value of the server from the server via the insecure device, wherein the shared secret response is encrypted by the secure device's rolling key and the shared secret response incorporates a server obfuscation key for decrypting the server's obfuscated secret value;
calculating a shared secret of the secure device and the server by concatenating the secure device's secret value and the server's secret value and hashing the result;
generating a session key for the secure connection based on the shared secret; and
establishing the secure connection using the session key to encrypt all traffic between the secure device and the server via the insecure device.

### Claim 13 (depends on 11)

The secure device of claim 11 wherein securely delivering the server password comprises:
receiving the server password from the keyboard via the second interface; and
sending the server password to the server via the secure connection over the insecure device.

### Claim 14 (depends on 9)

The secure device of claim 9 wherein securely delivering the server password comprises:
enabling the password manager module in response to receipt of a server nonce via the insecure device;
generating a random code;
displaying the random code via a user interface at a display of the insecure device;
selecting a digit of the random code in response to a first input from the insecure device;
adjusting the selected digit of the random code in response to a second input from the insecure device;
repeating the steps of selecting and adjusting digits of the random code until the incremented digits of the random code match all digits of an access code of the password manager module;
displaying a password manager module interface in response to matching all digits of the access code, wherein the password manager module interface displays one or more password names;
selecting a password name in response to a third input from the insecure device; and
retrieving the server password from the password manager module in response to selecting the password name.

### Claim 15 (depends on 14)

The secure device of claim 14 wherein securely delivering the server password to the server further comprises:
hashing a hash of the server password with the server nonce; and
sending the hash of the hash to the server via the insecure device.

### Claim 16 (depends on 9)

The secure device of claim 9 wherein securely delivering the server password comprises:
receiving the server password from the keyboard via the second interface;
hashing the server password with a server nonce received from the server; and
sending the hashed server password to the server via the insecure device.

### Claim 17

A method for establishing a secure connection from a device to a server, the method comprising, at the device:
sending a first shared secret request and an obfuscated secret value of the device from the device to the server, wherein the first shared secret request is encrypted by a symmetric rolling key known to the device and to a trusted authority but not known to the server and the first shared secret request incorporates a symmetric device obfuscation key for decrypting the device's obfuscated secret value;
receiving a first shared secret response and an obfuscated secret value of the server from the server, wherein the first shared secret response is encrypted by the device's symmetric rolling key and the first shared secret response incorporates a symmetric server obfuscation key for decrypting the server's obfuscated secret value;
calculating a shared secret of the device and the server by concatenating the device's secret value and the server's secret value and hashing the result;
generating a symmetric session key for the secure connection based on the shared secret; and
establishing the secure connection using the symmetric session key to encrypt all traffic between the device and the server.

### Claim 18 (depends on 17)

The method of claim 17 further comprising, at the trusted authority:
receiving a combined shared secret request from the server, wherein the combined shared secret request incorporates the first shared secret request from the secure device and a second shared secret request from the server;
obtaining the first shared secret request and the server obfuscation key by decrypting the combined shared secret request using a rolling key shared by the server and the trusted authority but not known to the secure device or to the insecure device;
obtaining the secure device obfuscation key by decrypting the first shared secret request using the secure device's rolling key;
forming the first shared secret response by encrypting the server obfuscation key with the secure device's rolling key;
forming a second shared secret response by encrypting the secure device obfuscation key with the server's rolling key; and
sending the first shared secret response and the second shared secret response to the server.

### Claim 19 (depends on 18)

The method of claim 18 further comprising, at the server:
receiving the first shared secret request from the secure device;
forming the combined shared secret request by concatenating the first shared secret request with the server obfuscation key and encrypting the concatenation using the server's rolling key;
sending the combined shared secret request to the trusted authority;
receiving the first shared secret response and the second shared secret response from the trusted authority;
obtaining the shared device obfuscation key by decrypting the second shared secret response;
obtaining the secure device's secret value by decrypting the secure device's obfuscated secret value using the shared device obfuscation key; and
sending the first shared secret response and the server's obfuscated secret value to the secure device.

### Claim 20 (depends on 17)

The method of claim 17 further comprising securely transferring data from the device to the server using the secure connection.

### Claim 21

A method for password-based authentication of a client to a server, the method comprising:
the server sending a nonce to the client;
the client generating a cryptographically secure hash from the nonce and a secure hashed version of a client password;
the client sending the cryptographically secure hash to the server;
the server, which has a copy of the secure hashed version of the client password, verifying that the cryptographically secure hash can only be generated from the secure hashed version of the password and the nonce; and
the server granting access to the client in response to the verifying step.
