Home

Sysadm read-me:

See: README.md

---

Dev read-me:

How-to set-up development environment:

Please use _dev environment when developing so I can accept your pull request, further reading here: http://wiki.zimbra.com/wiki/Zimlet_Developers_Guide:Dev_Environment_Setup#Zimlet_Development_Directory

First make sure to undeploy OpenPGP Zimlet if you installed it before using zmzimletctl:

  su zimbra
  zmzimletctl undeploy tk_barrydegraaff_zimbra_openpgp

Then as root:

  cd /tmp
  rm pgp-zimlet -Rf
  git clone https://github.com/barrydegraaff/pgp-zimlet
  cd pgp-zimlet
  ./install-dev.sh

Building OpenPGP.js

We use a non-minified version that is build from source using dist/openpgp.js this is done so we can track changes of OpenPGP.js in our own Github and avoid issues with Zimbra Javascript optimizer:

To build new version: npm install && npm test

Pre-build binaries

Pre-build binaries are put in the binaries Github: https://github.com/barrydegraaff/pgp-zimlet-binaries

The pre-build zip binaries contain all the files needed to run the Zimlet (no documentation videos and test files). Also pay attention that script files in the zip have '_dev/' removed from url's, so you cannot unzip and paste these pre-build zip binaries back to _dev environment.

GPG-CLI Integration:

If you created the Key-pair with the Zimlet (which you have to do coz the one created with gpg did not work)

save your private key in a file and

gpg --imort file....

copy pub-key also in a file and

gpg --allow-non-selfsigned-uid --import file...

than sign your own key and maybe make him primary and finally upload it to a key server.

adjust add setings with gpg --edit-key