0.5.4

fixes an issue with .gpg-id creation.

0.5.3

fixes an issue with .gpg-id creation

0.5.2

commands

init, generate, insert, rm added.

so, set alias like

▶ alias pass="leeloo"

and 👍

0.5.1

"wrapping" commands support now -c and -k options.

0.5.0

New features are available 🎅

• export allows to extract all secrets to a plain text file. (useful for interoperability)
• key manages peoples allowing to read secrets. (grain fined feature to add/remove people on your organisation)

0.4.1 - Support of Ruby 3

works well with Ruby 3

0.4.0

• huge refactoring with MVC pattern
• ability to share a secret with someone who doesn't have leeloo installed.

To do so,

$> leeloo share my_secret
MY_TOKEN

Generates a token.

Run now

$> ssh -R 80:localhost:8000 ssh.localhost.run
Connect to http://sylvek-annn.localhost.run or https://sylvek-annn.localhost.run

Now, open this url => https://sylvek-annn.localhost.run?q=my_secret and enjoy :)

0.3.0

We can remove a keystore 👍

$> leeloo keystore remove my-old-keystore

(The keystore is not deleted, only removed from database)

0.2.0

it's now possible to search a secret by pattern.

$> leeloo search my_pattern
# will return a list of secret matching the "my_pattern"

the pattern is case insensitive but can not contain wildcard like * ?, etc.

0.1.0

The main goal of this release is to start futures features easily.

Current features are same as 0.0.x version.
I added copy/paste timeout (30s) and translate command.
This command allows to translate stdin (like a file) containing ${path/to/secret} to a file with the current secret.
I should be useful for contextual vars file (dev/qa/prod, etc..). Ex. leeloo translate --keystore production < env.vars > env.prod

---

Preferences contains Keystores list and knows the Keystore used by default. It loads the current configuration by reading files from ~/.leeloo directory.

Keystore contains a list of Secrets, a cypher and a version control policy. A Keystore can be stored on a local filesystem but also can use a GPG cypher. At last, Keystore can use GIT version control.

Secret contains your own secret, according to cypher policy.

Output allows to display Keystore and Secret.

Command allows to interact with you.