What occurs here that the github username is used? Seems like it should be a gpg email attached to your key?

What is this gverify thing? Is this part of gitian?

it is your github user name. What ever github user you are using now.

This is a true statement. *Why* is it my github username?

Is it intentional to switch to $USER here from $GUSER?

I'm not sure how to do this on vagrant. Please include instructions on how that's done. My shallow understanding is there's a shared directory where you can put the key file, but I'm not sure which.

You just need to run gpg --import < key_file on the virtual box. The keys will be stored somewhere inside ~/.gnpg.

key_file's contents can be scp or copy and pasted to the virtual box from the key machine.

The string you put there is the name of the path that will be created with your assert + signature.

It seems most people use the GitHub name, to simplify the identification of the builds.

The signature contains the key id that was used to sign it, and the person verifying the signature need to have imported the matching public key before hand. It doesn't have to match the github user name

thanks. updated.

it will check you build against other builders, it is a gitian feature already there.

It is the same we do it manually on slack, but better.

I understand the first part, but it's not clear to me how to scp to a local vagrant box. Is there a default server to scp to/from? It looks like there's a pluging to do it: https://github.com/invernizzi/vagrant-scp but we don't have this plugin as part of our dev process as far as I know.

Does the NFS mounts I have been using not work for you?