Thomas Jensen

I had a bunch of stuff laying around in branches, so I brought a version up to date here: https://github.com/srcagency/credentials The code base is pretty much a complete rewrite though...

> as long as the tests still pass They don't. The interface is different: - By default there's no instantiation or even a constructor/closure - The `configure` function returns new...

> I assume you've updated the test suite and that all the new tests pass? Oh, yes, of course 😛 Feel free to do that.

So, I assume, with my newbie cryptography knowledge, that the entropy is by definition the same regardless of how you encode the bytes. If that is the only desirable property...

After some quick searching it seems there is at least nothing bad in what you're suggesting, and it does give a ~2x speedup on hashing, which I fear an attacker...

Thanks. So, what you are suggesting is: - Use SHA-256 - Use a 256 bits salt - Use a key length of 24 Currently the key length is set to...

This is something that keeps biting me as well. Streams and promises are both excellent abstractions, but the interoperability is poor. I have been a heavy user of your "promise-streams",...

If someones into pull-streams, here's some helpers I've build recently (promises made by Bluebird): https://github.com/srcagency/pull-from-promise https://github.com/srcagency/pull-to-promise https://github.com/srcagency/pull-json-stringify https://github.com/srcagency/pull-json-parse

Saw this too. ``` $ fkill gpg ? Error killing process. Would you like to use the force? Yes AggregateError: Error: Killing process gpg failed: Process doesn't exist at Array.map...

I'm not really concluded on whether I would, personally, like the `= ` or not. I would like to do some research into whether parsers (and the spec for it)...