Encrypting Files
Description
mcli support inspect downloads raw object data and metadata from the server’s underlying drives. PGSTY mcli saves diagnostic archives locally without requiring SUBNET registration or uploading anything automatically. Treat both the archive and its decryption key as sensitive material.
Encryption
Current SILO and mcli releases always encrypt support inspect output (there is no --encrypt flag on the command):
If no user-supplied support_public.pem is present in the client configuration directory, SILO generates a random one-time key and mcli prints the decryption key alongside the downloaded filename. Save that key immediately—it cannot be recovered later, and PGSTY does not embed any vendor decryption key.
If you provide support_public.pem, keep the matching private key safe. Quote paths containing wildcards so the shell passes the pattern directly to mcli. Because recursive inspection can pull object shards from multiple drives, collect only the specific files needed for troubleshooting.
Decryption
Build the inspect decryption utility from the maintained SILO source repository using the Go toolchain version required by that release:
To decrypt an archive using the symmetric key printed during download:
If you omit -key and no private key file is specified, the utility prompts interactively for the decryption key.
To decrypt output encrypted with support_public.pem, pass the matching private key:
With -key, the utility writes a decrypted ZIP archive next to the input file; with -private-key, it extracts the decrypted streams (including inspect.zip) into an output directory. Review the extracted files before sharing them, and note that unwrapping the inspect.enc diagnostic archive does not decrypt objects that are themselves stored with server-side encryption (SSE).