|
|
@@ -9,6 +9,27 @@ file. |
|
|
|
The only file needed for this is the snapaid.sh script. The other files |
|
|
|
are used for generating the index. |
|
|
|
|
|
|
|
NOTE: The xz vs non-xz versions of some of the images are not able to be |
|
|
|
differentiated. Currently shorting rules should always put the xz version |
|
|
|
before the non-xz version. |
|
|
|
|
|
|
|
NOTE: Only snapshots that have SHA512 hashes are included. This excludes |
|
|
|
most snapshots from 2015 and before. The tool could be updated to include |
|
|
|
SHA256, but not a priority currently. |
|
|
|
|
|
|
|
NOTE: Not all of the snapshots are in the database. Some snapshot names, |
|
|
|
like 11.0-RC1, don't contain all the info others do, and are not |
|
|
|
included. In the future, hopefully this will be fixed. |
|
|
|
|
|
|
|
backend |
|
|
|
------- |
|
|
|
|
|
|
|
The backend is just a simple text file the indexes all the published |
|
|
|
snapshots. It is built from the emails to the freebsd-snapshot |
|
|
|
list. After verification of the email's signature, the SHA512 entry |
|
|
|
lines are extracted, the file name is parsed, and added to the complete |
|
|
|
index. The message-id of the email is in the index so that the frontend |
|
|
|
can d/l the original email, verify the GPG signature locally. The |
|
|
|
complete index is used for verifying a snapshot that has already been |
|
|
|
downloaded. Another index is also maintained which only contains the |
|
|
|
currently available to d/l snapshots. |