No description
Find a file
2026-01-10 16:34:20 +01:00
docs initial commit 2026-01-10 00:52:00 +01:00
src docs: better documentation 2026-01-10 16:29:05 +01:00
tests chore: version 0.1..0 2026-01-10 01:03:23 +01:00
.gitignore docs: better documentation 2026-01-10 16:29:05 +01:00
bcryptrocks.nimble chore: Update version to v0.1.1 2026-01-10 16:34:20 +01:00
config.nims initial commit 2026-01-10 00:52:00 +01:00
LICENSE chore: Add LICENSE 2026-01-10 16:03:18 +01:00
README.md docs: This entire section is meaningless 2026-01-10 15:59:52 +01:00

bcryptrocks

Nim wrapper over Solar Designer's crypt_blowfish, created as a drop-in replacement for bcryptnim with better Windows compatability as the main goal.

This Nim wrapper library is released under the public domain, if you reside in a legal jurisdiction that doesn't recognize the public domain, then the following fallback license applies:

Copyright (c) 1998-2014 Solar Designer and it is hereby released to the general public under the following terms: Redistribution and use in source and binary forms, with or without modification, are permitted.

TL;DR: Use this however you want.

Here's the original disclaimer from crypt_blowfish.c, with parts not relevant to licensing removed.

/*
 * The crypt_blowfish homepage is:
 *
 *	http://www.openwall.com/crypt/
 *
 * Written by Solar Designer <solar at openwall.com> in 1998-2014.
 * No copyright is claimed, and the software is hereby placed in the public
 * domain.  In case this attempt to disclaim copyright and place the software
 * in the public domain is deemed null and void, then the software is
 * Copyright (c) 1998-2014 Solar Designer and it is hereby released to the
 * general public under the following terms:
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted.
 *
 * There's ABSOLUTELY NO WARRANTY, express or implied.
 *
 * It is my intent that you should be able to use this on your system,
 * as part of a software package, or anywhere else to improve security,
 * ensure compatibility, or for any other purpose.  I would appreciate
 * it if you give credit where it is due and keep your modifications in
 * the public domain as well, but I don't require that in order to let
 * you place this code and any modifications you make under a license
 * of your choice.
*/