Dell PowerVault TL2000 Dell PowerVault ML6000 Encryption Key Manager User's - Page 101

Appendix A. Sample Files, Sample startup daemon script, Linux Platforms, Sample Configuration Files - backup software

Page 101 highlights

Appendix A. Sample Files Sample startup daemon script Attention: It is impossible to overstate the importance of preserving your keystore data. Without access to your keystore you will be unable to decrypt your encrypted tapes. Ensure that you save your keystore and password information. Linux Platforms The following is a sample script that allows EKM to be kicked off in the background, in a proven manner. This script starts EKM and passes the keystore password, keystore_password, in through the script. In this way the keystore password does not have to be in the EKM Configuration file. (see note below). The following should be contained in the script file: java com.ibm.keymanager.KMSAdminCmd KeyManagerConfig.properties

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122

Appendix A. Sample Files
Sample startup daemon script
Attention:
It is impossible to overstate the importance of
preserving your keystore data. Without access to your keystore
you will be unable to decrypt your encrypted tapes. Ensure that
you save your keystore and password information.
Linux Platforms
The following is a sample script that allows EKM to be kicked off in the
background, in a proven manner. This script starts EKM and passes the keystore
password,
keystore_password
, in through the script. In this way the keystore
password does not have to be in the EKM Configuration file. (see note below). The
following should be contained in the script file:
java com.ibm.keymanager.KMSAdminCmd KeyManagerConfig.properties <<EOF
startekm
keystore_password
status
EOF
Note:
If the keystore password is entered into EKM through a script, (that is, the
EKM config file does not contain the keystore password), then when the
EKM is backed up, the files (configuration file, drive table, and keystore
backup file) need not necessarily be treated as secret, but the script that
contains the keystore password
must
be stored securely and resiliently (for
example, multiple copies in multiple locations). The keystore password is
confidential information and must be treated as such. Backing up the script
file securely has the same options that exist for backing up the configuration
file that contains the keystore password. But the scripts might be backed up
and stored/transmitted secretly and separately from the EKM backup files,
which would add a level of indirection for security. Finally, we must
emphasize that however the keystore password is stored (in a script or in
EKM’s configuration file), it must be stored securely and resiliently, such
that the keystore password can always be recovered.
Loss of all copies of
the keystore password would cause loss of all of the keys in the keystore
and there is no recovery path for this
.
Sample Configuration Files
The following is a sample EKM properties file with all of the keystore entries
pointing to the same software keystore:
Admin.ssl.keystore.name = /keymanager/testkeys
Admin.ssl.keystore.type = jceks
Admin.ssl.truststore.name = /keymanager/testkeys
Admin.ssl.truststore.type = jceks
Audit.event.outcome = success,failure
Audit.event.types = all
Audit.eventQueue.max = 0
Audit.handler.file.directory = /keymanager/audit
Audit.handler.file.name = kms_audit.log
Audit.handler.file.size = 10000
Audit.metadata.file.name = /keymanager/metafile.xml
A-1