Skip to content

Update blobfuse2-commands-secure-encrypt.md #124838

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update blobfuse2-commands-secure-encrypt.md #124838

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions articles/storage/blobs/blobfuse2-commands-secure-encrypt.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,17 +37,17 @@ The following flags are inherited from parent command [`blobfuse2 secure`](blobf
| Flag | Value type | Default value | Description |
|--|--|--|--|
| config-file | string | ./config.yaml | The path configuration file |
| output-file | string | | Path and name for the output file |
| passphrase | string | | The Key to be used for encryption or decryption<br />Can also be specified by environment variable BLOBFUSE2_SECURE_CONFIG_PASSPHRASE.<br />The key must be 16 (AES-128), 24 (AES-192), or 32 (AES-256) bytes in length. |
| output-file | string | $HOME/.blobfuse2/{configFileName}.azsec | Path and name for the output file |
| passphrase | string | | The Key to be used for encryption or decryption<br />Can also be specified by environment variable BLOBFUSE2_SECURE_CONFIG_PASSPHRASE.<br />The key must be 16 (AES-128), 24 (AES-192), or 32 (AES-256) bytes in length. |

## Examples

> [!NOTE]
> The following examples assume you have already created a configuration file in the current directory.
> The following examples assume you have already created a configuration file in the current directory. Additionally, once the encrypted configuration file is created, the original configuration file is deleted and it is replaced by the new encrypted configuration file.

Encrypt a BlobFuse2 configuration file using a passphrase:

`blobfuse2 secure encrypt --config-file=./config.yaml --passphrase=PASSPHRASE`
`blobfuse2 secure encrypt --config-file=./config.yaml --passphrase=PASSPHRASESAMPLE --output-file=./encryptedconfig.yaml`

## See also

Expand Down