Use the [Verifying Keyserver Interface Client](https://crates.io/crates/vks-client) and implement the automation user stories in [this Epic](https://codeberg.org/pEp/pEpEngine/wiki/EpicStandardKeyserver)
- Zig 82.9%
- C 17.1%
| src | move buffer from stack to heap | |
| .gitignore | clean allocate and set to 0 | |
| build.zig | explicitly link against the libc | |
| build.zig.zon | bump version number | |
| LICENSE | Initial commit | |
| README.md | correcting README | |
Library vks_automation
Use the Verifying Keyserver Interface Client and implement the automation user stories in this Epic
Build
To build give the prefix, where it searches for the two libraries it depends on
(pEpEngine and vks_client) – in this example, they’re installed in $HOME
zig build --search-prefix $HOME
To install give the prefix, where it has to install it
zig build --search-prefix $HOME --prefix $HOME install
To build the documentation use:
zig build --search-prefix $HOME docs
Usage in p≡p apps
To use this in p≡p apps there are four things to implement:
When Account settings change
After Account settings change call:
vks_update_keys_of_own_identities(session);
When a message goes out
When p≡p Sync updates keys or a user message goes out then myself() was called; after that call:
vks_update_keys_of_own_identities(session);
When a message comes in
If a verification mail from keyserver@keys.openpgp.org arrives call:
vks_deliver_verification_mail_async(own_address, maildata);
When the user clicks "Search Keyserver" on an identity
vks_retrieve_key_for_identity(session, identity);
In an outgoing mail draft when an identity is not at least yellow
vks_update_identity_if_key_from_keyserver(session, identity);
This does nothing if the former key was not downloaded, too.