keepasshttp-objc exposes a KeePass client via HTTP. To implement this functionality, a developer needs to do the following.
- Implement the protocol defined in KPHKeePassClient
- Pass that implementation into a new instance of KPHServer
The server handles all network communication, and the KeePassClient leaves the heavy lifting to a KeePass compatible client (such as MacPass).
Testing changes to keepasshttp-objc against a browser requires a few steps. These methods return either plugin to a blank state.
- Delete all saved databases from the plguin admin page
- Reload the plugin
- Disable the plugin
- Restart the browser
- Delete the saved key from the password manager
- Enable the plugin
- Restart the browser
| Name | Purpose | Link |
|---|---|---|
| Mono | Used as a reference for partial .NET reimplementations | https://github.com/mono/mono/tree/master/mcs/class/corlib/System |
| KeePass GitLab Mirror | Original project is hosted as a zipped source archive. This is easier to navigate | https://github.com/dlech/keepass2 |
| KeePassHttp Plugins Repo | What this project interfaces with | https://github.com/pfn/passifox/ |
| KeePassHttp Repo | What is being rebuilt in Obj-C. A fork of kph, with better URL matching | https://github.com/mpern/keepasshttp |
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent