---
- branch: MAIN
  date: Thu Oct 30 03:32:19 UTC 2008
  files:
  - new: 1.1.1.1
    old: '0'
    path: pkgsrc/security/pakchois/Makefile
    pathrev: pkgsrc/security/pakchois/Makefile@1.1.1.1
    type: imported
  - new: 1.1.1.1
    old: '0'
    path: pkgsrc/security/pakchois/PLIST
    pathrev: pkgsrc/security/pakchois/PLIST@1.1.1.1
    type: imported
  - new: 1.1.1.1
    old: '0'
    path: pkgsrc/security/pakchois/distinfo
    pathrev: pkgsrc/security/pakchois/distinfo@1.1.1.1
    type: imported
  - new: 1.1.1.1
    old: '0'
    path: pkgsrc/security/pakchois/DESCR
    pathrev: pkgsrc/security/pakchois/DESCR@1.1.1.1
    type: imported
  - new: 1.1.1.1
    old: '0'
    path: pkgsrc/security/pakchois/buildlink3.mk
    pathrev: pkgsrc/security/pakchois/buildlink3.mk@1.1.1.1
    type: imported
  id: 20081030T033219Z.282778cb98e13972de04a753d880039a4f008076
  log: "Add pakchois-0.4. (upcoming new neon can use it)\n--\n\npakchois is just another
    PKCS#11 wrapper library.  pakchois aims to\nprovide a thin wrapper over the PKCS#11
    interface.\n\nThe goals are:\n\n1) to offer a modern* object-oriented C interface
    wrapper for PKCS#11.\n\n2) to not hide or abstract away any details of the PKCS#11
    interface\nitself except where absolutely necessary.\n\n3) to handle the details
    of loading DSOs\n\n4) to allow the caller to avoid caring about where on the system\nPKCS#11
    modules might be stored, or exactly how they are named.\n\n5) to avoid any dependency
    on a particular cryptography toolkit.\n\nExisting PKCS#11 wrapper libraries solutions
    differ in at least one of\nthe above goals.\n\n*: \"modern\" being a euphemism
    for not using process-global state,\nhaving a sane symbol namespace, etc.\n\nStatus:\n\nVendor
    Tag:\tTNF\nRelease Tags:\tpkgsrc-base\n"
  module: pkgsrc
  subject: 'CVS commit: pkgsrc/security/pakchois'
  unixtime: '1225337539'
  user: bjs