Pinned key types

[tel]

Instead of using Bytestring to store keys a representation using Data.Vector.Storable is pinned in memory and never swapped making their use somewhat safer.

If this is a good fit I could write up a diff.

[thoughtpolice]

Sure. One thing to be aware of is that mlock(2) works on a page sized boundary. I am not sure how many private keys you would expect in a typical application, but a typical 4k to 8k for a single key is a bit wasteful. So you may want to manage that as you wish. I'd certainly accept a patch changing the underlying representation to storable, though.

See issue #10 (although it's pretty pie in the sky.)

[thoughtpolice]

Hm, also be aware that I'm currently working on changing the key types to be more parametric and type safe. The effects of this should mostly be localized, but I may or may not be done before you are, so just be aware (in the worst case I'll do the merge myself no matter what.)