From 05fd607d736edd5aa932a4ca90fa74bd1bbc4b4b Mon Sep 17 00:00:00 2001 From: Evan Su <48808396+HACKERALERT@users.noreply.github.com> Date: Sat, 12 Apr 2025 21:02:11 -0400 Subject: [PATCH 01/14] Update README.md: add more to Security section Note that I've done a lot to lock down the Picocrypt organization and repos --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 73f0835..1f06b82 100644 --- a/README.md +++ b/README.md @@ -38,8 +38,8 @@ A command-line interface is available for Picocrypt here which allows you to encrypt and decrypt standard Picocrypt volumes (no advanced features or keyfiles) on any modern browser, including mobile devices. It's a simple, future-proof way to encrypt files that should work indefinitely due to the web's stable nature. Note that you can only encrypt single files up to a maximum size of 1 GiB. -## Mobile -An experimental project PicoGo is a community-developed port of Picocrypt to platforms like Android and iOS using the Fyne GUI library. Feel free to try it out, but keep in mind that it is not part of the official core Picocrypt project (like the platforms listed above) and thus not subject to the same scrutiny and standards that the core project is. So, **use it with caution and diligence** during its experimental phase. +## Mobile 🚧 +An experimental project PicoGo is a community-developed port of Picocrypt to platforms like Android and iOS using the Fyne GUI library. Feel free to try it out, but keep in mind that it is *not* part of the official core Picocrypt project (like the platforms listed above) and thus not subject to the same scrutiny and standards that the core project is. So, **use it with caution and diligence** during its experimental phase. # Why Picocrypt? Why should you use Picocrypt instead of VeraCrypt, 7-Zip, BitLocker, or Cryptomator? Here are a few reasons why you should choose Picocrypt: @@ -93,7 +93,7 @@ While being simple, Picocrypt also strives to be powerful in the hands of knowle # 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, Reddit, Google, 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 as long as you understand: +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, 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. I've also meticulously gone through every single setting in the Picocrypt organization and repos, locking down access behind multiple layers of security such as read-only base-level member permissions, required PRs and mandatory approvals (which no one can do but me), mandatory CODEOWNERS approvals, and I'm the only member of the Picocrypt organization and repos (except for PicoGo). You can feel confident about using Picocrypt as long as you understand: Picocrypt operates under the assumption that the host machine it is running on is safe and trusted. If that is not the case, no piece of software will be secure, and you will have much bigger problems to worry about. As such, Picocrypt is designed for the offline security of volumes and does not attempt to protect against side-channel analysis. From 7e53b2f51853b34169c23c896789a023022c2a55 Mon Sep 17 00:00:00 2001 From: Evan Su <48808396+HACKERALERT@users.noreply.github.com> Date: Sat, 12 Apr 2025 21:08:45 -0400 Subject: [PATCH 02/14] Update issue templates Add test issue template --- .github/ISSUE_TEMPLATE/custom.md | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/custom.md diff --git a/.github/ISSUE_TEMPLATE/custom.md b/.github/ISSUE_TEMPLATE/custom.md new file mode 100644 index 0000000..48d5f81 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/custom.md @@ -0,0 +1,10 @@ +--- +name: Custom issue template +about: Describe this issue template's purpose here. +title: '' +labels: '' +assignees: '' + +--- + + From baa4b73219439406a448038fca48f3c7b38fa842 Mon Sep 17 00:00:00 2001 From: Evan Su <48808396+HACKERALERT@users.noreply.github.com> Date: Sat, 12 Apr 2025 21:13:37 -0400 Subject: [PATCH 03/14] Create config.yml: require usage of issue template --- .github/ISSUE_TEMPLATE/config.yml | 1 + 1 file changed, 1 insertion(+) create mode 100644 .github/ISSUE_TEMPLATE/config.yml diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml new file mode 100644 index 0000000..3ba13e0 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -0,0 +1 @@ +blank_issues_enabled: false From 14d4c60c0e6eaeafbb8d4e2e3aa389f3c3188aa2 Mon Sep 17 00:00:00 2001 From: Evan Su <48808396+HACKERALERT@users.noreply.github.com> Date: Sat, 12 Apr 2025 21:17:26 -0400 Subject: [PATCH 04/14] Update issue templates --- .github/ISSUE_TEMPLATE/{custom.md => default.md} | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) rename .github/ISSUE_TEMPLATE/{custom.md => default.md} (56%) diff --git a/.github/ISSUE_TEMPLATE/custom.md b/.github/ISSUE_TEMPLATE/default.md similarity index 56% rename from .github/ISSUE_TEMPLATE/custom.md rename to .github/ISSUE_TEMPLATE/default.md index 48d5f81..fae9ff9 100644 --- a/.github/ISSUE_TEMPLATE/custom.md +++ b/.github/ISSUE_TEMPLATE/default.md @@ -1,5 +1,5 @@ --- -name: Custom issue template +name: Default about: Describe this issue template's purpose here. title: '' labels: '' @@ -7,4 +7,5 @@ assignees: '' --- - + +* [ ] I agree From 3fe738604359526ffa831ab3cd910487a50848c9 Mon Sep 17 00:00:00 2001 From: Evan Su <48808396+HACKERALERT@users.noreply.github.com> Date: Sat, 12 Apr 2025 21:23:51 -0400 Subject: [PATCH 05/14] Update default.md --- .github/ISSUE_TEMPLATE/default.md | 26 +++++++++++++++----------- 1 file changed, 15 insertions(+), 11 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/default.md b/.github/ISSUE_TEMPLATE/default.md index fae9ff9..9edc2b2 100644 --- a/.github/ISSUE_TEMPLATE/default.md +++ b/.github/ISSUE_TEMPLATE/default.md @@ -1,11 +1,15 @@ ---- -name: Default -about: Describe this issue template's purpose here. -title: '' -labels: '' -assignees: '' - ---- - - -* [ ] I agree +name: Default template +about: The default template for all issues +body: + - type: markdown + attributes: + value: | + Hi + - type: checkboxes + id: agreement + attributes: + label: Label + description: abc + options: + - label: Orange cat + required: true From bf21bd02626597e18570db7d3f8b5cab6c66e3f1 Mon Sep 17 00:00:00 2001 From: Evan Su <48808396+HACKERALERT@users.noreply.github.com> Date: Sat, 12 Apr 2025 21:26:52 -0400 Subject: [PATCH 06/14] Update and rename default.md to default.yml --- .github/ISSUE_TEMPLATE/{default.md => default.yml} | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) rename .github/ISSUE_TEMPLATE/{default.md => default.yml} (79%) diff --git a/.github/ISSUE_TEMPLATE/default.md b/.github/ISSUE_TEMPLATE/default.yml similarity index 79% rename from .github/ISSUE_TEMPLATE/default.md rename to .github/ISSUE_TEMPLATE/default.yml index 9edc2b2..01a8e3c 100644 --- a/.github/ISSUE_TEMPLATE/default.md +++ b/.github/ISSUE_TEMPLATE/default.yml @@ -1,12 +1,11 @@ name: Default template -about: The default template for all issues +description: The default template for all issues body: - type: markdown attributes: value: | Hi - type: checkboxes - id: agreement attributes: label: Label description: abc From de386390ef7b65f98fdc8be5646fcdc7cad23f6d Mon Sep 17 00:00:00 2001 From: Evan Su <48808396+HACKERALERT@users.noreply.github.com> Date: Sat, 12 Apr 2025 21:30:20 -0400 Subject: [PATCH 07/14] Update default.yml --- .github/ISSUE_TEMPLATE/default.yml | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/default.yml b/.github/ISSUE_TEMPLATE/default.yml index 01a8e3c..b753ae0 100644 --- a/.github/ISSUE_TEMPLATE/default.yml +++ b/.github/ISSUE_TEMPLATE/default.yml @@ -4,11 +4,10 @@ body: - type: markdown attributes: value: | - Hi + # Rules + Test abc - type: checkboxes attributes: - label: Label - description: abc options: - - label: Orange cat + - label: I have read and agree to the rules required: true From e3eb8b5847338371cd26ff3eac4a2788530a60a7 Mon Sep 17 00:00:00 2001 From: Evan Su <48808396+HACKERALERT@users.noreply.github.com> Date: Sat, 12 Apr 2025 21:34:07 -0400 Subject: [PATCH 08/14] Update default.yml --- .github/ISSUE_TEMPLATE/default.yml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/.github/ISSUE_TEMPLATE/default.yml b/.github/ISSUE_TEMPLATE/default.yml index b753ae0..6afd708 100644 --- a/.github/ISSUE_TEMPLATE/default.yml +++ b/.github/ISSUE_TEMPLATE/default.yml @@ -5,9 +5,22 @@ body: attributes: value: | # Rules + - type: markdown + attributes: + value: | Test abc - type: checkboxes attributes: options: - label: I have read and agree to the rules required: true + - type: input + attributes: + label: Describe the issue briefly + description: "Give a short (max one paragraph in length) summary" + validations: + required: true + - type: markdown + attributes: + values: | + Create the issue and you can add additional details in a separate comment. From ea9105b91a57f53be67b93c5797bd642cc55cfaf Mon Sep 17 00:00:00 2001 From: Evan Su <48808396+HACKERALERT@users.noreply.github.com> Date: Sat, 12 Apr 2025 21:37:22 -0400 Subject: [PATCH 09/14] Update default.yml --- .github/ISSUE_TEMPLATE/default.yml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/default.yml b/.github/ISSUE_TEMPLATE/default.yml index 6afd708..b227a31 100644 --- a/.github/ISSUE_TEMPLATE/default.yml +++ b/.github/ISSUE_TEMPLATE/default.yml @@ -11,6 +11,7 @@ body: Test abc - type: checkboxes attributes: + label: "Please confirm" options: - label: I have read and agree to the rules required: true @@ -22,5 +23,5 @@ body: required: true - type: markdown attributes: - values: | + value: | Create the issue and you can add additional details in a separate comment. From 837281168db041f2911101c2b1413cd69a951d52 Mon Sep 17 00:00:00 2001 From: Evan Su <48808396+HACKERALERT@users.noreply.github.com> Date: Sat, 12 Apr 2025 21:40:42 -0400 Subject: [PATCH 10/14] Update default.yml --- .github/ISSUE_TEMPLATE/default.yml | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/default.yml b/.github/ISSUE_TEMPLATE/default.yml index b227a31..ceec3a0 100644 --- a/.github/ISSUE_TEMPLATE/default.yml +++ b/.github/ISSUE_TEMPLATE/default.yml @@ -11,17 +11,13 @@ body: Test abc - type: checkboxes attributes: - label: "Please confirm" + label: "Please confirm:" options: - - label: I have read and agree to the rules + - label: "I have read and agree to the rules" required: true - type: input attributes: - label: Describe the issue briefly - description: "Give a short (max one paragraph in length) summary" + label: "Describe the issue briefly in a few sentences:" + description: "After creating the issue, you can add more details in a separate comment" validations: required: true - - type: markdown - attributes: - value: | - Create the issue and you can add additional details in a separate comment. From eb4fef1d0ec8bba9a4fb5f5f7d2bb8f95a8adc07 Mon Sep 17 00:00:00 2001 From: Evan Su <48808396+HACKERALERT@users.noreply.github.com> Date: Sat, 12 Apr 2025 23:44:31 -0400 Subject: [PATCH 11/14] Update default.yml: first draft of issues template --- .github/ISSUE_TEMPLATE/default.yml | 58 +++++++++++++++++++++++++++++- 1 file changed, 57 insertions(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/default.yml b/.github/ISSUE_TEMPLATE/default.yml index ceec3a0..f189a7c 100644 --- a/.github/ISSUE_TEMPLATE/default.yml +++ b/.github/ISSUE_TEMPLATE/default.yml @@ -8,7 +8,63 @@ body: - type: markdown attributes: value: | - Test abc + **Please read this section carefully. Breaking the rules may result in you being blocked from interacting with this repository.** + - type: markdown + attributes: + value: | + Picocrypt is a "finished" piece of software and is in a maintenance-only stage. This does not mean the software is old, outdated, or abandonware, but that the focus is on fixing bugs and ensuring the software continues to work smoothly as opposed to actively developing new features. As well, my time as the developer is limited considering that Picocrypt brings me no monetary benefit and is entirely a gift of my time and skill to the community. + - type: markdown + attributes: + value: | + *To ensure that issues remain relevant and as time-efficient for me as possible, please follow the guidelines below depending on what the topic of your issue creation is.* + - type: markdown + attributes: + value: | + ### Bug reports or security issues + - type: markdown + attributes: + value: | + These are high-priority and the main purpose of leaving issues open for creation. Make the issue with a short description, and then once the issue is created, add a comment with as many details as possible. Ping me (@HACKERALERT) in the comment so that I can get to it as soon as possible. Keep in mind that I define "bug" as something wrong with Picocrypt's code itself. If it's not Picocrypt's fault, it's not a bug. +- type: markdown + attributes: + value: | + ### Problems running/starting Picocrypt + - type: markdown + attributes: + value: | + Usually these issues are not directly because of Picocrypt's code. Create the issue and in a separate comment, provide details about the environment you're running in (like OS, OS version, DE, etc.). **Do not ping me initially.** Let the issue sit for at least *3 days* to allow other users to potentially help you resolve the issue. If after 3 days, you haven't figured things out, then you may ping me (@HACKERALERT). +- type: markdown + attributes: + value: | + ### Support requests/usage questions + - type: markdown + attributes: + value: | + Create the issue and ask your question or support request in a separate comment. **Do not ping me initially.** Let the issue marinate for at least *5 days* to give other users a chance to help you first. If after 5 days, you have not received any assistance, then you may ping me (@HACKERALERT). +- type: markdown + attributes: + value: | + ### Feature requests/suggestions + - type: markdown + attributes: + value: | + Picocrypt is mature software; I do not intend to add any new features. Generally, do not create any feature requests unless it's very minor and can be implemented with low effort and minimal impact on reliability. What is considered "minor" is subjective, but here is an example: "ability to decrypt a volume entirely in-memory" is pretty significant, while "press the Start button on Enter key" is relatively minor. +- type: markdown + attributes: + value: | + ### Performance issues/improvements + - type: markdown + attributes: + value: | + Picocrypt prioritizes correctness and reliability over performance, so many parts of the code are written sequentially and don't use concurrency. This is intentional and need not be pointed out. Unless performance is absolutely atrocious to the point where it is indicative of a potential bug, do not make issues about performance. +- type: markdown + attributes: + value: | + ### Other issues/generic topics + - type: markdown + attributes: + value: | + You will have to use your best judgement here. Read the sections above to get an idea of what I expect to see and do what you think is best. Ideally, ping me only if sufficient time has passed for other users to assist/answer you, or it is best addressed by me directly. - type: checkboxes attributes: label: "Please confirm:" From 2313dcff4b4205aefe68704a2ce9c1799939cc69 Mon Sep 17 00:00:00 2001 From: Evan Su <48808396+HACKERALERT@users.noreply.github.com> Date: Sat, 12 Apr 2025 23:45:41 -0400 Subject: [PATCH 12/14] Update default.yml: fix indentation --- .github/ISSUE_TEMPLATE/default.yml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/default.yml b/.github/ISSUE_TEMPLATE/default.yml index f189a7c..e0cf6e6 100644 --- a/.github/ISSUE_TEMPLATE/default.yml +++ b/.github/ISSUE_TEMPLATE/default.yml @@ -25,7 +25,7 @@ body: attributes: value: | These are high-priority and the main purpose of leaving issues open for creation. Make the issue with a short description, and then once the issue is created, add a comment with as many details as possible. Ping me (@HACKERALERT) in the comment so that I can get to it as soon as possible. Keep in mind that I define "bug" as something wrong with Picocrypt's code itself. If it's not Picocrypt's fault, it's not a bug. -- type: markdown + - type: markdown attributes: value: | ### Problems running/starting Picocrypt @@ -33,7 +33,7 @@ body: attributes: value: | Usually these issues are not directly because of Picocrypt's code. Create the issue and in a separate comment, provide details about the environment you're running in (like OS, OS version, DE, etc.). **Do not ping me initially.** Let the issue sit for at least *3 days* to allow other users to potentially help you resolve the issue. If after 3 days, you haven't figured things out, then you may ping me (@HACKERALERT). -- type: markdown + - type: markdown attributes: value: | ### Support requests/usage questions @@ -41,7 +41,7 @@ body: attributes: value: | Create the issue and ask your question or support request in a separate comment. **Do not ping me initially.** Let the issue marinate for at least *5 days* to give other users a chance to help you first. If after 5 days, you have not received any assistance, then you may ping me (@HACKERALERT). -- type: markdown + - type: markdown attributes: value: | ### Feature requests/suggestions @@ -49,7 +49,7 @@ body: attributes: value: | Picocrypt is mature software; I do not intend to add any new features. Generally, do not create any feature requests unless it's very minor and can be implemented with low effort and minimal impact on reliability. What is considered "minor" is subjective, but here is an example: "ability to decrypt a volume entirely in-memory" is pretty significant, while "press the Start button on Enter key" is relatively minor. -- type: markdown + - type: markdown attributes: value: | ### Performance issues/improvements @@ -57,7 +57,7 @@ body: attributes: value: | Picocrypt prioritizes correctness and reliability over performance, so many parts of the code are written sequentially and don't use concurrency. This is intentional and need not be pointed out. Unless performance is absolutely atrocious to the point where it is indicative of a potential bug, do not make issues about performance. -- type: markdown + - type: markdown attributes: value: | ### Other issues/generic topics From a66583927126dc84beed96bd98b5df0f4ddb4807 Mon Sep 17 00:00:00 2001 From: Evan Su <48808396+HACKERALERT@users.noreply.github.com> Date: Sun, 13 Apr 2025 00:06:38 -0400 Subject: [PATCH 13/14] Update default.yml: add antivirus section, more checkboxes --- .github/ISSUE_TEMPLATE/default.yml | 20 ++++++++++++++++---- 1 file changed, 16 insertions(+), 4 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/default.yml b/.github/ISSUE_TEMPLATE/default.yml index e0cf6e6..87751f2 100644 --- a/.github/ISSUE_TEMPLATE/default.yml +++ b/.github/ISSUE_TEMPLATE/default.yml @@ -8,7 +8,7 @@ body: - type: markdown attributes: value: | - **Please read this section carefully. Breaking the rules may result in you being blocked from interacting with this repository.** + **Please read this section carefully and completely. You may be blocked from this repository if you violate the rules.** - type: markdown attributes: value: | @@ -33,6 +33,14 @@ body: attributes: value: | Usually these issues are not directly because of Picocrypt's code. Create the issue and in a separate comment, provide details about the environment you're running in (like OS, OS version, DE, etc.). **Do not ping me initially.** Let the issue sit for at least *3 days* to allow other users to potentially help you resolve the issue. If after 3 days, you haven't figured things out, then you may ping me (@HACKERALERT). + - type: markdown + attributes: + value: | + ### Antivirus problems + - type: markdown + attributes: + value: | + These are unpreventable; Picocrypt is cryptography, file deletion, and passwords bundled into an executable... looks the same as ransomware unfortunately. Please report these false positives to your antivirus software provider and do not create an issue about it. - type: markdown attributes: value: | @@ -48,7 +56,7 @@ body: - type: markdown attributes: value: | - Picocrypt is mature software; I do not intend to add any new features. Generally, do not create any feature requests unless it's very minor and can be implemented with low effort and minimal impact on reliability. What is considered "minor" is subjective, but here is an example: "ability to decrypt a volume entirely in-memory" is pretty significant, while "press the Start button on Enter key" is relatively minor. + Picocrypt is mature software; I do not intend to add any new features. Generally, do not create any feature requests unless it's very minor and can be implemented with low effort and minimal impact on reliability and security. What is considered "minor" is subjective, but here is an example: "ability to decrypt a volume entirely in-memory" is pretty significant, while "press the Start button on Enter key" is relatively minor. A proof-of-concept link to code or a fork would be appreciated. - type: markdown attributes: value: | @@ -69,11 +77,15 @@ body: attributes: label: "Please confirm:" options: - - label: "I have read and agree to the rules" + - label: "I have carefully read and agree to the rules outlined above" + required: true + - label: "I will provide as many helpful details as possible" + required: true + - label: "I acknowledge my issue may be ignored or closed without explanation" required: true - type: input attributes: label: "Describe the issue briefly in a few sentences:" - description: "After creating the issue, you can add more details in a separate comment" + description: "You can add more details in a separate comment after creating the issue" validations: required: true From f0bfe3ba0378331138304ad8ce166b14c30d4176 Mon Sep 17 00:00:00 2001 From: Evan Su <48808396+HACKERALERT@users.noreply.github.com> Date: Sun, 13 Apr 2025 00:17:32 -0400 Subject: [PATCH 14/14] Update default.yml: grammar fixes --- .github/ISSUE_TEMPLATE/default.yml | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/default.yml b/.github/ISSUE_TEMPLATE/default.yml index 87751f2..9aa09e5 100644 --- a/.github/ISSUE_TEMPLATE/default.yml +++ b/.github/ISSUE_TEMPLATE/default.yml @@ -16,7 +16,7 @@ body: - type: markdown attributes: value: | - *To ensure that issues remain relevant and as time-efficient for me as possible, please follow the guidelines below depending on what the topic of your issue creation is.* + *To ensure that issues remain relevant and as time-efficient as possible for me, please follow the guidelines below depending on the type/topic of your issue.* - type: markdown attributes: value: | @@ -24,7 +24,7 @@ body: - type: markdown attributes: value: | - These are high-priority and the main purpose of leaving issues open for creation. Make the issue with a short description, and then once the issue is created, add a comment with as many details as possible. Ping me (@HACKERALERT) in the comment so that I can get to it as soon as possible. Keep in mind that I define "bug" as something wrong with Picocrypt's code itself. If it's not Picocrypt's fault, it's not a bug. + These are high-priority issues and the main purpose of this repository's issue tracker. Make the issue with a short description, and then once the issue is created, add a comment with as many details as possible. Ping me (@HACKERALERT) in the comment so that I can get to it as soon as possible. Keep in mind that I define "bug" as something wrong with Picocrypt's code itself. If it's not Picocrypt's fault, it's not a bug. - type: markdown attributes: value: | @@ -32,7 +32,7 @@ body: - type: markdown attributes: value: | - Usually these issues are not directly because of Picocrypt's code. Create the issue and in a separate comment, provide details about the environment you're running in (like OS, OS version, DE, etc.). **Do not ping me initially.** Let the issue sit for at least *3 days* to allow other users to potentially help you resolve the issue. If after 3 days, you haven't figured things out, then you may ping me (@HACKERALERT). + Usually these issues are not directly caused by Picocrypt's code. Create the issue and in a separate comment, provide details about the environment you're running in (like OS, DE, etc.). **Do not ping me initially.** Let the issue sit for at least *3 days* to allow other users to potentially help you resolve the issue. If after 3 days, you haven't figured things out, then you may ping me (@HACKERALERT). - type: markdown attributes: value: | @@ -40,7 +40,7 @@ body: - type: markdown attributes: value: | - These are unpreventable; Picocrypt is cryptography, file deletion, and passwords bundled into an executable... looks the same as ransomware unfortunately. Please report these false positives to your antivirus software provider and do not create an issue about it. + These are unpreventable; Picocrypt is cryptography, file deletion, and passwords bundled into an executable... which looks similar to ransomware, unfortunately. Please report these false positives to your antivirus software provider and do not create an issue about it. - type: markdown attributes: value: | @@ -48,7 +48,7 @@ body: - type: markdown attributes: value: | - Create the issue and ask your question or support request in a separate comment. **Do not ping me initially.** Let the issue marinate for at least *5 days* to give other users a chance to help you first. If after 5 days, you have not received any assistance, then you may ping me (@HACKERALERT). + Create the issue and ask your question or support request in a separate comment. **Do not ping me initially.** Let the issue sit for at least *5 days* to give other users a chance to help you first. If after 5 days, you have not received any assistance, then you may ping me (@HACKERALERT). - type: markdown attributes: value: | @@ -56,7 +56,7 @@ body: - type: markdown attributes: value: | - Picocrypt is mature software; I do not intend to add any new features. Generally, do not create any feature requests unless it's very minor and can be implemented with low effort and minimal impact on reliability and security. What is considered "minor" is subjective, but here is an example: "ability to decrypt a volume entirely in-memory" is pretty significant, while "press the Start button on Enter key" is relatively minor. A proof-of-concept link to code or a fork would be appreciated. + Picocrypt is mature software; I do not intend to add any new features. Generally, do not create any feature requests unless it's very minor and can be implemented with low effort and minimal impact on reliability and security. What is considered "minor" is subjective, but here is an example: "the ability to decrypt a volume entirely in-memory" is pretty significant, while "auto start encryption on pressing the Enter key" is relatively minor. A proof-of-concept link to code or a fork would be appreciated. - type: markdown attributes: value: | @@ -86,6 +86,6 @@ body: - type: input attributes: label: "Describe the issue briefly in a few sentences:" - description: "You can add more details in a separate comment after creating the issue" + description: "You can add more details in a separate comment after creating the issue." validations: required: true