1. 29 Aug, 2015 4 commits
  2. 23 Aug, 2015 1 commit
    • Jesper Louis Andersen's avatar
      Simplify the code base, first round: · a135bce9
      Jesper Louis Andersen authored
      * Introduce enacl:verify/0 to verify the integrity of the library.
      * Always run keypair functions on the dirty schedulers.
      * Do not call NIFs when creating zerobytes. Avoid constructing new binary data, but reuse a constant.
      * The box/box_open and box_seal/box_seal_open API is so expensive to call there is little overhead in
        running it on the DS always.
      a135bce9
  3. 14 Aug, 2015 1 commit
    • Jesper Louis Andersen's avatar
      Fix box_seal/2 and box_seal_open/3. · f444d1e4
      Jesper Louis Andersen authored
      * Call the functions `box_seal` and `box_seal_open` to match the libsodium names in module `enacl`.
      * Fix a bug in the C NIF: We should fail if the input is `<` SEALBYTES but not on `<=` SEALBYTES. The latter made it impossible to encode empty messages.
      * Add variants which run directly on the interpreter scheduler for small messages.
      
      Also:
      
      * Provide full EQC functions for the testing purposes. This generated around 13000 random test cases in a 5 minute run, all passing.# Please enter the commit message for your changes. Lines starting
      f444d1e4
  4. 12 Aug, 2015 1 commit
  5. 09 Aug, 2015 1 commit
  6. 06 Aug, 2015 1 commit
  7. 26 Jul, 2015 2 commits
  8. 02 Apr, 2015 1 commit
  9. 22 Feb, 2015 1 commit
  10. 21 Feb, 2015 2 commits
  11. 18 Dec, 2014 1 commit
    • Jesper Louis Andersen's avatar
      Improve the documentation of the project. · 50b00583
      Jesper Louis Andersen authored
      Go over the README file, and improve its contents. Add a Usage/hints section
      with some helpful hints on how to use the library in turn. Also while here, make
      sure that `rebar doc` works as expected and fix every documentation bug in
      the EDoc sections, so it compiles and works. Verify the documentation output
      is nice-looking while at it.
      50b00583
  12. 17 Dec, 2014 3 commits
  13. 16 Dec, 2014 2 commits
  14. 13 Dec, 2014 1 commit
  15. 12 Dec, 2014 1 commit
  16. 08 Dec, 2014 1 commit
  17. 29 Nov, 2014 3 commits
  18. 28 Nov, 2014 2 commits
  19. 26 Nov, 2014 4 commits
  20. 25 Nov, 2014 4 commits
  21. 22 Nov, 2014 1 commit
    • Jesper Louis Andersen's avatar
      Introduce negative testing. · d3471348
      Jesper Louis Andersen authored
      Negative testing means we inject faulty data into the test now and then. When this happens, we make sure the SUT will
      return some kind of badarg error for bad arguments. This means we should make sure things actually work out as they should.
      
      As a side-effect, this can also be used to test for memory leaks. If run for a while, it makes sure there are no leaks in the code base,
      and it probably also makes sure there are no ways to crash the server by any means of use of these NIFs. As such, it looks like the
      NIFs are fairly stable.
      d3471348
  22. 21 Nov, 2014 2 commits