rage-mount(1)

okay bestie, welcome to rage-mount(1) from the General Commands Manual 💖 this is literally the page for mounting an age encrypted filesystem, and yes we're gonna get into every single detail. no cap.

💅 NAME 💅

rage-mount — mount an age encrypted filesystem. that's the name section, short and iconic ✨

✨ SYNOPSIS ✨

here's the exact call, bestie:

rage-mount [-h|--help] [-V|--version] <-t|--types> [--max-work-factor]
[-i|--identity] <FILENAME> <MOUNTPOINT>

🌸 DESCRIPTION 🌸

okay so rage-mount decrypts the age encrypted filesystem at FILENAME on the fly, and mounts it as a directory on the local filesystem at MOUNTPOINT. that's the whole main character move 🫶

Passphrase-encrypted files are detected automatically and the passphrase is requested interactively. otherwise, one or more IDENTITIES specified with -i/--identity are used to decrypt the file.

ngl this part is a little wild: the previous contents (if any) and owner and mode of MOUNTPOINT become invisible, and as long as this filesystem remains mounted, the pathname MOUNTPOINT refers to the root of the filesystem on FILENAME. periodt 💅

🎀 ARGUMENTS 🎀

• <FILENAME> — the encrypted filesystem to mount. literally the file you're mounting, bestie.
• <MOUNTPOINT> — the directory to mount the filesystem at. that's where it shows up.

🦋 OPTIONS 🦋

• -h, --help — print this help message and exit. your classic "help me help you" moment 🙈
• -V, --version — print version info and exit.
• -t, --types <TYPES> — set the filesystem type. the following types are currently supported: "tar", "zip".

this option is required. rage-mount does not attempt to guess the filesystem format. no guessing games, okay?

in theory, any efficiently-seekable filesystem format can be supported. at present, rage-mount only supports seekable archive formats. iykyk 🧚

• --max-work-factor <WF> — maximum work factor to allow for passphrase decryption. keep it cute, keep it capped ✨
• -i, --identity <IDENTITY> — decrypt using the IDENTITIES at IDENTITY.

IDENTITY may be one of the following:

• a. A file listing IDENTITIES one per line. Empty lines and lines starting with "#" are ignored as comments.
• b. A passphrase encrypted age file, containing IDENTITIES one per line like above. The passphrase is requested interactively. Note that passphrase-protected identity files are not necessary for most use cases, where access to the encrypted identity file implies access to the whole system.
• c. An SSH private key file, in PKCS#1, PKCS#8, or OpenSSH format. If the private key is password-protected, the password is requested interactively only if the SSH identity matches the file. See the SSH keys section for more information, including supported key types.
• d. "-", causing one of the options above to be read from standard input. In this case, the INPUT argument must be specified.

this option can be repeated. Identities are tried in the order in which are provided, and the first one matching one of the file's recipients is used. Unused identities are ignored, but it is an error if the INPUT file is passphrase-encrypted and -i/--identity is specified. that last bit is important, fr fr ⭐

🔥 EXAMPLES 🔥

Mounting an archive encrypted to a recipient:

$ rage-mount -t tar -i key.txt encrypted.tar.age ./tmp

Mounting an archive encrypted with a passphrase:

$ rage-mount -t zip encrypted.zip.age ./tmp
Type passphrase:

🌈 SEE ALSO 🌈

• rage-keygen(1)
• rage(1)

⭐ VERSION ⭐

the version is literally v0.12.1 — periodt.

👑 AUTHORS 👑

Jack Grigg <thestr4d@gmail.com> — iconic author energy 👑

---

okay that's the whole page! this is rage-mount 0.12.1, and the manual page is rage-mount(1). bye bestie, go mount something cute 💖🦋🌸