Protonvpn wireguard config downloader

[elfkuzco]

Changes

• add script to automatically download wireguard configuration files for all available VPN servers

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.66%. Comparing base (0c088e1) to head (45b4e65).
Report is 4 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #47   +/-   ##
=======================================
  Coverage   69.66%   69.66%           
=======================================
  Files          30       30           
  Lines         946      946           
  Branches       93       93           
=======================================
  Hits          659      659           
  Misses        267      267           
  Partials       20       20           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[rgaudin]

Thank you it's great and functional but I'd like a bit more details as comments.

That notion of port is unclear to me. What would one care about it? What are the consequences of picking one or not?

[rgaudin]

Can you also add a comment here about how data is organized in their API so it's easier to maintain this in a year :)
I also recall that the UI mentions an expiration date. Are those ones expiring at some point? When?

[elfkuzco]

Um, regarding this. I can't see a parameter for configuring the timeline. On the web browser, the credentials don't show either. I checked out their desktop code and there wasn't expiration set. It was simply saving the files to disk and updating them whenever the connection settings changed. In their case, there was only one configuration file

[elfkuzco]

Another thing I noticed was that the web client used a serial number for the configuration files but I didn't see similar code used in other clients. Also, the clients config when created on the web expires when their plan is inactive. I assume the same applies for the configs generated by this script.

[elfkuzco]

I will make a different PR depending on what I find out about this.

[elfkuzco]

Thank you it's great and functional but I'd like a bit more details as comments.

That notion of port is unclear to me. What would one care about it? What are the consequences of picking one or not?

Our wireguard configuration from the worker-manager is configured to use a specific port for routing traffic, 51820 by default. When I fetch the client's config from ProtonVPN, there are other ports available for wireguard e.g 443, etc. So, when I try to write the configuration file using the template provided by ProtonVPN library, they end up picking up the first available port e.g 443 and if it's not the same port used on the worker-manager, then it won't work.

[rgaudin]

OK, please add it in the README