Events
19 May, 6 pm - 23 May, 12 am
Calling all developers, creators, and AI innovators to join us in Seattle @Microsoft Build May 19-22.
Register todayThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Use the blobfuse2 secure encrypt
command to encrypt a BlobFuse2 configuration file.
blobfuse2 secure encrypt --[flag-name]=[flag-value]
Flags that apply to blobfuse2 secure encrypt
are inherited from the grandparent command, blobfuse2
, or apply only to the blobfuse2 secure
subcommands.
The following flags are inherited from grandparent 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 | Help info for the blobfuse2 command and subcommands |
The following flags are inherited from parent 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. |
Note
The following examples assume you have already created a configuration file in the current directory.
Encrypt a BlobFuse2 configuration file using a passphrase:
blobfuse2 secure encrypt --config-file=./config.yaml --passphrase=PASSPHRASE
Events
19 May, 6 pm - 23 May, 12 am
Calling all developers, creators, and AI innovators to join us in Seattle @Microsoft Build May 19-22.
Register today