Updated Notify_simplepush (markdown)

master
Chris Caron 2024-10-03 22:04:47 -04:00
parent ba7275ab8e
commit 7f172a727e
1 changed files with 7 additions and 2 deletions

@ -11,9 +11,14 @@ You can optionally add additional notification encryption in the settings where
### :lock: AES-CBC-128 Encryption Weakness
The Apprise team recognizes that the encryption used by this plugin is AES-CBC-128 which has been identified to have weaknesses including being vulnerable to the padding oracle attack ([Reference](https://soatok.blog/2020/07/12/comparison-of-symmetric-encryption-methods/#aes-gcm-vs-aes-cbc)).
If the level of encryption is not satisfactory to you, your options are reach out to SimplePush to improve their security (to which Apprise can accomodate), or choose not to use Simple Push.
If the level of encryption is not satisfactory to you, your options are:
1. Reach out to SimplePush and ask for them to improve their security (to which Apprise will gladly accomodate) ...or
1. Choose not to use Simple Push and select one of the [many other options available](https://github.com/caronc/apprise/wiki#notification-services).
What is important to identify is this weak encryption used by Apprise to access SimplePush is in place for compliance only. This will never have any cascading effect or impact any other secure notification service also supported by Apprise.
Below is a screenshot from https://simplepush.io/features explaining why the encryption is required (for compliance)<br/>![Screenshot from 2024-10-03 21-52-46](https://github.com/user-attachments/assets/d6764e5f-6f90-46be-9994-4cffc881477a)
What is important to identify is this weak encryption is required to use this plugin, and does not have any cascading effect or impact any other secure notification service also supported by Apprise.
### Syntax
Valid authentication syntaxes are as follows: