nnn

An alternative approach would be to call "await util.promisify(socket.connect)(8125, host)" so that subsequent calls to send don't need to name the destination (and the underlying runtime could call send instead of sendto). Perhaps the author needs the messages to be sent to a new host quickly when DNS records change, but the trade-off might be different depending on the use case, and perhaps some applications might prefer to periodically re-connect the socket to re-resolve DNS.

The cost of running Vuvuzela is dominated by bandwidth, and the paper used AWS prices to estimate the cost; purchasing IP transit directly would lead to about an order of magnitude reduction in costs (still non-trivial, of course).

Based on my reading of the article, it says that OpenBSD always uses the same key, scr_key[0], and does not implement the use of different keys for different parts of the disk. I haven't looked at the OpenBSD source code to confirm this, though.

Here are some parts of the KeyKOS source code: http://css.csail.mit.edu/6.858/2011/readings/keykos/