Switch branches/tags
Nothing to show
Commits on Dec 15, 2016
  1. Merge pull request #3 from marramgrass/link-crypt

    Don't use -lcrypt on OS X
    committed on GitHub Dec 15, 2016
  2. Don't use -lcrypt on OS X

    OS X doesn't require -lcrypt, and the build fails
    with it. The crypt function is in the system C library.
    for an old, old reference.
    marramgrass committed Dec 15, 2016
Commits on Dec 14, 2016
  1. makefile: add lint target

    committed Dec 14, 2016
Commits on Nov 27, 2016
  1. makefile: add typer target

    committed Nov 27, 2016
Commits on Nov 26, 2016
  1. makefile: mark targets as phony

    committed Nov 26, 2016
Commits on Nov 5, 2016
  1. Use elvis syntax checks

    committed Nov 5, 2016
Commits on Oct 9, 2016
Commits on Aug 6, 2016
  1. Use rebar3

    committed Aug 6, 2016
Commits on Mar 14, 2016
  1. Move to common test

    committed Mar 14, 2016
Commits on Jan 8, 2015
  1. Fix build on Solaris

    committed Jan 8, 2015
Commits on Aug 5, 2014
  1. Remove autoconf

    autoconf support is awesome but unfortunately still required manually
    changing rebar.config. Hardcode flags in rebar.config. If an OS supports
    crypt_r(), then it will have to be added to the pattern match before
    committed Aug 5, 2014
Commits on Aug 4, 2014
  1. Fix compiling on OpenBSD

    OpenBSD, unlike FreeBSD and NetBSD, does not require -lcrypt. Issue a
    warning only if libcrypt is not found.
    On platforms that do not support crypt_r, do not require linking with
    committed Aug 4, 2014
  2. tests: run on freebsd

    committed Aug 4, 2014
  3. Use iolists as arguments to crypt/2

    Simplify the code by accepting iolists as arguments to crypt. The
    behaviour of crypt/2 has been changed to always return a binary, rather
    than a string.
    A new function, crypt_to_string/2, will return the output of crypt as a
    string. The naming follows the base64 module.
    On memory allocation failures, the NIF will crash the calling process
    rather than returning an error.
    committed Aug 4, 2014
  4. Merge pull request #2 from snar/nif_locking

    Nif locking: thread-safety on platforms lacking crypt_r
    committed Aug 4, 2014
Commits on Jul 18, 2014
  1. Merge pull request #1 from jcomellas/jc-crypt_r

    Add support for crypt_r() to make the library thread-safe
    committed Jul 18, 2014
  2. Add support for crypt_r() to make the library thread-safe

    - Add support for binaries as key and password.
    - Make the buffers used for key and password dynamic by using alloca()
    - Remove local crypt.h header to avoid collisions with system header
    - Add conditional compilation arguments to compile on non-thread-safe
      environments (i.e. Mac OS X)
    - Update version to 0.3.0
    jcomellas committed Jul 18, 2014
Commits on Dec 10, 2013
  1. Use semver format

    committed Dec 10, 2013
Commits on Dec 8, 2013
  1. rebar: update URL

    committed Dec 8, 2013
  2. Use semver format

    committed Dec 8, 2013
Commits on Dec 6, 2013
  1. rebar: generate app file

    committed Dec 6, 2013
Commits on Dec 5, 2013
  1. Check for undefined funs

    committed Dec 5, 2013
Commits on Nov 13, 2013
Commits on Mar 14, 2012
  1. Fix error handling

    The behaviour on error of crypt(3) is tricky. The only real error it can
    return is {error,enosys} on platforms not supporting it (the old
    implementation would have returned {error, {crypt, "enosys"}}).
    Change the behaviour of the module to test for NULL before loading. If
    there is any error, there is no point loading the library.
    In the event of an error, the crypt implementation may choose to return
    NULL (crypt/2 will throw a bad arg exception) or return a fixed string
    (the caller will need to check for this case if it is a concern).
    committed Mar 14, 2012
  2. Figure out path to shared lib

    committed Mar 14, 2012