This repository has been archived by the owner on Nov 6, 2020. It is now read-only.
Restrict vault.json permssion to owner and using random suffix for temp vault.json file #8932
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In an unlucky situation, multiple process (which may be incorrectly started to run on the same chain) can decide to write to
vault_temp.json
file at the same time, resulting in a corrupted file. We don't protect this in key files right now, but given the original intention to write tovault_temp.json
and then atomically rename tovault.json
is to prevent similar type of thing, I think it would work better to use a random suffix ifvault_temp.json
file already exists.This also restricts newly created
vault.json
file with permission owner only.