~ivilata/gwit-spec: Allow both binary and ASCII-armored formats for the site key file.

e65516bd004deb11ab47cc4e10f0c4404859fbed — Ivan Vilata-i-Balaguer 4 months ago 7132c26

Allow both binary and ASCII-armored formats for the site key file.

Do not require the ASCII format, as it does not provide any relevant advantage
for gwit: the content is still not useful for humans, and it should not change
very often.  Plus GnuPG can handle both formats just fine.

This is a backwards-compatible change.

patch browse .tar.gz

1 files changed, 1 insertions(+), 1 deletions(-)

M README.md

M README.md => README.md +1 -1

@@ 74,7 74,7 @@ Since gwit is based on Git, a gwit site is made up of *static files and director
 
 To use a particular commit of a Git repository as a gwit site, the top directory of the commit MUST include a `_gwit` directory (underscore `gwit`), which in turn:
 
-- MUST include a `self.key` file containing the site key (and any signing subkeys) in ASCII-armored OpenPGP public key format (e.g. the output of `gpg --export --armor <SITE-KEY>`). Although the primary key itself SHOULD NOT change, subsequent updates to `_gwit/self.key` MAY add new subkeys, identities, signatures, revocations and other metadata.
+- MUST include a `self.key` file containing the site key (and any signing subkeys) in OpenPGP public key format, ASCII-armored or not (e.g. the output of `gpg --export [--armor] <SITE-KEY>`). Although the primary key itself SHOULD NOT change, subsequent updates to `_gwit/self.key` MAY add new subkeys, identities, signatures, revocations and other metadata.
 - SHOULD include a `self.ini` file with the **site configuration**. Its contents are described below.
 
 Also, the commit MUST be signed by the private key associated with the site key, or by a signing subkey of it.