Replace chinese double quotes to English double quotes
Change-Id: I18e9b7afe00ee971c74799bc4db979c8d8602783
This commit is contained in:
parent
fa77c7fc0a
commit
064314998c
|
@ -21,18 +21,18 @@ This is the same behaviour as if the volume_clear = ‘none’ option was
|
|||
selected. This could let an attacker recover data from a volume that was
|
||||
intended to be securely erased. Examples of possible incorrect
|
||||
configuration options include values that would appear to result in a
|
||||
secure erase, for example “volume_clear = true” or “volume_clear =
|
||||
yes”.
|
||||
secure erase, for example "volume_clear = true" or "volume_clear =
|
||||
yes".
|
||||
|
||||
In the event of a misconfiguration resulting in this issue, the message
|
||||
“Error unrecognized volume_clear option” should be present in log
|
||||
"Error unrecognized volume_clear option" should be present in log
|
||||
files.
|
||||
|
||||
### Recommended Actions ###
|
||||
- Create and clear a volume (cinder create --display_name erasetest 10;
|
||||
cinder delete erasetest)
|
||||
- Review log files for the above error message (grep “Error unrecognized
|
||||
volume_clear option” <logfile>)
|
||||
- Review log files for the above error message (grep "Error unrecognized
|
||||
volume_clear option" <logfile>)
|
||||
- Review configuration files to ensure that the valid options ‘zero’ or
|
||||
‘shred’ are specified.
|
||||
|
||||
|
|
Loading…
Reference in New Issue