Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

End-to-end encrypted notification support for mobile_app #52048

Closed

Conversation

zacwest
Copy link
Member

@zacwest zacwest commented Jun 21, 2021

Proposed change

Allows for encrypting notification content using the same encryption as is used for webhooks in mobile_app.

Type of change

  • Dependency upgrade
  • Bugfix (non-breaking change which fixes an issue)
  • New integration (thank you!)
  • New feature (which adds functionality to an existing integration)
  • Breaking change (fix/feature causing existing functionality to break)
  • Code quality improvements to existing code or addition of tests

Additional information

Checklist

  • The code change is tested and works locally.
  • Local tests pass. Your PR cannot be merged unless tests pass
  • There is no commented out code in this PR.
  • I have followed the development checklist
  • The code has been formatted using Black (black --fast homeassistant tests)
  • Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • The manifest file has all fields filled out correctly.
    Updated and included derived files by running: python3 -m script.hassfest.
  • New or updated dependencies have been added to requirements_all.txt.
    Updated by running python3 -m script.gen_requirements_all.
  • Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

  • No score or internal
  • 🥈 Silver
  • 🥇 Gold
  • 🏆 Platinum

To help with the load of incoming pull requests:

robbiet480 and others added 7 commits March 6, 2021 23:07
…-e2e

# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.
@probot-home-assistant
Copy link

Hey there @robbiet480, mind taking a look at this pull request as its been labeled with an integration (mobile_app) you are listed as a codeowner for? Thanks!
(message by CodeOwnersMention)

push_url = app_data[ATTR_PUSH_URL]

if data[ATTR_MESSAGE] in cleartext_commands:
data = {"command": data[ATTR_MESSAGE]}
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

some of these commands require additional arguments, which may need parsing themselves. for example, clear_notification. maybe it would be worth having a 'cleartext_push_url' and 'encrypted_push_url' for this case.

@github-actions
Copy link

There hasn't been any activity on this pull request recently. This pull request has been automatically marked as stale because of that and will be closed if no further activity occurs within 7 days.
Thank you for your contributions.

@github-actions github-actions bot added the stale label Jul 21, 2021
@github-actions github-actions bot closed this Jul 28, 2021
Dev automation moved this from Needs review to Cancelled Jul 28, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Jul 29, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Dev
  
Cancelled
Development

Successfully merging this pull request may close these issues.

None yet

3 participants