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
The packager could list the gpg key, and we will just check against it. The idea is to check the key didn't change from the past, rather than doing the full verification of identity.
Bonus point, we could start to rank upstream by some metrics on "being serious by using more than md5, using a proper gpg key", ie assess usage ( so checksum + signature ), and then later people using strong enough keys and checksum ( like what qualys did for SSL ).
The text was updated successfully, but these errors were encountered:
This feature is described here fedora-infra/anitya#191.
Example: http://www.postgresql.org/ftp/source/v9.2.0/ there is a .md5 file.
The packager could list the gpg key, and we will just check against it. The idea is to check the key didn't change from the past, rather than doing the full verification of identity.
Bonus point, we could start to rank upstream by some metrics on "being serious by using more than md5, using a proper gpg key", ie assess usage ( so checksum + signature ), and then later people using strong enough keys and checksum ( like what qualys did for SSL ).
The text was updated successfully, but these errors were encountered: