Do you have any recommendations for microphones suitable for desktop use?

Financial services should employ a second JS-based PKI layer. BofA has no excuse.

"... log into the BofA website using the AccountID of "barry123457". While this transaction went over SSL, you can see clearly that sslsplit was able to intercept it. AS you can see, in the middle of the post information is the string "barry123457".

You realize that anything the real BofA site adds to increase security can be removed by the proxy? Once your CA trust-store is compromised there really is no way to do anything secure without asking the user to use another channel to verify things.

> You realize that anything the real BofA site adds to increase security can be removed by the proxy?

This is true for targeted attacks only. A second JS layer doing crypto can at least prevent firesheep-class untargeted mass snooping of auth data.

Wonder if these improvements work in tandem with the in-memory columnar store (incs) contributed by Konstantin Knizhnik.

IMCS [1] already uses SIMD vector instructions.

[1] http://www.pgcon.org/2014/schedule/attachments/322_IMCS.pdf

I found the incremental approach used in redis to be most interesting (http://antirez.com/news/63).

Can you comment on how one can safely enumerate "all" keys of the hashtable, while minimizing contention.

It would be great to know whether, in principle, rhashtable can offer such a capability.

> Can you comment on how one can safely enumerate "all" keys of the hashtable, while minimizing contention.

for each bucket: