{"action":"created","issue":{"url":"https://api.github.com/repos/barrydegraaff/pgp-zimlet/issues/52","labels_url":"https://api.github.com/repos/barrydegraaff/pgp-zimlet/issues/52/labels{/name}","comments_url":"https://api.github.com/repos/barrydegraaff/pgp-zimlet/issues/52/comments","events_url":"https://api.github.com/repos/barrydegraaff/pgp-zimlet/issues/52/events","html_url":"https://github.com/barrydegraaff/pgp-zimlet/issues/52","id":53455144,"number":52,"title":"Support a global (admin-managed) public key store","user":{"login":"voretaq7","id":184910,"avatar_url":"https://avatars.githubusercontent.com/u/184910?v=3","gravatar_id":"","url":"https://api.github.com/users/voretaq7","html_url":"https://github.com/voretaq7","followers_url":"https://api.github.com/users/voretaq7/followers","following_url":"https://api.github.com/users/voretaq7/following{/other_user}","gists_url":"https://api.github.com/users/voretaq7/gists{/gist_id}","starred_url":"https://api.github.com/users/voretaq7/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/voretaq7/subscriptions","organizations_url":"https://api.github.com/users/voretaq7/orgs","repos_url":"https://api.github.com/users/voretaq7/repos","events_url":"https://api.github.com/users/voretaq7/events{/privacy}","received_events_url":"https://api.github.com/users/voretaq7/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-01-05T22:15:56Z","updated_at":"2015-01-07T06:23:48Z","closed_at":"2015-01-06T08:25:17Z","body":"For some organizations it may be desirable to have a global list of public keys available to every user (for example, a \"corporate keychain\" containing all the known users in a company and their current/verified keys).\r\n\r\nThere are some hints as to how this may be possible using Zimlet Configuration templates (config_template.xml) & the getConfigProperty() method as described here: http://wiki.zimbra.com/wiki/Zimlet_Configuration_File\r\n\r\n(I've tried this briefly but only succeeded in breaking the zimlet - Opening this issue in case someone else feels motivated before I get around to looking at this again.)"},"comment":{"url":"https://api.github.com/repos/barrydegraaff/pgp-zimlet/issues/comments/68983828","html_url":"https://github.com/barrydegraaff/pgp-zimlet/issues/52#issuecomment-68983828","issue_url":"https://api.github.com/repos/barrydegraaff/pgp-zimlet/issues/52","id":68983828,"user":{"login":"barrydegraaff","id":4353213,"avatar_url":"https://avatars.githubusercontent.com/u/4353213?v=3","gravatar_id":"","url":"https://api.github.com/users/barrydegraaff","html_url":"https://github.com/barrydegraaff","followers_url":"https://api.github.com/users/barrydegraaff/followers","following_url":"https://api.github.com/users/barrydegraaff/following{/other_user}","gists_url":"https://api.github.com/users/barrydegraaff/gists{/gist_id}","starred_url":"https://api.github.com/users/barrydegraaff/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/barrydegraaff/subscriptions","organizations_url":"https://api.github.com/users/barrydegraaff/orgs","repos_url":"https://api.github.com/users/barrydegraaff/repos","events_url":"https://api.github.com/users/barrydegraaff/events{/privacy}","received_events_url":"https://api.github.com/users/barrydegraaff/received_events","type":"User","site_admin":false},"created_at":"2015-01-07T06:23:48Z","updated_at":"2015-01-07T06:23:48Z","body":"The dirty way of setting 128K of (the same) data for each user would be using zmprov like:\r\nzmprov ma user1 +zimbraZimletUserProperties \"com_company_testing:favoriteColor:blue\"\r\n\r\nAlso change:\r\nnano /opt/zimbra/conf/attrs/zimbra-attrs.xml\r\nFind the line:\r\nname=\"zimbraZimletUserProperties\" type=\"cstring\" max=\"5120\"\r\nand change it to\r\nname=\"zimbraZimletUserProperties\" type=\"cstring\" max=\"15120\"\r\n\r\nThen make on of the users pubkeys read-only for the user.\r\n\r\nAll the above is NOT a good idea, also with the amount of keys you are talking about\r\nthe zimlet should be re-written to handle public keys more targeted. Right now\r\nit just trows together all 40 and iterate trough them... this will become too slow\r\nfor what you are doing. So if will have to do a lookup based on for example\r\nthe email-address. Avoiding using keys that are not necessary.\r\n\r\nMaybe you can use the GAL?\r\n\r\nOtherwise the keyserver lookup may be the best way to g.\r\n"}}