Open Dr-Flay opened 4 years ago
@Dr-Flay I like the basic idea. I will think about it and possibly set up a separate update channel. But probably still with signed and base tested files (against the UI).
Nevertheless I will try to update the project in the next days. ;)
@bitbeans Not time yet?
The current version of DNSCrypt-Proxy is 2.0.42, Simple DNSCrypt is still using version 2.0.31! Please give us an opportunity to update of DNSCrypt-Proxy as soon as possible regardless of the distribution of Simple DNSCrypt.
I`am working on an update at the moment :)
As the core proxy gets a lot more updates than this GUI, I suggest; Have the client check for updates of DNSCrypt-proxy, and display the info in the client somewhere. If the updated core can be pulled and installed via the client, that would be ideal for end users.
I understand you may prefer testing a build with the UI before bundling for obvious reasons. Thing is a lot of the updates have been bug fixes as well as new features, so perhaps a manual forced update with a warning that it has not been tested with Simple DNSCrypt would be adequate. At the least giving the user a link to the update would seem sensible if there are security issues that are more important than UI functionality. Many users are not aware the GUI and the proxy are 2 different projects, so will assume that updates will include any important security fixes.