| title | titleSuffix | description | author | ms.service | ms.topic | ms.date | ms.author |
|---|---|---|---|---|---|---|---|
How to use the 'blobfuse2 secure' command to encrypt, decrypt, or access settings in a BlobFuse2 configuration file | Azure Storage | Learn how to use the 'blobfuse2 secure' command to encrypt, decrypt, or access settings in a BlobFuse2 configuration file. | akashdubey-ms | azure-blob-storage | how-to | 12/02/2022 | akashdubey |
Use the blobfuse2 secure command to encrypt, decrypt, or access settings in a BlobFuse2 configuration file.
blobfuse2 secure [command] --[flag-name]=[flag-value]
[command]
The supported subcommands for blobfuse2 secure are:
| Command | Description |
|---|---|
| encrypt | Encrypts a BlobFuse2 configuration file |
| decrypt | Decrypts a BlobFuse2 configuration file |
| get | Gets a specified value from an encrypted BlobFuse2 configuration file |
| set | Sets a specified value in an encrypted BlobFuse2 configuration file |
Select one of the command links in the table above to view the documentation for the individual subcommands, including the arguments and flags they support.
Flags that apply to blobfuse2 secure are inherited from the parent command, blobfuse2, or apply only to the blobfuse2 secure subcommands.
The following flags are inherited from parent command blobfuse2:
| Flag | Short version | Value type | Default value | Description |
|---|---|---|---|---|
| disable-version-check | boolean | false | Enables or disables automatic version checking of the BlobFuse2 binaries | |
| help | -h | n/a | n/a | Help info for the blobfuse2 command and subcommands |
The following flags apply only to command blobfuse2 secure:
| 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 Can also be specified by environment variable BLOBFUSE2_SECURE_CONFIG_PASSPHRASE. The key must be 16 (AES-128), 24 (AES-192), or 32 (AES-256) bytes in length. |
For examples, see the documentation for the individual subcommands.
