From 3ff93efacd865d49497da3347fc62d8dc6e34c36 Mon Sep 17 00:00:00 2001 From: Dmytrol <46675332+Dimitrolito@users.noreply.github.com> Date: Fri, 29 Nov 2024 17:08:41 +0200 Subject: [PATCH] typos rules.md --- cmd/clef/rules.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/cmd/clef/rules.md b/cmd/clef/rules.md index cc4a645596..8f0a72217f 100644 --- a/cmd/clef/rules.md +++ b/cmd/clef/rules.md @@ -83,7 +83,7 @@ Some security precautions can be made, such as: * Never load `ruleset.js` unless the file is `readonly` (`r-??-??-?`). If the user wishes to modify the ruleset, he must make it writeable and then set back to readonly. * This is to prevent attacks where files are dropped on the users disk. -* Since we're going to have to have some form of secure storage (not defined in this section), we could also store the `sha3` of the `ruleset.js` file in there. +* Since we're going to have some form of secure storage (not defined in this section), we could also store the `sha3` of the `ruleset.js` file in there. * If the user wishes to modify the ruleset, he'd then have to perform e.g. `signer --attest /path/to/ruleset --credential ` ##### Security of implementation