- 14 Mar 2023
- 1 Minute to read
Validation & Security
- Updated on 14 Mar 2023
- 1 Minute to read
A Universal Package is intended to be read-only, and once created, its contents and metacontents sealed within the package and not tampered with. However, the simple format of a Universal Package makes it easy to tamper with its contents using a zip editor.
This is where cryptographic hashing comes into play. This is a small text string that acts as a "thumbprint" of a file and allows you to verify that it is the expected file after downloading "Accounts/HDars v1.3.4" from a package source.
Since the hash of a package is calculated from the bytes in the package file, it is impossible to store the hash of a package within the package, since changing the package would change the hash. For this reason, a trusted package source should be used to verify the hash of the package.
However, a package's manifest file may reference other packages' hashes in the
Secure Package Identifier
A universal package can be uniquely identified by its group, name, and version. In some cases, such as when specifying a dependency or describing an audit trail, these details are combined into a single string.
The format for this string is quite simple: group and name are combined (separated by a slash), and version is appended (separated by a colon). For example:
To ensure a tamper-proof chain of packages, you may also use a package's cryptographic hash by appending a colon and then a hash string to the end of a package.
This will be used for verification purposes when possible. For example:
If the identified packages exist, but the hash doesn't exist, then the package will not be used.
Package Hash Format
Package hashes are calculated using the SHA-1 algorithm, and encoded visually as a 40-character case-insensitive string of hexidemical digits without spaces or other separator characters. For example: