From bdbe21166c9dabf3ffd10e31b19b608d00ff6041 Mon Sep 17 00:00:00 2001 From: Jet Hughes Date: Fri, 2 Dec 2022 15:07:37 +1300 Subject: [PATCH] vault backup: 2022-12-02 15:07:37 --- content/notes/think-writing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/notes/think-writing.md b/content/notes/think-writing.md index 69b242eb1..f4d228946 100644 --- a/content/notes/think-writing.md +++ b/content/notes/think-writing.md @@ -412,4 +412,4 @@ The SWIPL notebook is working. just need to change the version of pyswip back to If someone uploads a document by accident that is sensitive, then the chain hard forks to remove it from the history, is it still publicly available (to the members of chain) or is the old fork erased. bu then what if someone stored a local copy (which they do). maybe the local copy is stored encrypted and the owner of the document has the key to unlock it. **Scenario 4** -what if someone found a security vulnerability in the code. would they exploit it? how to change the code. would there be a different process to normal code changes for something critical like this. +what if someone found a security vulnerability in the code. would they exploit it? how to change the code. would there be a different process to normal code changes for something critical like this. within the blockchain wallets/accounts are linked to a real world identity. but i guess the person who found the vulnerability could easily (note the "person" is a member of an organisation who has access to the code) tell someone else who is not identifiable and have them exploit the vulnerability. how do organisations decide who has access to the code. if the person does not decide to try to exploit it, they have to bring it to the attention of others or try to fix it themselves. \ No newline at end of file