-
Notifications
You must be signed in to change notification settings - Fork 25
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Add skip onboarding option * update the initial pin auth screen * update disclaimer screen * update github issues url * update the invoice screen, share invoice Fixes #147 * update nav "settings" to "options" * improve UX on claiming while having no mint * update the donation row under settings * skip mint selection screen if user has 1 mint * fix negative bal. in txOverview after invoice scan * update history entries, see #154 * add SECURITY_POLICY.md * update security_policy * update * update app config * update hash_list * add submit:ios * update submit:ios * update security policy * update security policy * sign apk & hash_list * update SECURITY.md
- Loading branch information
Showing
21 changed files
with
246 additions
and
83 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,53 @@ | ||
# Security Policy | ||
|
||
<!-- ## Supported Versions | ||
Use this section to tell people about which versions of your project are | ||
currently being supported with security updates. | ||
| Version | Supported | | ||
| ------- | ------------------ | | ||
| 5.1.x | :white_check_mark: | | ||
| 5.0.x | :x: | | ||
| 4.0.x | :white_check_mark: | | ||
| < 4.0 | :x: | --> | ||
|
||
## Reporting a Vulnerability | ||
|
||
We take the security of our users seriously. If you believe you have discovered a security vulnerability or have any security concerns regarding this project, please follow our responsible disclosure guidelines outlined below. | ||
|
||
### How to Report | ||
|
||
To report a security vulnerability or concern, you can use one of the following methods: | ||
|
||
#### Related to the eNuts implementation | ||
|
||
- Github: [https://github.com/cashubtc/eNuts/security/advisories/new](https://github.com/cashubtc/eNuts/security/advisories/new) | ||
- Email: [m.echerbebo@gmail.com](mailto:m.echerbebo@gmail.com) | ||
- Telegram: [https://t.me/eNutsWallet](https://t.me/eNutsWallet) | ||
|
||
#### Related to the Cashu protocol | ||
|
||
- Telegram: [https://t.me/CashuBTC](https://t.me/CashuBTC) | ||
|
||
Feel free to request a private discussion with the maintainers for a more personalized conversation. When reporting, please provide as much detail as possible, including a clear description of the vulnerability and any potential impact. | ||
|
||
### Disclosure Process | ||
|
||
We will acknowledge your report immediatly and provide an estimated timeline for resolution. We will work closely with you to understand the issue and verify its validity. | ||
|
||
Once the vulnerability is confirmed and resolved, we will coordinate with you to determine an appropriate disclosure timeline, which may include a coordinated public release of information. | ||
|
||
### Bug Bounty Program | ||
|
||
We highly value the contributions of security researchers who responsibly disclose security vulnerabilities to us. While we aspire to have a bug bounty program in place to reward these efforts, we regret to inform you that, at the moment, we do not have sufficient funds allocated for this purpose. | ||
|
||
We are committed to the idea of establishing a bug bounty program as soon as our financial situation allows. Our aim is to fairly compensate security researchers and any collaborator for their valuable contributions to our projects. | ||
|
||
We appreciate your understanding and patience in this matter. In the meantime, please continue to report security vulnerabilities using the methods outlined above. | ||
|
||
## Legal Disclaimer | ||
|
||
We kindly request that you refrain from disclosing any security-related information publicly until we have had a chance to review and address the reported issue. We are committed to acting in accordance with all relevant laws and regulations to protect the security of our users. | ||
|
||
Thank you for helping us make eNuts more secure. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.