This guide walks you through the core rskey workflow: generating a key file, encrypting a sensitive value, and confirming the key with its fingerprint. The examples use Posit Package Manager paths, but the same steps apply to Connect and Workbench — swap the key file path and anyDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/rstudio/rskey/llms.txt
Use this file to discover all available pages before exploring further.
--mode flag as needed.
Install rskey
Download a binary release for your platform or install with Go. See the installation guide for full instructions.Confirm the installation:
Generate a key
Use If you want to inspect the key or pipe it elsewhere, omit The key is 512 hex-encoded, securely-generated random bytes — equivalent to
rskey generate to create a new key file. Pass -o to write directly to a file instead of standard output. The command sets file permissions to 0600 automatically.-o and the key is written to standard output instead:openssl rand -hex 512.Encrypt a value
Use Copy the output and paste it into your product’s configuration file.To encrypt multiple values non-interactively, pass them as newline-separated lines on standard input:rskey outputs one encrypted value per line, in the same order as the input.
rskey encrypt with -f pointing to your key file. When you run the command interactively, rskey prompts you to type the sensitive value twice (input is not echoed to the terminal):Verify with fingerprint
Use The default fingerprint algorithm is SHA-256. For Workbench keys, rskey uses CRC-32 to match the fingerprint format Workbench records in its logs.
rskey fingerprint to print a short identifier for the key file. Posit products log this fingerprint when they load a key, so you can use it to confirm that the product is using the correct key.What’s next?
- Posit Connect
- Package Manager
- Workbench
- FIPS mode
Posit Connect guide
Learn how to generate keys, encrypt configuration values, and reference encrypted secrets in
rstudio-connect.gcfg for Connect deployments.