RIPASSO-CURSIVE(1)

πŸ’– RIPASSO-CURSIVE(1) πŸ’–

okay bestie, gather round, because this one is actually iconic: ripasso-cursive is a password manager that speaks the exact same file format as the standard unix password manager pass β€” except it's written in rust πŸ¦€βœ¨


✨ NAME ✨

ripasso-cursive β€” a password manager that uses the file format of the standard unix password manager pass, implemented in rust. no cap.


🌸 SYNOPSIS 🌸

ripasso-cursive [FLAGS]

πŸŽ€ DESCRIPTION πŸŽ€

ripasso-cursive is a curses application that lets you manage your passwords or your team's passwords. The passwords are encrypted with pgp, and optionally stored in an git repository. The list of team members lives in the file .gpg-id, with one pgp key id per line. it's giving secure, it's giving collaborative, it's giving main character energy πŸ’…


πŸ¦‹ FLAGS πŸ¦‹

  • -h, --help β€” print a help text. that's it, that's the flag 🫢

πŸ’… KEYBOARD SHORTCUTS πŸ’…

  • Enter β€” copy the current selected password to the copy buffer for 40 seconds ⏳
  • Delete β€” delete the marked password 😭 (rip bozo)
  • Insert β€” create a new password entry ✨
  • Control + y β€” same as Enter
  • Control + b β€” if the password has an otpauth:// url in it, generate a code and store it in the copy buffer πŸ”
  • Control + n β€” move marker down ⬇️
  • Control + p β€” move marker up ⬆️
  • Control + r β€” rename the password without changing it's content ✏️
  • Control + u β€” copy the filename of the password πŸ“‹
  • Control + h β€” show the git history of the password πŸ•°οΈ
  • Control + v β€” view the list of team members πŸ‘₯
  • Control + o β€” open a password edit dialog πŸ“
  • Control + f β€” pull from the git repository ⬇️
  • Control + g β€” push to the git repository ⬆️
  • Escape β€” quit πŸ‘‹

🌈 USAGE NOTE 🌈

ripasso-cursive reads $HOME/.password-store/ by default, bestie. override this by setting the PASSWORD_STORE_DIR environmental variable.

If you specify the PASSWORD_STORE_SIGNING_KEY environmental variable, then ripasso will verify that the .gpg-id file is correctly signed. Valid values are one or more 40 character pgp fingerprints, separated by commas.


πŸ“ CONFIG FILE πŸ“

ripasso reads configuration from $XDG_CONFIG_HOME/ripasso/settings.toml

Example config file:

[stores]

  [stores.default]

    path = "/home/user/.password-store/"

    valid_signing_keys = "AF77DAC5B3882EAD316B7312D5B659E1D2FDF0C3"

  [stores.work]

    path = "/home/user/.work_pass/"

    style_path = "/home/user/.config/ripasso/work-style.toml"

Valid settings for a store are:

  • path β€” this is the root path to the password store directory πŸ“‚
  • valid_signing_keys β€” this setting corresponds to the PASSWORD_STORE_SIGNING_KEY environmental variable
  • style_path β€” color and style information for the store. different stores can have different styles and they will change when you switch store 🎨 Documentation on the format can be found here https://docs.rs/cursive_core/0.1.1/cursive_core/theme/index.html
  • pgp β€” the pgp implementation to use for the store, valid values are gpg or sequoia
  • own_fingerprint β€” if the pgp option is set to sequoia, ripasso needs to know the fingerprint of your own key in order to communicate with gpg-agent πŸ”‘

⭐ EXIT STATUS ⭐

  1. 0 β€” Successful program execution. slay πŸ’–
  2. 1 β€” Unsuccessful program execution. πŸ™ˆ
  3. 101 β€” The program panicked. πŸ’€

πŸ‘‘ AUTHORS πŸ‘‘

  • Joakim Lundborg <joakim.lundborg@gmail.com>
  • Alexander KjΓ€ll <alexander.kjall@gmail.com>

and that's the whole vibe, bestie 🧚✨ this page came to you straight out of the General Commands Manual β€” it's RIPASSO-CURSIVE(1), and yes, the header said exactly that at the top too. go forth and manage those passwords, you absolute icon πŸ«ΆπŸ’œ