WO2024072911A1 - Sécurisation de cryptoportefeuilles d'extension de navigateur à l'aide d'une clé électronique matérielle - Google Patents

Sécurisation de cryptoportefeuilles d'extension de navigateur à l'aide d'une clé électronique matérielle Download PDF

Info

Publication number
WO2024072911A1
WO2024072911A1 PCT/US2023/033897 US2023033897W WO2024072911A1 WO 2024072911 A1 WO2024072911 A1 WO 2024072911A1 US 2023033897 W US2023033897 W US 2023033897W WO 2024072911 A1 WO2024072911 A1 WO 2024072911A1
Authority
WO
WIPO (PCT)
Prior art keywords
wallet
dongle
browser extension
communication interface
hardware
Prior art date
Application number
PCT/US2023/033897
Other languages
English (en)
Inventor
Nabil Wasily
Michael Atef Ayoub
Original Assignee
Thirdwayv, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Thirdwayv, Inc. filed Critical Thirdwayv, Inc.
Publication of WO2024072911A1 publication Critical patent/WO2024072911A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
    • G06F21/12—Protecting executable software
    • G06F21/121—Restricting unauthorised execution of programs
    • G06F21/123—Restricting unauthorised execution of programs by using dedicated hardware, e.g. dongles, smart cards, cryptographic processors, global positioning systems [GPS] devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3247—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving digital signatures
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q2220/00—Business processing using cryptography
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
    • H04L2209/56—Financial cryptography, e.g. electronic payment or e-cash

Definitions

  • the present invention is directed to cryptowallets, and more specifically, the present disclosure is directed to secure hardware for use with browser extension cryptowallets.
  • Cryptowallets are used to generate and store the cryptographic keys required for performing cryptocurrency transactions.
  • the private keys of a cryptowallet are usually generated via a deterministic hierarchical scheme based on one master secret, called the seed value.
  • a private key and/or a wallet personalidentification-number (PIN) code are also important to maintain securely. If the seed value, private key, and/or wallet PIN code are leaked or compromised, a hacker may gain control of the cryptowallet and/or initiate unwanted transactions.
  • PIN personalidentification-number
  • a hardware wallet dongle may be for a secure browser extension cryptowallet system for securing cryptocurrency transactions in a browser extension wallet.
  • the hardware dongle may include a secure element configured to protect a private key of a user.
  • the hardware dongle may include a first communication interface to connect the hardware wallet dongle in electronic communication with a browsing device running the browser extension wallet.
  • the hardware dongle may include a second communication interface to connect the hardware wallet dongle in electronic communication with an authentication device.
  • the first communication interface and the second communication interface may both be connected to the secure element.
  • the secure element may sign a transaction and transmit the signed transaction to the first communication interface for provision to the browser extension wallet in response to a first authentication message from the authentication device being received by the second communication interface and verified by the secure element as authentic.
  • the authentication device is a smartphone.
  • the first communication interface is a wired interface.
  • the wired interface may be a Universal Serial Bus interface.
  • the second communication interface may be a wireless interface.
  • the hardware wallet dongle does not include a screen display.
  • the hardware wallet dongle includes no human-readable interface.
  • the first authentication message is a confirmation of a user identity by at least one biometric sensor.
  • a secure browser extension cryptowallet system may be for securing cryptocurrency transactions in a browser extension wallet.
  • the system may include a hardware wallet dongle.
  • the hardware wallet dongle may be for a secure browser extension cryptowallet system for securing cryptocurrency transactions in a browser extension wallet.
  • the hardware wallet dongle may include a secure element configured to protect a private key of a user.
  • the hardware wallet dongle may include a first communication interface to connect the hardware wallet dongle in electronic communication with a browsing device running the browser extension wallet.
  • the hardware wallet dongle may include a second communication interface to connect the hardware wallet dongle in electronic communication with an authentication device. The first communication interface and the second communication interface are both connected to the secure element.
  • the secure element signs a transaction and transmits the signed transaction to the first communication interface for provision to the browser extension wallet in response to a first authentication message from the authentication device being received by the second communication interface and verified by the secure element as authentic.
  • the browsing device may be running the browser extension wallet.
  • the browsing device is connected to a network having access to a blockchain to write the signed transaction to the blockchain.
  • a smartphone may be running a smartphone application and may be the authentication device.
  • the authentication device includes a biometric sensor.
  • the first authentication message is an authentication of an identify of the user by the biometric sensor.
  • the biometric sensor is a fingerprint sensor.
  • the biometric sensor is a facial recognition sensor.
  • the sensor may be a touch screen for entering a PIN code.
  • the browsing device is a commodify PC.
  • the authentication device may be a smartphone.
  • the first communication interface may be a wired interface.
  • the wired interface may be a Universal Serial Bus interface.
  • the second communication interface may be a wireless interface.
  • the hardware wallet dongle does not include a screen display. In various embodiments, the hardware wallet dongle includes no human- readable interface.
  • a method of performing a cryplocurrency transaction is provided.
  • the transaction may be performed with a secure browser extension cryptowallet system for securing cryptocurrency transactions in a browser extension wallet.
  • the method may include sending, by the browser extension wallet running on a browser device, a cryptocurrency transaction to a hardware wallet dongle connected to the browser device via a first communication interface.
  • the method may include receiving, by a secure element of the hardware wallet dongle, the transaction, parsing the transaction, and generating a visible representation of the transaction.
  • the method may include sending, by the secure element, the visible representation to a second communication interface wirelessly connectable to an authentication device.
  • the method may include receiving, by the secure element, a first authentication message from the second communication interface, the first authentication message corresponding to a verification by the authentication device of an identity of a user.
  • the method may include signing, by the secure element, the transaction in response to the first authentication message.
  • the method may include transmitting, by the secure element, the signed transaction to the browser extension wallet via the first communication interface, for writing the signed transaction to a blockchain by the browser extension wallet.
  • the visible representation is a transaction amount and a receiver address.
  • FIG. 1 is a diagram of components of a secure browser-based cryptowallet system, in accordance with various embodiments
  • FIG. 2 is a diagram of components of a hardware wallet dongle of a secure browser-based cryptowallet system, in accordance with various embodiments;
  • FIG. 3 is a diagram of components of a hardware wallet dongle of a secure browser-based cryptowallet system having a sensor on the hardware wallet dongle, in accordance with various embodiments;
  • FIG. 4 depicts a method of configuring a system for secure transactions, in accordance with various embodiments.
  • FIG. 5 depicts a method of performing a cryptocurrency transaction with a secure browser-based cryptowallet system, in accordance with various embodiments.
  • Cryptowallets are used to generate and store cryptographic keys required for performing cryptocurrency transactions.
  • Cryptowallets include at least two common varieties.
  • Software wallets are cryptowallets that are a smartphone or desktop application that stores the cryptographic keys and also manages incoming and outgoing transactions.
  • Hardware wallets are cryptowallets that have an embedded device, such as a secure element (SE), that stores the private keys used for signing outgoing transactions.
  • SE secure element
  • the hardware wallet communicates with a smartphone, desktop, or web application “watch-only wallet” that only stores the corresponding public keys of the hardware wallet’s private keys.
  • a watch-only wallet monitors incoming transactions and prepares unsigned outgoing transactions for the embedded device but cannot sign outgoing transactions.
  • the embedded device verifies the transaction details, retrieves the applicable signing key, signs the transaction, and sends the signed transaction back to the smartphone, desktop, or web application to be broadcast to mining nodes.
  • Hardware crypto wallets are known to be more secure than software crypto wallets because the software cryptowallets coexist with other applications on a smartphone or desktop and thus the private keys are susceptible to software attacks on the shared platform, while the keys in a hardware cryptowallet never leave the embedded device. Access to hardware cryptowallet operations is often protected by a personal identification number (PIN) or sensed biometric such as a fingerprint or facial recognition.
  • PIN personal identification number
  • biometric such as a fingerprint or facial recognition.
  • Private keys of a cryptowallet may be generated via a deterministic hierarchical scheme based on one master secret.
  • the master secret is called the seed value. This seed value is important and must be maintained securely.
  • the private keys must also be maintained securely.
  • a user may, in some instances, be required to enter a PIN code associated with the cryptowallet to authorize various transactions. The PIN code should also be maintained securely.
  • wallet users In parallel with these security requirements, wallet users also desire operational convenience.
  • One way to increase convenience is to perform cryptowallet transactions on a web browser.
  • a web browser increases convenience, it also introduces security risks.
  • a popular form of a cryptocurrency wallet is a browser extension wallet which runs software from inside a browser. These wallets usually run on a computer and enable an interactive Web3 user experience. One problem with this type of wallet is protecting the security of storing a cryptographic private key, using a key to sign a transaction, and confirming a transaction.
  • USB wallet with a screen on the USB wallet device is one solution.
  • this device is inconvenient.
  • the form-factor requires connecting the USB wallet to the computer using a USB cable and having the wallet sitting on a desk or dangling. This is inconvenient and limits mobility for a laptop.
  • providing a screen on the USB device is costly.
  • the disclosure herein provides a security solution for browser extension cryptocurrency wallets having a small form factor that could be implemented in the form of a small USB dongle.
  • the disclosure further provides that a secure element of a USB dongle stores a private key and/or seed phrase, parses a cryptocurrency transaction, and/or generates a visible representation of a transaction for presentation to a user on a smartphone device.
  • the disclosure provides a Bluetooth low energy (BLE) radio that connects the USB dongle to a smartphone running a corresponding application, the corresponding application presenting a visible representation of a transaction and facilitating sending by a user of a confirmation or rejection of a transaction to the secure element over Bluetooth low energy (BLE) communication.
  • BLE Bluetooth low energy
  • the disclosure further provides a touch-button or fingerprint touch-ID module connected to the secure element that proves to the secure element that an appropriate user of the system is present and is aware of a transaction being performed.
  • the touch-button or fingerprint touch-ID module, or another sensor is on a different device such as a separate authentication device.
  • the disclosure includes a USB interface to communicate to a browser extension wallet from a USB dongle.
  • the disclosure provides a visual indicator such as a light-emitting diode (LED) that shows the user that activity is occurring on the USB dongle.
  • LED light-emitting diode
  • This disclosure includes systems and methods to address both convenience concerns and security concerns, while avoiding bulky or awkward hardware-based wallet devices.
  • This disclosure provides a hardware solution that isolates cryptowallet operations. This disclosure preserves the current form-factor of a computer by avoiding use of large or unwieldy USB devices or USB devices with large screen displays (for instance, traditional hardware wallets).
  • a secure browser extension cryptowallet system 100 (“system” 100) is illustrated in block diagram form.
  • the system 100 includes a browsing device 106.
  • the browsing device 106 may be a computer, or may be a handheld computer, or may be an application-specific integrated circuit (ASIC) device or may be any other computing platform as desired.
  • the browsing device 106 may be connected to a hardware wallet dongle 108.
  • the hardware wallet dongle 108 comprises a peripheral that is connectable to the browsing device 106 and provides a secure storage and/or secure execution environment for computer data or code to be stored or executed without potential interception, code injection, unwanted access, or other nefarious compromise.
  • the hardware wallet dongle 108 may provide a secure element configured to protect a private key of a user, such as for asymmetric cryptographic keys.
  • the system 100 may interoperate with an authentication device 110.
  • the authentication device 110 may comprise a smartphone device such as a phone that can run applications, or the authentication device 110 may be a dedicated purpose computing device that solely interacts with the secure browser extension cryptowallet system 100.
  • the authentication device 110 may be in wireless communication with the hardware wallet dongle 108 and may provide a user readable interface for the hardware wallet dongle 108.
  • the authentication device 110 may have a display 212 (FIGs.
  • an application running on the authentication device 110 may interact with the hardware wallet dongle 108 so that the hardware wallet dongle 108 can provide data to the authentication device 110 for review by a user on a user-readable interface device such as a display 212 (FIGs. 2-3).
  • the authentication device 110 may provide a mechanism for a user to approve or reject proposed transactions associated with the data being reviewed on the user-readable interface device and the authentication device 110 may transmit data representative of this approval or rejection to the hardware wallet dongle 108.
  • the display 212 (FIGs. 2-3) may be a touch-screen.
  • the system 100 includes a browsing device 106.
  • the browsing device 106 may be a commodity personal computer (“PC”).
  • the browsing device 106 may include a browser 102 and a browser extension wallet 104.
  • a browser 102 may comprise a software application that permits the browsing device 106 to access network resources such as websites, remote computers, Web3 applications, blockchain resources, and the like.
  • the system 100 may also include a browser extension wallet 104.
  • a browser extension wallet 104 is a software-based cryptocurrency wallet that integrates into a browser 102 of a browsing device 106.
  • the system 100 includes a hardware wallet dongle 108.
  • the hardware wallet dongle 108 comprises a hardware device that connects to the browsing device 106.
  • the hardware wallet dongle 108 may connect via a universal serial bus (USB) or other connection type.
  • USB universal serial bus
  • the hardware wallet dongle 108 may have a first communication interface 204.
  • the first communication interface 204 may be a universal serial bus connection interface.
  • the first communication interface 204 connects the hardware wallet dongle 108 in electronic communication with the browsing device 106, and correspondingly, the browser extension wallet 104 of the browsing device 106.
  • the hardware wallet dongle 108 may also have a second communication interface 202.
  • the second communication interface 202 connects the hardware wallet dongle 108 in electronic communication with the authentication device 110. In this manner, the hardware wallet dongle 108 may utilize a display 212 of the authentication device 110.
  • the hardware wallet dongle 108 may include a secure element 206.
  • a secure element 206 (SE) is a tamper-resistant platform capable of securely hosting applications and their confidential and cryptograph data.
  • a secure element 206 may have a memory and or processor for storage of seeds, or private keys and for execution of cryptographic operations with seeds or private keys.
  • one or more of key pairs may be generated within the SE, for enhanced security, such that the key is hardware-backed and cannot be retrieved outside a SE.
  • one or more of the private keys are retained in a SE. This also facilitates improved security. By retaining the key within the SE, the key is secured from retrieval outside the SE, but may still be utilized for cryptographic operations.
  • the secure element may store a private key (seed phrase), parse a cryptocurrency transaction, generate visible representation of the transaction to be presented to a user, and/or receive user confirmation via a push-button or other input connected to secure element.
  • the hardware wallet dongle 108 may have a sensor 210.
  • FIG. 2 illustrates a hardware wallet dongle 108 with a sensor 210.
  • FIG. 3 illustrates that the authentication device 110 has the sensor 210.
  • the sensor 210 may comprise an identity verification sensor, such as a biometric sensor or a code entry mechanism.
  • the biometric sensor may be a fingerprint recognizing touch sensor (e.g., touch- ID) or a face recognizing optical sensor (e.g., face-ID).
  • the hardware wallet dongle 108 in various embodiments, does not include a screen display.
  • the hardware wallet dongle 108 in various embodiments, includes no human-readable interface. In this manner, the hardware wallet dongle 108 may be significantly more compact and convenient than a hardware wallet having a human-readable interface connected directly to a secure element.
  • FIG. 4 describes one example method 400 of a configuring a system for secure transactions using the aforementioned system.
  • a user may link a hardware wallet dongle to a browser extension wallet (block 402).
  • a user may connect the dongle to a browsing device having the browser extension wallet.
  • a user may connect an authentication device to the hardware wallet dongle (block 404).
  • a user may connect a smartphone having a smartphone application configured to communicate with the hardware wallet dongle, to the hardware wallet dongle, via a Bluetooth low energy (BLE) or other wireless connection.
  • BLE Bluetooth low energy
  • a user may establish a first transaction verification identifier, such as a facial recognition, fingerprint recognition, or passcode identifier for entry into the smartphone application configured to communicate with the hardware wallet dongle (or for entry directly into a sensor of the hardware wallet dongle) (block 406).
  • the hardware wallet dongle may establish a private key (e.g., seed phrase) on the secure element (block 408).
  • establishing a private key includes cry ptographically generating the private key by the secure element.
  • establishing a private key may include a user loading a seed phrase onto the hardware wallet device via a USB connection to the browsing device, or via a Bluetooth low energy (BLE) connection to a smartphone.
  • BLE Bluetooth low energy
  • the key may be loaded via a manual entry over BLE, USB, or near field communication.
  • this key is transmitted one time to the authentication device for visual display to a user for manual backup (block 410). In other instances, this key is not transmitted.
  • the devices are now configured for the execution of cryptographic transactions. To execute a cryptographic transaction, further steps may be executed. For instance, referring now to FIG. 5, a method 500 of performing a cryptocurrency transaction with a secure browser extension cryptowallet system may be provided.
  • the method 500 may include a user entering a cryptocurrency transaction on the browser extension wallet running on the browser device (block 502).
  • the browser extension wallet running on the browser device may send the cryptocurrency transaction to the hardware wallet dongle connected to the browser device via a first communication interface (block 504).
  • the secure element of the hardware wallet dongle receives the transaction, parses the transaction, and generates a visible representation of the transaction (block 506).
  • the visible representation comprises a transaction amount and a receiver address.
  • the secure element then causes the hardware wallet dongle to send a notification to the authentication device (block 508).
  • the hardware wallet dongle may send an app push notification to a smartphone and may send the visible representation to the smartphone.
  • the user opens the app notification on the authentication device so that the user may view the visible representation (block 510).
  • the user may interact with the sensor to confirm that the visual representation of the transaction on the authentication device is accurate (block 512). This interaction may take various forms. For instance, a user may press a button.
  • the user may enter a PIN code on the authentication device via a touch screen of the authentication device.
  • the user may provide biometric information such touching the sensor to confirm a fingerprint or looking at the sensor to confirm facial recognition.
  • the sensor may be on the authentication device.
  • the sensor may be on the hardware wallet dongle.
  • the transaction is confirmed as accurate, and in various embodiments, the identity of the user is confirmed as authorized.
  • the sensor of the authentication device e.g., smartphone application
  • the secure element receives a first authentication message from the second communication interface, the first authentication message corresponding to a verification by the authentication device of an identity of the user (block 514).
  • the secure element may sign the transaction using a private key in response to the first authentication message (block 516).
  • the secure element may transmit the signed transaction to the browser extension wallet via the first communication interface, for writing the signed transaction to a blockchain by the browser extension wallet (block 518).
  • the browser extension wallet receives the signed transaction and publishes the signed transaction to a blockchain to complete a transaction (block 520).
  • a user may further establish a signing policy of the hardware wallet dongle, such as including a receiver whitelist or blacklist, a transaction amount limit, a destination address selection criteria, or other requirements.
  • a signing policy of the hardware wallet dongle such as including a receiver whitelist or blacklist, a transaction amount limit, a destination address selection criteria, or other requirements.
  • connecting lines shown in various figures contained herein are intended to represent exemplary functional relationships and/or physical couplings between various elements. It should be noted that many alternative or additional functional relationships or physical connections may be present in a practical method of construction.
  • mechanical communication means any joint, connection, bond, or arrangement whereby an article is held, retained, or fixed in relatively static spatial relationship to another article.
  • electronic communication means any wired, wireless, analog, digital, or other mechanism whereby information is communicated between machines, circuits, or devices.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Technology Law (AREA)
  • Computer Hardware Design (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Remote Sensing (AREA)
  • Radar, Positioning & Navigation (AREA)
  • Telephone Function (AREA)

Abstract

La prévalence des transactions de cryptomonnaie augmente. Une pratique de sécurité importante pour des transactions de cryptomonnaie consiste à maintenir un cryptoportefeuille avec une clé privée pour signer des transactions de cryptomonnaie. Des cryptoportefeuilles à base de matériel avec un élément sécurisé retenant la clé privée sont hautement sécurisés. Cependant, des cryptoportefeuilles à base de matériel peuvent être volumineux en raison du besoin de présenter une interface lisible par l'homme pour la vérification de détails de transaction. Un cryptoportefeuille à base de matériel amélioré est fourni qui omet l'interface lisible par l'homme et qui utilise un dispositif d'authentification connecté sans fil, tel qu'un téléphone intelligent, pour fournir un écran d'affichage pour un utilisateur. De cette manière, une transaction peut être sécurisée sans avoir besoin d'un portefeuille matériel avec un facteur de forme volumineux ou encombrant.
PCT/US2023/033897 2022-09-27 2023-09-27 Sécurisation de cryptoportefeuilles d'extension de navigateur à l'aide d'une clé électronique matérielle WO2024072911A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202263410583P 2022-09-27 2022-09-27
US63/410,583 2022-09-27

Publications (1)

Publication Number Publication Date
WO2024072911A1 true WO2024072911A1 (fr) 2024-04-04

Family

ID=90479015

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2023/033897 WO2024072911A1 (fr) 2022-09-27 2023-09-27 Sécurisation de cryptoportefeuilles d'extension de navigateur à l'aide d'une clé électronique matérielle

Country Status (1)

Country Link
WO (1) WO2024072911A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170154330A1 (en) * 2013-03-01 2017-06-01 Samsung Pay, Inc. Mobile checkout systems and methods
US20210344487A1 (en) * 2019-02-08 2021-11-04 Keyless Technologies Ltd Authentication processing service
US20220092589A1 (en) * 2018-10-02 2022-03-24 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170154330A1 (en) * 2013-03-01 2017-06-01 Samsung Pay, Inc. Mobile checkout systems and methods
US20220092589A1 (en) * 2018-10-02 2022-03-24 Capital One Services, Llc Systems and methods for cryptographic authentication of contactless cards
US20210344487A1 (en) * 2019-02-08 2021-11-04 Keyless Technologies Ltd Authentication processing service

Similar Documents

Publication Publication Date Title
US9741033B2 (en) System and method for point of sale payment data credentials management using out-of-band authentication
US11557164B2 (en) Contactless card personal identification system
CN108769027B (zh) 安全通信方法、装置、移动终端和存储介质
JP2019083536A (ja) モバイルアプリケーションの安全性を確保する方法および装置
US20100180120A1 (en) Information protection device
EP2690840B1 (fr) Appareil et procédé d'interaction d'informations de sécurité basée sur l'internet
US11042624B2 (en) Wireless injection of passwords
US20120303964A1 (en) Portable terminal, and method for securing data transmitted between hardware modules
JP2008544710A (ja) 暗号化を実現する方法及び装置
US20120095919A1 (en) Systems and methods for authenticating aspects of an online transaction using a secure peripheral device having a message display and/or user input
US20210184851A1 (en) Authentication device, system and method
Frisby et al. Security Analysis of Smartphone Point-of-Sale Systems.
US20140025946A1 (en) Audio-security storage apparatus and method for managing certificate using the same
US10963546B2 (en) Biometric security device
KR101272349B1 (ko) 복수의 일회용 비밀번호를 이용한 사용자 인증 방법
US10845990B2 (en) Method for executing of security keyboard, apparatus and system for executing the method
US20120272060A1 (en) Electronic file delivering system, relevant mobile communication device, and relevant computer program product
CN112636914A (zh) 一种身份验证方法、身份验证装置及智能卡
WO2024072911A1 (fr) Sécurisation de cryptoportefeuilles d'extension de navigateur à l'aide d'une clé électronique matérielle
US9477822B1 (en) Secure password entry for accessing remote online services
CN107026817B (zh) 一种密码自动输入的系统
CN113904850A (zh) 基于区块链私钥keystore安全登录方法、生成方法、系统及电子设备
WO2011060739A1 (fr) Système et procédé de sécurité
WO2013183010A1 (fr) Dispositif d'entrée auxiliaire pour entrée de données chiffrées
WO2024072824A2 (fr) Cryptoportefeuilles matériels sécurisés pour des téléphones intelligents

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23873587

Country of ref document: EP

Kind code of ref document: A1