Thanks! I've added this to the transcript.
On Sat, Jan 6, 2018 at 8:02 PM, Brian via zapps-wg
> Powers of Tau Operational Writeup
> Date: 2018-01-06
> Name: Brian Gomes Bascoy
> Location: Seattle, WA, USA
> Preparation Steps
> Host system:
> Linux yuri 4.14.11-1-ARCH #1 SMP PREEMPT Wed Jan 3 07:02:42 UTC 2018
> x86_64 GNU/Linux
> Guest system:
> Linux debian 220.127.116.11-amd64 #1 SMP Debian 4.14.7-1 (2017-12-22) x86_64
> On 2018-01-05 I installed Debian "buster" (I had to use testing for the
> cargo package) with encrypted LVM on a VirtualBox VM with a 8GB fixed
> size virtual HD. I kept the laptop (a ThinkPad T450s that I bought
> about two years ago) with me the whole time here in my apartment. The
> host OS is Arch Linux without swap space, which I had fully upgraded a
> few hours before. To the best of my knowledge I never had any kind of
> security incident with this computer, which I have used for instance to
> do valuable cryptocurrencies transactions and also to manage banks and
> investments accounts, so I'm relatively confident that it's somewhat
> Used apt-get to install unzip, rustc, cargo and all its dependencies.
> Downloaded the current Powers of Tau master branch with wget from
> GitHub (https://github.com/ebfull/powersoftau/archive/master.zip).
> Side Channel Defenses
> It's not much but: I left my cell phone far away from the basement room
> where I had my laptop, disabled the wifi kernel modules, and unplugged
> the power adapter before starting the process. I didn't use any other
> electronic device (not even my lovely mechanical keyboard ^_^).
> Sean Bowe sent me a link to a page hosted on an Amazon S3 instance with
> a link to the challenge file. I downloaded it using the host system at
> 11:20 AM (PST) and then I disconnect it from the Internet and unplugged
> the charger. I started the guest system VM and used scp to copy the
> challenge. I ran cargo, introduced more than a minute of random
> keyboard typing, then waited for almost 4 hours for the process to
> complete (unfortunately I had to charge the batteries after the 3rd
> hour for about 30 minutes). When it finished I took a picture of the
> hash with a Canon EOS, and copied the response file using scp to the
> host system.
> Deleted all the VM files with shred, rebooted and then ran Lenovo's
> Diagnostic tool on CPU, RAM, HDD and motherboard, to cleanup registers,
> memory, caches, buffers, etc.
> I verified the photograph of the response's BLAKE2 checksum, and after
> posting this report I will check it again from the mailing list archive
> using different devices.
> a3a5b581169394e68a0d566e72df3a6a4bd3c54e7e75c87b01c4c981401dcfd4 virtu
> a8e8aff5c5709657ec40b1a8eb5c58c9f543386532261bdd4a30ca3ca462e3e4 virtu
> 41670305b5468693e4fb17f8a695ba1fe5385a088d7fc2b1efb81b956f68c5c1 debia
> 2f186a48f45c31844b8288d9ee403b97ff558735478a215c49bb13652fe2fdc5 cargo
> 88a2e940bd7573c62ee3a979f823c47c2e252ef54ec6a885fdcac56705cd1a8a rustc
> d0d8d9ab3e55b139a207c43b7a15faec17faf7b0da77f9b844ffd2d2c03b68e6 unzip
> 0902301defc0705d3d824d9ec17382f40785cb9ce84502ee13b774840752def7 maste
> Debian ISO's SHA256SUMS.SIGN