| 1 |
CLEVIS-ENCRYPT-FILE(1) |
| 2 |
====================== |
| 3 |
:doctype: manpage |
| 4 |
|
| 5 |
|
| 6 |
== NAME |
| 7 |
|
| 8 |
clevis-encrypt-file - Encrypts using a file policy |
| 9 |
|
| 10 |
== SYNOPSIS |
| 11 |
|
| 12 |
*clevis encrypt file* CONFIG < PT > JWE |
| 13 |
|
| 14 |
== OVERVIEW |
| 15 |
|
| 16 |
The *clevis encrypt file* command encrypts using a file policy. |
| 17 |
Its only argument is the JSON configuration object. |
| 18 |
|
| 19 |
Encrypting data using the file pin works like this: |
| 20 |
|
| 21 |
$ clevis encrypt file '{"name":"/path/to/file"}' < PT > JWE |
| 22 |
|
| 23 |
The given file must not exist yet. |
| 24 |
|
| 25 |
To decrypt the data, just pass it to the *clevis decrypt* command: |
| 26 |
|
| 27 |
$ clevis decrypt < JWE > PT |
| 28 |
|
| 29 |
== CONFIG |
| 30 |
|
| 31 |
This command uses the following configuration properties: |
| 32 |
|
| 33 |
* *name* (string) : |
| 34 |
The name to the file where the jwk is stored (REQUIRED) |
| 35 |
|
| 36 |
== BUGS |
| 37 |
|
| 38 |
Requires that directories for that file already exist. |
| 39 |
|
| 40 |
Rather for educational purposes. |
| 41 |
|
| 42 |
== SEE ALSO |
| 43 |
|
| 44 |
link:clevis-decrypt.1.adoc[*clevis-decrypt*(1)] |