[GH-ISSUE #335] Support end-to-end encryption #48

Closed
opened 2026-03-03 16:36:12 +03:00 by kerem · 5 comments
Owner

Originally created by @michnovka on GitHub (Jan 18, 2024).
Original GitHub issue: https://github.com/NdoleStudio/httpsms/issues/335

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

Originally created by @michnovka on GitHub (Jan 18, 2024). Original GitHub issue: https://github.com/NdoleStudio/httpsms/issues/335 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
kerem closed this issue 2026-03-03 16:36:13 +03:00
Author
Owner

@AchoArnold commented on GitHub (Jan 18, 2024):

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?

<!-- gh-comment-id:1898956990 --> @AchoArnold commented on GitHub (Jan 18, 2024): 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?
Author
Owner

@michnovka commented on GitHub (Jan 18, 2024):

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

<!-- gh-comment-id:1899292438 --> @michnovka commented on GitHub (Jan 18, 2024): 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
Author
Owner

@AchoArnold commented on GitHub (Jan 19, 2024):

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

<!-- gh-comment-id:1899801982 --> @AchoArnold commented on GitHub (Jan 19, 2024): I like the idea. It sounds like a fun weekend project.
Author
Owner

@AchoArnold commented on GitHub (Jan 21, 2024):

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

<!-- gh-comment-id:1902617157 --> @AchoArnold commented on GitHub (Jan 21, 2024): It's done. I had a great time learning about AES encryption 🚀
Author
Owner

@michnovka commented on GitHub (Jan 21, 2024):

Thanks!

<!-- gh-comment-id:1902788287 --> @michnovka commented on GitHub (Jan 21, 2024): Thanks!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/httpsms#48
No description provided.