From 9480f4cf9e66fa2ca104b2073efc6433d14c3647 Mon Sep 17 00:00:00 2001
From: Evan Su <48808396+HACKERALERT@users.noreply.github.com>
Date: Sat, 15 Jan 2022 15:27:01 -0500
Subject: [PATCH] Add network request note
---
README.md | 2 ++
1 file changed, 2 insertions(+)
diff --git a/README.md b/README.md
index 88aa0a8..47b4db0 100644
--- a/README.md
+++ b/README.md
@@ -55,6 +55,8 @@ In addition to these comprehensive options for encryption and decryption, Picocr
# Security
For more information on how Picocrypt handles cryptography, see Internals for the technical details. If you're worried about the safety of me or this project, let me assure you that this repository won't be hijacked or backdoored. I have 2FA (TOTP) enabled on all accounts with a tie to Picocrypt (GitHub, Google, Reddit, Ubuntu One/Snapcraft, Discord, etc.), in addition to full-disk encryption on all of my portable devices. For further hardening, Picocrypt uses my isolated forks of dependencies and I fetch upstream only when I have taken a look at the changes and believe that there aren't any security issues. This means that if a dependency gets hacked or deleted by the author, Picocrypt will be using my fork of it and remain completely unaffected. You can feel confident about using Picocrypt.
+Note: Current versions of Picocrypt will make a network request to raw.githubusercontent.com to check whether a newer verison of Picocrypt is available. In the future, when Picocrypt becomes production-ready, I will remove the update checker and Picocrypt will become completely isolated from the Internet.
+
# Community
Here are some places where you can stay up to date with Picocrypt and get involved: