arangodump Options
Encryption
Name | Type | Description |
---|---|---|
encryption.key-generator | string | Enterprise Edition only Program providing the encryption key on stdout. If set, encryption will be enabled. Default: “” |
encryption.keyfile | string | Enterprise Edition only File containing the encryption key. If set, encryption will be enabled. Default: “” |
Random
Name | Type | Description |
---|---|---|
random.generator | uint32 | Random number generator to use (1 = MERSENNE, 2 = RANDOM, 3 = URANDOM, 4 = COMBINED (not for Windows), 5 = WinCrypt (Windows only) Default: 1 Possible values: 1, 2, 3, 4 |
SSL
Name | Type | Description |
---|---|---|
ssl.protocol | uint64 | Ssl protocol (1 = SSLv2 (unsupported), 2 = SSLv2 or SSLv3 (negotiated), 3 = SSLv3, 4 = TLSv1, 5 = TLSv1.2, 6 = TLSv1.3, 9 = generic TLS) Default: 5 Possible values: 1, 2, 3, 4, 5, 6, 9 |
Dump encryption is only available in the , including ArangoDB Oasis.
The file path-to-keyfile
must contain the encryption key. This file must be secured, so that only arangodump
or arangorestore
can access it. You should also ensure that in case someone steals your hardware, they will not be able to read the file. For example, by encrypting /mytmpfs
or creating an in-memory file-system under /mytmpfs
. The encryption keyfile must contain 32 bytes of data.
This output is used if you want to use the program to generate your encryption key. The program must output the encryption on standard output and exit. The encryption keyfile must contain 32 bytes of data.