Send patches - preferably formatted by git format-patch - to patches at archlinux32 dot org.
summaryrefslogtreecommitdiff
path: root/doc/makepkg.conf.5.asciidoc
diff options
context:
space:
mode:
authorAllan McRae <allan@archlinux.org>2020-01-23 12:14:14 +1000
committerAllan McRae <allan@archlinux.org>2020-01-28 10:46:26 +1000
commit21af79860403f9120d2c0412a95ec97d06368e11 (patch)
tree44961845d694432a85a70cf25f702ff181a1d95a /doc/makepkg.conf.5.asciidoc
parentc3852ff42569542b787d9e49289f5358ad22f900 (diff)
makepkg: add CRC checksums and set these to be the default
Checksums arrays should be filled with values provided by upstream. We currently have md5 set as an unsecure default, and are constantly asked to change it to sha2. However, just changing the default to a stronger checksum gives the user the impression that "makepkg -g" checksums are perfect. Instead, change the default checksum to a CRC, to make it clear that any checksum generated purely by "makepkg -g" is not ideal. Signed-off-by: Allan McRae <allan@archlinux.org>
Diffstat (limited to 'doc/makepkg.conf.5.asciidoc')
-rw-r--r--doc/makepkg.conf.5.asciidoc2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/makepkg.conf.5.asciidoc b/doc/makepkg.conf.5.asciidoc
index b7496324..04cc5ea9 100644
--- a/doc/makepkg.conf.5.asciidoc
+++ b/doc/makepkg.conf.5.asciidoc
@@ -192,7 +192,7 @@ Options
**INTEGRITY_CHECK=(**check1 ...**)**::
File integrity checks to use. Multiple checks may be specified; this
affects both generation and checking. The current valid options are:
- `md5`, `sha1`, `sha224`, `sha256`, `sha384`, `sha512`, and `b2`.
+ `ck`, `md5`, `sha1`, `sha224`, `sha256`, `sha384`, `sha512`, and `b2`.
**STRIP_BINARIES=**"--strip-all"::
Options to be used when stripping binaries. See linkman:strip[1]