5 commits

Author	SHA1	Message	Date
SomberNight	f5f3394552	git sanity: enforce "git checkout commithash" actually pulls commit ... If there is a collision between a branch name and a commit hash, git will choose the branch, even if the full 40-hex-long commit hash is given. GitHub disallows branches/tags with such a name but git itself does not. By adding the `^{commit}` syntax sugar after a ref name, we can tell git that we want the commit hash to be preferred, and hence we don't need to trust GitHub (only git). see https://security.stackexchange.com/questions/225411/	2020-06-16 19:55:17 +02:00
SomberNight	83cabccdb5	bump libsecp256k1 version	2020-06-15 16:56:36 +02:00
SomberNight	875e6b31b1	make_libsecp256k1.sh: add comment how to cross-compile to Windows ... related: #5976, #6054	2020-03-29 07:51:48 +02:00
SomberNight	5b84e714f2	build: workaround for 'realpath' missing on macOS	2020-02-11 16:48:28 +01:00
SomberNight	4cec098d2d	build: create a standalone build script for libsecp256k1 ... heavily based on Electron-Cash/Electron-Cash@eda015908e	2020-02-11 16:48:24 +01:00