Need out-of-the-box support for bcrypt/blowfish/twofish/etc.

[Abscissa]

Like the title says.

[aberba]

I was going to file an issue on bcrypt support. 😄 and I saw this. Yet, its been over a year since it was filed. Botan has implemented it but your api seem more clean.

[Abscissa]

Yea, my work on this lib has been converting it to the "Basic" part of the 3-part "InstaUser" (preview over here), but I haven't had much time for it in awhile. I'm hoping to be able to get back to it soon, though. When I do, this issue, along with getting a first release of InstaUser ready, will be the absolute top priorities for InstaUser.

[Abscissa]

I've been working on this, but one thing that's been slowing progress is that bcrypt has certain fundamental incompatibilities with std.digest, which DAuth is fairly heavily based around. So incorporating bcrypt (it will use Botan's bcrypt behind-the-scenes) has required some fairly significant re-thinking of DAuth's internals. I think I'm through the bulk of the difficulties though, in that I've mostly worked out how to make it all mesh together.

[ghost91-]

@Abscissa are you still working on this? Do you intend to make Botan a dependency? if so, please make this optional. I am currently using dauth in a project, which is intended to run on arm. Botan is not available on arm architectures and if dauth had a hard dependency on Botan, then I'd not be able to use dauth in my project anymore.

[Abscissa]

Although I've been having trouble making time for this project, it's definitely still on my radar. In fact, a work project I'm in the early stages of is going to need this anyway.

You make a good point about botan. I'll try to make sure it's an optional dependency. bcrypt will still require botan (at least initially anyway - I'd be perfectly happy to have an alternative option for bcrypt support to increase compatibility).