17 Commits (e64b2f1a16e8d0ad2cd181d84e3b70312e3cdf33)

Author	SHA1	Message	Date
Andrew Chow	53b07b2b47	verify-commits: Move trusted-keys valid sig check into verify-commits itself ... Instead of having gpg.sh check against the trusted keys for a valid signature, do it inside of verify-commits itself. This also allows us to use the same trusted-keys throughout the verify-commits.py check rather than it possibly being modified during the clean merge check.	2 years ago
MarcoFalke	aaaaad6ac9	scripted-diff: Bump copyright of files changed in 2019 ... -BEGIN VERIFY SCRIPT- ./contrib/devtools/copyright_header.py update ./ -END VERIFY SCRIPT-	5 years ago
Hennadii Stepanov	1ac454a384	Enable ShellCheck rules ... Enabled ShellCheck rules: SC1087 SC2001 SC2004 SC2005 SC2006 SC2016 SC2028 SC2048 SC2066 (note that IFS already contains only a line feed) SC2116 SC2166 SC2181 SC2206 SC2207 SC2230 SC2236	5 years ago
Wladimir J. van der Laan	45c00f8416	Merge #13454: Make sure LC_ALL=C is set in all shell scripts ... 47776a958b Add linter: Make sure all shell scripts opt out of locale dependence using "export LC_ALL=C" (practicalswift) 3352da8da1 Add "export LC_ALL=C" to all shell scripts (practicalswift) Pull request description: ~~Make sure `LC_ALL=C` is set when using `grep` range expressions.~~ Make sure `LC_ALL=C` is set in all shell scripts. From the `grep(1)` documentation: > Within a bracket expression, a range expression consists of two characters separated by a hyphen. It matches any single character that sorts between the two characters, inclusive, using the locale's collating sequence and character set. For example, in the default C locale, `[a-d]` is equivalent to `[abcd]`. Many locales sort characters in dictionary order, and in these locales `[a-d]` is typically not equivalent to `[abcd]`; it might be equivalent to `[aBbCcDd]`, for example. To obtain the traditional interpretation of bracket expressions, you can use the C locale by setting the `LC_ALL` environment variable to the value C. Context: [Locale issue found when reviewing #13450](https://github.com/bitcoin/bitcoin/pull/13450/files#r194877736) Tree-SHA512: fd74d2612998f9b49ef9be24410e505d8c842716f84d085157fc7f9799d40e8a7b4969de783afcf99b7fae4f91bbb4559651f7dd6578a6a081a50bdea29f0909	6 years ago
Loganaden Velvindron	9e2e5626da	Fix CVE-2018-12356 by hardening the regex.	6 years ago
practicalswift	3352da8da1	Add "export LC_ALL=C" to all shell scripts	6 years ago
Matt Corallo	a38686cea0	[verify-commits] Fix gpg.sh's echoing for commits with '\n'	7 years ago
Matt Corallo	d23be309c2	[verify-commits] Allow revoked keys to expire	7 years ago
Matt Corallo	f20e664f40	Check gpg version before setting --weak-digest	8 years ago
Matt Corallo	bbd757940b	Fix regsig checking for subkey sigs in verify-commits	8 years ago
Matt Corallo	d025bc7964	Allow any subkey in verify-commits	8 years ago
Peter Todd	eddc77a1b1	Add comment re: why SHA1 is disabled	8 years ago
Matt Corallo	d9c450ffb2	Verify Tree-SHA512s in merge commits, enforce sigs are not SHA1	8 years ago
isle2983	0766d1cac3	[copyright] add MIT license headers to .sh scripts where missing ... Years are set according to 'git log' history	8 years ago
Matt Corallo	f7d4a25fe6	Make verify-commits POSIX-compliant	9 years ago
Matt Corallo	1d94b72019	Whitelist commits signed with Pieter's now-revoked key	9 years ago
Matt Corallo	adaa568722	Add script to verify all merge commits are signed	10 years ago