http://bugzilla.suse.com/show_bug.cgi?id=977946 http://bugzilla.suse.com/show_bug.cgi?id=977946#c8 Marguerite Su <i@marguerite.su> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |IN_PROGRESS Flags|needinfo?(i@marguerite.su) | --- Comment #8 from Marguerite Su <i@marguerite.su> --- (In reply to Hemanth Kumar from comment #6)
Its possible from the upstream's dnscrypt-proxy- https://github.com/jedisct1/dnscrypt-proxy/issues/228
If so, it is a valid issue for openSUSE.
The process seems to involve editing the dnscrypt-proxy.socket, which is not installed from openSUSE repo. So i don't know how to do it for the "forked" method installation from openSUSE, which is why i asked it here.
An example of using "Redundant DNSCrypt providers"- https://wiki.archlinux.org/index.php/DNSCrypt
As you said "Neither dnscrypt-proxy.service nor dnscrypt-proxy.socket provided by upstream was installed/used in openSUSE. Upstream used "simple" method while we used "forking" method, which means we are superior."
If it was provided like the upstream method it would be better.
Thanks for the hint, I'll add that possibility ASAP. Actually I didn't think DNSCrypt can be used like that. If there're too many aspects to cover with our own systemd service, I think using upstream's service is a good idea for maintenance. Marguerite -- You are receiving this mail because: You are on the CC list for the bug.