bitcoin-core / guix.sigs Goto Github PK
View Code? Open in Web Editor NEWBitcoin Core release attestations (Guix)
Bitcoin Core release attestations (Guix)
In #1201 it turns out that @0xB10C had been building mismatching builds for a while, without it being noticed before.
It would be useful to have some kind of notification when this happens. A mismatching build always points to a problem, either (in the good case) a local configuration issue, but it can also be a bug in the build system or worst-case even a backdoor attempt. So it needs to be investigated.
See discussion here: #1201 (comment)
.
Looks like the \n
remains escaped in the CI log. Maybe a good first issue if someone wants to fix this in a follow-up?
Originally posted by @MarcoFalke in #544 (comment)
Currently I import the keys by running:
KEY_URL=https://raw.githubusercontent.com/bitcoin-core/guix.sigs/main/builder-keys
curl -sSL ${KEY_URL}/CoinForensics.gpg | gpg --import - \
&& curl -sSL ${KEY_URL}/Emzy.gpg | gpg --import - \
&& curl -sSL ${KEY_URL}/Sjors.gpg | gpg --import - \
&& curl -sSL ${KEY_URL}/TheCharlatan.gpg | gpg --import - \
&& curl -sSL ${KEY_URL}/achow101.gpg | gpg --import - \
&& curl -sSL ${KEY_URL}/benthecarman.gpg | gpg --import - \
&& curl -sSL ${KEY_URL}/cfields.gpg | gpg --import - \
&& curl -sSL ${KEY_URL}/darosior.gpg | gpg --import - \
&& curl -sSL ${KEY_URL}/dunxen.gpg | gpg --import - \
&& curl -sSL ${KEY_URL}/fanquake.gpg | gpg --import - \
&& curl -sSL ${KEY_URL}/glozow.gpg | gpg --import - \
&& curl -sSL ${KEY_URL}/guggero.gpg | gpg --import - \
&& curl -sSL ${KEY_URL}/hebasto.gpg | gpg --import - \
&& curl -sSL ${KEY_URL}/jackielove4u.gpg | gpg --import - \
&& curl -sSL ${KEY_URL}/josibake.gpg | gpg --import - \
&& curl -sSL ${KEY_URL}/laanwj.gpg | gpg --import - \
&& curl -sSL ${KEY_URL}/satsie.gpg | gpg --import - \
&& curl -sSL ${KEY_URL}/sipa.gpg | gpg --import - \
&& curl -sSL ${KEY_URL}/svanstaa.gpg | gpg --import - \
&& curl -sSL ${KEY_URL}/theStack.gpg | gpg --import - \
&& curl -sSL ${KEY_URL}/vertiond.gpg | gpg --import - \
&& curl -sSL ${KEY_URL}/willyko.gpg | gpg --import -
But as soon as new signers will be added or removed in the future, the script will break.
So why is there not a single file that bundles all the current keys so that I dont have to download them all individually?
Or otherwise at least a file that contains all the names of the signers, so that I can parse that instead of hardcoding the names in my code?
Should there be a sanity check similar to https://github.com/bitcoin-core/gitian.sigs/blob/dfaecb5fa5062a3b2443e1f93933139b864745d8/.travis.yml ?
See #27 (comment)
We should have a directory where it's just people's public keys to avoid over-reliance on keyservers and this situation: bitcoin-core/bitcoincore.org#793 (comment)
We can check via CI that everyone who uploads has a key and that signatures are valid.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.