Systems and methods for securely transferring account information between devices
In one embodiment, a method includes scanning, by a first device, a code from a second device and determining, by the first device, information comprising a peer identifier and a first certificate hash using the code. The method also includes initiating, by the first device, a connection with the second device using the peer identifier and receiving, by the first device, a second certificate hash from the second device via the connection. The method further includes validating, by the first device, the second certificate hash using the first certificate hash, establishing a session with the second device, and transferring, by the first device, account information to the second device via the session.
1 . A first device, comprising:
one or more processors; and
one or more computer-readable non-transitory storage media coupled to the one or more processors and comprising instructions that, when executed by the one or more processors, cause the first device to perform operations comprising:
scanning a code from a second device, wherein the code is generated by the second device in response to receiving a request to transfer account information from the second device to the first device;
determining information comprising a peer identifier and a first certificate hash using the code, wherein the first certificate hash is generated by the second device and the peer identifier is a verifiable link between a peer and its public cryptographic key;
initiating a connection with the second device using the peer identifier;
receiving a second certificate hash from the second device via the connection;
comparing the first certificate hash to the second certificate hash;
validating the second certificate hash using the first certificate hash;
establishing a session with the second device; and
transferring the account information to the second device via the session.
2 . The first device of claim 1 , wherein the code is a machine-readable image.
3 . The first device of claim 1 , wherein the connection is one of the following:
a Transport Layer Security (TLS) connection;
a Datagram Transport Layer Security (DTLS) connection; or
a Constrained Application Protocol (CoAP) connection.
4 . The first device of claim 1 , wherein the first certificate hash is generated by the second device by hashing a self-signed certificate.
5 . The first device of claim 1 , wherein:
an operating system of the first device is one of the following:
an iPhone Operating System (iOS); or
an Android OS; and
an operating system of the second device is one of the following:
an iOS; or
an Android OS.
6 . The first device of claim 1 , wherein:
the account information is associated with a mobile application installed on the first device; and
the account information comprises an identity of at least one third-party account.
7 . The first device of claim 1 , wherein the session is an encrypted, authenticated multi-party computation (MPC) session.
8 . A method, comprising:
scanning, by a first device, a code from a second device, wherein the code is generated by the second device in response to receiving a request to transfer account information from the second device to the first device;
determining, by the first device, information comprising a peer identifier and a first certificate hash using the code, wherein the first certificate hash is generated by the second device and the peer identifier is a verifiable link between a peer and its public cryptographic key;
initiating, by the first device, a connection with the second device using the peer identifier;
receiving, by the first device, a second certificate hash from the second device via the connection;
comparing, by the first device, the first certificate hash to the second certificate hash;
validating, by the first device, the second certificate hash using the first certificate hash;
establishing, by the first device, a session with the second device; and
transferring, by the first device, the account information to the second device via the session.
9 . The method of claim 8 , wherein the code is a machine-readable image.
10 . The method of claim 8 , wherein the connection is one of the following:
a Transport Layer Security (TLS) connection;
a Datagram Transport Layer Security (DTLS) connection; or
a Constrained Application Protocol (CoAP) connection.
11 . The method of claim 8 , wherein the first certificate hash is generated by the second device by hashing a self-signed certificate.
12 . The method of claim 8 , wherein:
an operating system of the first device is one of the following:
an iPhone Operating System (iOS); or
an Android OS; and
an operating system of the second device is one of the following:
an iOS; or
an Android OS.
13 . The method of claim 8 , wherein:
the account information is associated with a mobile application installed on the first device; and
the account information comprises an identity of at least one third-party account.
14 . The method of claim 8 , wherein the session is an encrypted, authenticated multi-party computation (MPC) session.
15 . One or more computer-readable non-transitory storage media embodying instructions that, when executed by a processor, cause the processor to perform operations comprising:
scanning, by a first device, a code from a second device, wherein the code is generated by the second device in response to receiving a request to transfer account information from the second device to the first device;
determining information comprising a peer identifier and a first certificate hash using the code, wherein the first certificate hash is generated by the second device and the peer identifier is a verifiable link between a peer and its public cryptographic key;
initiating a connection with the second device using the peer identifier;
receiving a second certificate hash from the second device via the connection;
determining that the first certificate hash matches the second certificate hash;
validating the second certificate hash using the first certificate hash;
establishing a session with the second device; and
transferring the account information to the second device via the session.
16 . The one or more computer-readable non-transitory storage media of claim 15 , wherein the code is a machine-readable image.
17 . The one or more computer-readable non-transitory storage media of claim 15 , wherein the connection is one of the following:
a Transport Layer Security (TLS) connection;
a Datagram Transport Layer Security (DTLS) connection; or
a Constrained Application Protocol (CoAP) connection.
18 . The one or more computer-readable non-transitory storage media of claim 15 , wherein the first certificate hash is generated by the second device by hashing a self-signed certificate.
19 . The one or more computer-readable non-transitory storage media of claim 15 , wherein:
an operating system of the first device is one of the following:
an iPhone Operating System (iOS); or
an Android OS; and
an operating system of the second device is one of the following:
an iOS; or
an Android OS.
20 . The one or more computer-readable non-transitory storage media of claim 15 , wherein:
the account information is associated with a mobile application installed on the first device; and
the account information comprises an identity of at least one third-party account.