---
- branch: MAIN
  date: Sat Mar 16 09:17:09 UTC 2019
  files:
  - new: '1.1'
    old: '0'
    path: pkgsrc/security/monocypher/DESCR
    pathrev: pkgsrc/security/monocypher/DESCR@1.1
    type: added
  - new: '1.1'
    old: '0'
    path: pkgsrc/security/monocypher/Makefile
    pathrev: pkgsrc/security/monocypher/Makefile@1.1
    type: added
  - new: '1.1'
    old: '0'
    path: pkgsrc/security/monocypher/PLIST
    pathrev: pkgsrc/security/monocypher/PLIST@1.1
    type: added
  - new: '1.1'
    old: '0'
    path: pkgsrc/security/monocypher/buildlink3.mk
    pathrev: pkgsrc/security/monocypher/buildlink3.mk@1.1
    type: added
  - new: '1.1'
    old: '0'
    path: pkgsrc/security/monocypher/distinfo
    pathrev: pkgsrc/security/monocypher/distinfo@1.1
    type: added
  - new: '1.1'
    old: '0'
    path: pkgsrc/security/monocypher/patches/patch-makefile
    pathrev: pkgsrc/security/monocypher/patches/patch-makefile@1.1
    type: added
  id: 20190316T091709Z.dd11e70c4bdb96f211a45a424886099bcee18728
  log: |
    Add monocypher version 2.0.5

    Monocypher is an easy to use crypto library. It is:

    - Small. Sloccount counts about 1700 lines of code, small enough to
    allow audits. The binaries are under 65KB.
    = Easy to deploy. Just add monocypher.c and monocypher.h to your
    project. They compile as C99 or C++, have no dependency, and
    are dedicated to the public domain.
    - Easy to use. The API is small, consistent, and cannot fail
    on correct input.
    - Fast. The primitives are fast to begin with, and performance
    wasn't needlessly sacrificed. Monocypher holds up pretty well
    against Libsodium, despite being closer in size to TweetNaCl.
  module: pkgsrc
  subject: 'CVS commit: pkgsrc/security/monocypher'
  unixtime: '1552727829'
  user: maya