The present invention involves systems and methods that allow participants in cryptocurrency networks to exchange cryptocurrency for traditional currency legally and safely without requiring the use of a traditional exchange or online brokerage as a fiduciary. The invention accomplishes this through the use of a decentralized identity verification protocol that allows a service provider to verify the identity of a participant and then publish an identity signature on the participant's cryptocurrency address or addresses. The invention enables full compliance with Country specific customer identification program and anti-money laundering requirements, and maintains the ability to independently satisfy requests for information or data retention requirements if requested by legally authorized parties, but does not require that the participant store the private keys or access controls to their cryptocurrency on an exchange or brokerage service. The invention serves to verify a participant's identity in full compliance with US Bank Secrecy and Patriot Act provisions or similar regulations where identification may be achieved through non-documentary or documentary identity verification procedures. After passing the applicable verification procedure, the service provider stamps the participant's cryptocurrency address with a transaction containing an identity signature. This identity signature within the transaction consists of a public indicator of the participant's Country and subdivision, a compliance level code, an ID type indicator, and an identity hash. The identity hash is created from the digests of cryptographic hash functions where the participant's personal information is used as an input. The service provider signs the transaction with their authorized private key that corresponds to their publicly accessible public key. This serves as a publicly verifiable confirmation that the identity associated with the address in question was validated by the service provider authorized to act on behalf of the regulatory authority. The participant may then purchase and sell cryptographic currency from and to a third party exchange or brokerage service legally and safely when using their verified cryptocurrency address. This is because the third party is able to confirm compliance by openly referencing and verifying the identity verification transaction present on the address. Subsequent transactions where the third party sells or purchases cryptocurrency for the verified participant are similarly stamped with a transaction conforming to the identity verification protocol. This allows the third party interacting with the verified participant's address to observe any regulations limiting the amount or frequency of transactions over a variable period of time. It follows that this address could be used with any third party or participant in the cryptocurrency network that observes the decentralized identity verification protocol, all without requiring the third party or participant to collect and verify personal information redundantly. The ability to verify an identity remotely also eliminates the need for the third party to act as a fiduciary holding the private keys or access controls to the verified address. Lawful requests for information by authorized authorities are served to the service provider as digitally signed transactions that may then be linked to the participant's identity and transactions, allowing the protocol to observe subpoenas or similar lawful requests for information. The encrypted personal information may be held in escrow by the service provider indexed to the verified cryptocurrency address for such purposes. An alternate embodiment would store the encrypted personal information in a decentralized network of other participants, with the information accessible for retrieval using the public key of the verified cryptocurrency address and decryption using the corresponding private key, decentralizing the process entirely except for the identity verification step.

Decentralized identity verification systems and methods

A system for auditing authorized key files associated with secure shell (SSH) servers is disclosed. In an example, the system may include a purpose-built SSH audit server. The SSH audit server may be configured to receive an authorized key file and a list of users. The SSH audit sever may generate and provide unique registration codes for each of the users in the list. The SSH audit server may associate particular users with particular public keys as each of the users accesses the SSH audit server using a public key and inputs a registration code.

Secure shell public key audit system

The invention refers to a procedure for generating a digital identity for a user ( 100 ) of a mobile device ( 10 ), based on a digital certificate generated by a certificate authority. The mobile device ( 10 ) is associated with a first mobile identification number (MSISDN). The user can access an executable application ( 11 ) which is installed either on the mobile device or on a second device that can run the application. The application:
 contains a key container for at least a public key and a private key which are associated with the aforementioned first mobile identification number; is associated with a unique application identifier; and includes connection logic for connecting with a mobile identity server ( 30 ). The procedure consists of a series of stages whereby the user's mobile digital identity is generated from the first mobile identification number (MSISDN), the user's digital certificate, and the unique application identifier. The invention also refers to the digital identity of a user ( 100 ), a procedure for authenticating a user which makes use of said digital identity. And an application ( 11 ) which can be installed in a mobile device ( 10 ) or a second device that is able to run the application, to generate a digital identity for the user ( 100 ) of the mobile device ( 10 ).

Procedure for generating a digital identity of a user of a mobile device, digital identity of the user, and authentication procedure using said digital identity of the user

Various embodiments provide systems and methods for connecting wireless-enabled products to wireless networks. Customer network credentials may be stored in a server along with a customer identifier (“customer ID”) during one-time registration. When a wireless-enabled product is purchased, a product identifier (“product ID”) and the customer's ID are forwarded to the server, which correlates the two identifiers, linking the purchased product to the customer. When the wireless-enabled product is powered on, the product accesses the server via a public network connection, and sends the product ID and a security token to the server. The server uses the product ID and the security token to authenticate the product. Once authenticated, the server uses the correlated customer ID to look up the network credentials for the customer's private network, and provides the network credentials to the wireless-enabled product. The wireless-enabled product then uses the downloaded credentials to access the customer's private network.

Method and system for onboarding wireless-enabled products in a network

A computer program product for secure data storage. The present invention may include completing a registration process by sending, by the client device, a connection request to the server. The present invention may include generating, by the server, an authentication session identification (ID). The present invention may include sending, by the server, a stored salt and the generated authentication session ID to the client device. The present invention may include sending, by the server, the generated authentication session ID, the server encryption key and user data to the third-party device. The present invention may include sending, by the client device, the generated authentication session ID and user data to the third-party device. The present invention may include generating, by the third-party device, a decryption key. The present invention may include determining the user data received by the client device and the decrypted user data received by the server is authenticated.

Secure data storage system

An authentication device may provide an authentication code to a third party device. The third party device may provide a third party service to which a client device has requested access. The authentication device may receive the authentication code from a mobile device that is different from the client device. The authentication device may determine a third party device identifier included in the authentication code. The third party device identifier may identify the third party device that provides the third party service. The authentication device may determine a transaction identifier included in the authentication code. The authentication device may selectively provide the transaction identifier to the third party device, identified by the third party device identifier, to cause the third party device to selectively permit the client device to access the third party service.

Jeffrey R. Wise

Papers

Global authentication service using a global user identifier