Skip to content

Support end-to-end encryption #335

Closed

Description

@michnovka

I think there should be an option to enable e2e for received SMS. I.e. all the payload is encrypted using a secret on the mobile phone, and can be decrypted by the webhook notification only, which knows the secret. HTTPSMS server will not know anything about the SMS content

Activity

  1. AchoArnold commented on Jan 18, 2024

    @AchoArnold
    Member

    Hello @michnovka

    I'm open to this. If you have a PR with the functionality I'll review it. Although I wonder if privacy is a concern, isn't it better to create your own backend server so you don't use httpsms at all?

  2. michnovka commented on Jan 18, 2024

    @michnovka
    Author

    Hi @AchoArnold , I will in the end go for the self hosted solution, but I mean this as a business idea for you. Not having e2e is basically the MAIN reason why I will self-host in the end, if you had this I would have ended using your servers and possibly paying.

    For that reason also, I will not make a PR for this, as I currently have no time and as you mentioned, self-hosting addresses my issues.

    Just an idea for a feature that might increase the % of people not defaulting to self-hosting and converting into paying customers.

    Cheers

  3. AchoArnold commented on Jan 19, 2024

    @AchoArnold
    Member

    I like the idea. It sounds like a fun weekend project.

  4. AchoArnold commented on Jan 21, 2024

    @AchoArnold
    Member

    It's done. I had a great time learning about AES encryption 🚀

  5. michnovka commented on Jan 21, 2024

    @michnovka
    Author

    Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions