| Name |
Last commit
|
Last update |
|---|---|---|
| bin | ||
| docs/man | ||
| docsite | ||
| examples | ||
| hacking | ||
| lib/ansible | ||
| library | ||
| packaging | ||
| plugins | ||
| test | ||
| .gitignore | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| COPYING | ||
| MANIFEST.in | ||
| Makefile | ||
| README.md | ||
| RELEASES.txt | ||
| VERSION | ||
| setup.py |
This is based somewhat loosely on how Keyczar does things. Their implementation does things in a much more generic way to allow for more variance in how the cipher is created, but since we're only using one key type most of our values are hard-coded. They also add a header to their messages, which I am not doing (don't see the need for it currently).
| Name |
Last commit
|
Last update |
|---|---|---|
| bin | Loading commit data... | |
| docs/man | Loading commit data... | |
| docsite | Loading commit data... | |
| examples | Loading commit data... | |
| hacking | Loading commit data... | |
| lib/ansible | Loading commit data... | |
| library | Loading commit data... | |
| packaging | Loading commit data... | |
| plugins | Loading commit data... | |
| test | Loading commit data... | |
| .gitignore | Loading commit data... | |
| CHANGELOG.md | Loading commit data... | |
| CONTRIBUTING.md | Loading commit data... | |
| COPYING | Loading commit data... | |
| MANIFEST.in | Loading commit data... | |
| Makefile | Loading commit data... | |
| README.md | Loading commit data... | |
| RELEASES.txt | Loading commit data... | |
| VERSION | Loading commit data... | |
| setup.py | Loading commit data... |