<mark_weaver>sriharsha: btw, I wanted to mention that I would indeed like to get you shell access to a MIPS machine where you can debug the GNUnet problem, it's just that I've been overwhelmed with other things such as the recent Guile release(s).
<sriharsha>Ideally, one would generate and leave the master key on a computer that would never be hooked to the grid. Message encryption and signing are then done through subkeys which are added to the master key.
<mark_weaver>sriharsha: btw, I have a question: when I download from the GNUnet SVN repo, how do I know that the code wasn't modified in transit? also, if someone broke into the repo and modified it, how would that be detected?
<phant0mas>civodul: after a talk I had with David Michael, who is building his own hurd system from source I found that I shouldn't run autoreconf inside libpthread but just rerun it in the base glibc folder after I place the libpthread folder in it
<mark_weaver>sriharsha: GIT has a nice property that the commits are referenced by cryptographic hashes, and things are done in such a way that if the repo was changed, devs would likely notice it when pulling.
<sriharsha>mark_weaver, you have to rely on trusting the https connection to gnunet.org
<civodul>phant0mas: oh yeah so libpthread/configure just sets $libc_add_on_*, right?
<mark_weaver>sriharsha: i.e. any CA in my trust store could forge the cert and enable a MitM attack, right?
<civodul>mark_weaver: yes, it's only used for profiles
<civodul>phant0mas: yes, either that or add the version that it needs
<sriharsha>civodul, so I added the svn-fetch. How can I be sure that when a package uses svn-fetch, subversion is already installed in store? Should I include subversion as build dependency somewhere or will the derivation treats it as one automagically?
<mark_weaver>civodul: okay, well, I plan to get the union.scm changes done in the next two days. but if you'd like to apply a workaround to libffi.scm in the meantime and merge core-updates to master, that's fine too.
<civodul>sriharsha: yes, make subversion an input of the derivation, just like git is made an input in git-download.scm
<phant0mas>in aclocal.m4 files it says that it requires that everyone use exactly the same Autoconf version so that the internal functions defined and used by the main configure script match those expected by the fragments.
<civodul>phant0mas: then see texinfo.scm for an example of how to define a secondary version