You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently it is not possible to verify the cryptographic authenticity after downloading the Trust Wallet software because the releases are not cryptographically signed.
This makes it hard for Trust Wallet users to safely obtain the Trust Wallet software, and it introduces them to supply chain attacks.
I should be able to download the Trust Wallet Team's Software Release PGP Public Key out-of-band from popular third-party keyservers (eg https://keys.openpgp.org/)
I should be able to download a cryptographic signature of the release (or, better, the releases' digest file, such as a SHA256SUMS.asc file) along with the release itself
The downloads page itself should include a link to the documentation page that describes how to do the above two steps
Actual behavior
There's just literally no information on verifying downloads, and it appears that it is not possible to do so.
Versions Affected
Everything, all versions.
Use case
Installing the software securely
Suggested implementation
Cryptographic signing of all software releases with PGP
The text was updated successfully, but these errors were encountered:
Monero is a good case study because they actually were cryptographically signing their releases with PGP. Because of this, their users had a means to detect that the software they downloaded was malicious. It was reported to the developers, and the issue was promptly resolved.
But without signing releases (as is currently the case with Trust Wallet), a user has no way to know if the software they downloaded is [a] authentic or [b] maliciously modified.
Feature Request
Currently it is not possible to verify the cryptographic authenticity after downloading the Trust Wallet software because the releases are not cryptographically signed.
This makes it hard for Trust Wallet users to safely obtain the Trust Wallet software, and it introduces them to supply chain attacks.
Steps to Reproduce
Expected Behavior
A few things are expected:
SHA256SUMS.asc
file) along with the release itselfActual behavior
There's just literally no information on verifying downloads, and it appears that it is not possible to do so.
Versions Affected
Everything, all versions.
Use case
Installing the software securely
Suggested implementation
Cryptographic signing of all software releases with PGP
The text was updated successfully, but these errors were encountered: