< bitcoin-git>
[bitcoin] achow101 opened pull request #10565: [coverage] Remove leveldb, univalue, and benchmarks from coverage report (master...lcov-remove-extra) https://github.com/bitcoin/bitcoin/pull/10565
< bitcoin-git>
[bitcoin] practicalswift opened pull request #10566: Use the "domain name setup" image (previously unused) in the gitian docs (master...unreferenced-file) https://github.com/bitcoin/bitcoin/pull/10566
< jonasschnelli>
wumpus: the recent mail sent to security@ seems phishy... haven't checked although.
< wumpus>
yes, I'd be careful
< jonasschnelli>
Indeed
< jonasschnelli>
Such attacks (against developers) will rise IMO... good protection is really required now
< wumpus>
yes, agreed, we all need to start using qubes asap :)
< timothy>
the only problem of qubes is xen
< wumpus>
right, that's kind of its central point of failure
< wumpus>
its achilles heel. Then again, it does raise the difficulty and cost of compromise, which is the point of security
< timothy>
people are moving to kvm, xen in less maintained (as "big players" only amazon uses it, but they don't push patches upstream)
< wumpus>
that's good to hear - I use kvm a lot for manual VM wrangling
< wumpus>
kvm+libvirt is a breeze to use
< wumpus>
I also moved all gpg signing to tokens a while ago, as well as some critical ssh authenticions
< timothy>
openstack is kvm-based :)
< timothy>
ovirt / rhv (red hat virtualization) too
< wumpus>
trying to reduce attack surface as well as the impact when compromise would happen
< wumpus>
okay :)
< timothy>
I mean, big players are working on it
< timothy>
infact I think I'll convert my gitian setup to use kvm instead of virtualbox
< wumpus>
I've also started to use freebsd and openbsd for some things, to diversify from just linux
< wumpus>
gitian with virtualbox? didn't know anyone was actually using that, most use either lxc or kvm
< timothy>
the "official" procedure wants to install the VM on virtualbox and then gitian inside the vm
< luke-jr>
gmaxwell: hmm, so I think the only ones who haven't edited or been pinged 1:1 so far would be: sdaftuar MarcoFalke maaku rusty petertodd
< luke-jr>
does p2p-fullblocktest's runbarelyexpensive timeout for anyone else? it seems to have a limit of 60s for a 1000+ block reorg, which isn't practical? O.o