-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Description
Background
In the installation instructions, Roasbeef's PGP key is obtained from a github gist, and then used to verify the release, also downloaded from github. Since the release is already being downloaded over SSL, this effectively means that the verification step adds no additional security.
Note: This was introduced in the pr #3377:
"In this commit, we update the link to the security PGP key to a gist. We
do this as recent DoS attacks against popular keservers have rendered
many of them unresponsive or only partially operating. As a temporary
measure, we link to a gist until an alternative solution is found."
Your environment
Downloading LND from the releases page on github.
Expected behaviour
If the PGP key was obtained from a different source, that would at least mean that github would have to collude with that source to forge a release.
Actual behaviour
See background