On Mon, 05 Feb 2018, [email protected] (Ludovic Courtès) wrote: > Hi amirouche, > > amirouche <[email protected]> skribis: > >> After discussing gnunet & guix at fosdem with gnunet >> people I have better picture of where things can go. >> >> The short story is: >> >> 1) There is no way to know the gnunet hash aka. gnunet uri >> of a substitute before the build. >> >> 2) There is no way to associate gnunet hash and guix hash >> in a secure/trusted manner over gnunet. Except maybe >> if we use GNS to publish guix hash as subdomains of >> substitute-server.guix.gnu? > > Before jumping to conclusions, did you check the narinfo format that we > use on HTTP? A narinfo is essentially a statement that a given store > item, resulting from a .drv build, has a specific content hash. > > Lookup by content hash over GNUnet’s AFS is all we’d need. > > See also the discussion in > <https://www.gnu.org/software/guix/blog/2017/reproducible-builds-a-status-update/>. > > HTH! > > Ludo’. > > _______________________________________________ > GNUnet-developers mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/gnunet-developers
Adding to this subthread: I added nar and narinfo support to libextractor last year, maybe this comes in handy as well. -- ng0 :: https://ea.n0.is A88C8ADD129828D7EAC02E52E22F9BBFEE348588 :: https://ea.n0.is/keys/ _______________________________________________ GNUnet-developers mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnunet-developers
