Encrypt URLs with Proxy #294

Closed
opened 2025-08-19 10:46:30 +00:00 by XDeadHackerX · 4 comments
XDeadHackerX commented 2025-08-19 10:46:30 +00:00 (Migrated from github.com)

Hi @webstreamr ,

I think it would be a good idea to encrypt or obfuscate the proxy server credentials in the result links that go through Porxy.

Why?
In my case I share my MediaFlow server with a couple of friends and they don't use AIOStream (which does obfuscate the URLs), so, I don't want to put the Addon on their Stremio accounts because if they copy the download link of the contents already there they can see in plain text the URL and password of my MediaFlow server.

Thanks in advance!

Hi @webstreamr , I think it would be a good idea to encrypt or obfuscate the proxy server credentials in the result links that go through Porxy. Why? In my case I share my MediaFlow server with a couple of friends and they don't use AIOStream (which does obfuscate the URLs), so, I don't want to put the Addon on their Stremio accounts because if they copy the download link of the contents already there they can see in plain text the URL and password of my MediaFlow server. Thanks in advance!
webstreamr commented 2025-08-19 11:00:04 +00:00 (Migrated from github.com)

Hi, thx, I think that's a good idea. Basically, encrypting the configuration. I had this on my mind already in the past as well. Most likely it will need a manual "upgrade" via re-install once after the implementation is ready.

Hi, thx, I think that's a good idea. Basically, encrypting the configuration. I had this on my mind already in the past as well. Most likely it will need a manual "upgrade" via re-install once after the implementation is ready.
XDeadHackerX commented 2025-08-19 11:02:32 +00:00 (Migrated from github.com)

Hi, thx, I think that's a good idea. Basically, encrypting the configuration. I had this on my mind already in the past as well. Most likely it will need a manual "upgrade" via re-install once after the implementation is ready.

Sure, no problem! I'm sure your part will be much more complicated than mine which will just be reinstalling hehe.

> Hi, thx, I think that's a good idea. Basically, encrypting the configuration. I had this on my mind already in the past as well. Most likely it will need a manual "upgrade" via re-install once after the implementation is ready. Sure, no problem! I'm sure your part will be much more complicated than mine which will just be reinstalling hehe.
webstreamr commented 2025-08-19 11:20:53 +00:00 (Migrated from github.com)

notes for myself:

  • get a SECRET_KEY configured
  • use it in a similar way as aiostreams does to encrypt/decrypt user config
  • keep BC by allowing it to be null/undefined and support non-encrypted user configs

--> when configured and user install add-on the config will be encrypted

notes for myself: - get a `SECRET_KEY` configured - use it in a similar way as aiostreams does to encrypt/decrypt user config - keep BC by allowing it to be null/undefined and support non-encrypted user configs --> when configured and user install add-on the config will be encrypted
webstreamr commented 2026-01-01 19:18:13 +00:00 (Migrated from github.com)

Sorry, decided against this for now. Don't have time for it and the mfp password would be in streaming links anyway again

Sorry, decided against this for now. Don't have time for it and the mfp password would be in streaming links anyway again
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: Creepso/webstreamr-github#294
No description provided.