dnscrypt-proxy-win32-1.3.2.zip's content not correctly deployed

Comments

16 comments

  • Avatar
    maintenance

    True. You can always pull both the executables out and use them immediately, though.

    0
    Comment actions Permalink
  • Avatar
    brelun

    I did pull out both executables and moved them to the folder reserved for dnscrypt-proxy (C: at root), but --install stated that there was a missing dll (forgot which one) presumably in one of the zip's folders.

    Thanks for your concern.

    I'm absolutely ignorant in computing, but I appreciate dnscrypt-proxy together with OpenDNS (don't know how to cook but appreciate the meal).

    dnscrypt-proxy 1.3.0 works fine, but if 1.3.2 is in town I'd like to get dancing with her :)

     

     

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    dnscrypt-proxy.exe -V
    dnscrypt-proxy 1.3.1

    dnscrypt-proxy.exe --install
    [INFO] The dnscrypt-proxy service has been installed and started

    Now what? The version may be displayed wrongly though.

    0
    Comment actions Permalink
  • Avatar
    maintenance

    You may have had a plugin installed previously, perhaps? Not sure what, as I believe the dlls you see in the zip are examples for developers. Seeing as you can use DNSCrypt from the single executable only, the error seems odd. (Or did you have the Windows GUI extended version of the program installed before - DNSCrypt WinClient?)  I would note the name of the dll and post it here.

    Or check this: http://download.dnscrypt.org/dnscrypt-proxy/dnscrypt-proxy-win32-full-1.3.2.zip . This may be your package.

    0
    Comment actions Permalink
  • Avatar
    maintenance

    Note also that the http://download.dnscrypt.org/dnscrypt-proxy/dnscrypt-proxy-win32-1.3.2.zip is also updated today, containing only the 2 executable files...

    0
    Comment actions Permalink
  • Avatar
    brelun

    - Downloaded dnscrypt-proxy-win32-1.3.2.zip (MD5=8F4267F92F3AC36745B0FF5967301B7C) - 20-Jul-2013 17:31 - 239844kB
    - Installed dnscrypt-proxy.exe successfully

    ---

    I had no remains of previous dnscrypt-proxy plugin, DNSCrypt WinClient had not been installed, and previous dnscrypt-proxy 1.3.0 was free of any install problem when I started this post. I described the facts as I had experienced them. I know not the engine but I have my driver's license :)

    Anyway, dnscrypy-proxy 1.3.2 installed and functional.

    Thanks maintenance (forgot your name!) and rotblitz :)

    Long live OpenDNS, let dnscrypt be!

    0
    Comment actions Permalink
  • Avatar
    brelun

    I forgot to mention, though implicitly obvious from my previous  post, that of course dnscrypt-proxe 1.3.0 had been fully uninstalled when I tried to install ver. 1.3.2. It was a clean install.

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    It seems you downloaded the wrong (non-Windows or source) package before, although you mentioned dnscrypt-proxy-win32-1.3.2.zip only. Therefore you caused confusion, because this ZIP archive just contains two executables (.exe) only, not matter what version was there.

    "It was a clean install."

    Irrelevant. For me it worked with just overwriting the service entry. Btw, there is not really an "installation", the parameter --install only establishes the Windows service. You could achieve the same with the sc.exe command.

    0
    Comment actions Permalink
  • Avatar
    brelun

    Before, as you put it, I had downloaded the one and only dnscrypt-proxy-win32-1.3.2.zip (MD5=0D314A7CC87C449B93ED03004D8CBE59) - 206252kB available at that time (07-19-2013) on http://download.dnscrypt.org/dnscrypt-proxy/

    As for the install and the semantics I do understand it as well as the install of the service, --install remains that pertinent that it is the word the service install uses.

    By "clean install' I was referring to the fact that I did neither overwrite neither perform a -reinstall, but proceeded after having --uninstall(ed) version 1.3.0 that was in place (that is removing the service after having stopped it)

    If we recall the point which was mine to start this post it appears acknowledgeable that the 1.32 zip offered for download contained both executables each within a set of folders together with source and libraries, that I had pulled out these two executables (since the service install is said to require but these two), that I had moved them to a c:\dnscrypt-proxy folder, that I had proceeded with a dnscrypt-proxy.exe --install as always and that the result was an unsuccessful service install notified with a missing dll.

    Only present and future count. I am thankful for your commitment, after all OpenDNS and dnscrypt are seperate and moreover I have no authority to require whatsoever.

    I was only asking for advice. Many thanks should they be repeated.

     

    0
    Comment actions Permalink
  • Avatar
    maintenance

    @rotblitz: The zip that normally contains only the two executables did have source and the executables in two different folders (/bin & /sbin) when published on the 19th. This was fixed on the 20th. (Hence, some confusion regarding the contents of dnscrypt-proxy-win32-1.3.2.zip)

     

    The missing dll will remain a mystery since we don't know what it was. Unless jedisct1 has some idea - if it is package-related.

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    Ah, I see now. I've never seen the ZIP archive from July 19. Thanks.

    0
    Comment actions Permalink
  • Avatar
    jedisct1

    Hello,

    Building and testing the software on Windows takes way more time than on other platforms, if only because I'm not very familiar with Windows, so there is often some delay before I put Windows packages online.

    1.3.1 brought improvements for iOS and Android, nothing for Windows over 1.3.0, so upgrading wasn't really necessary.

    The extra files in the 1.3.2 package were not source code, but plugins (+ required headers to build your own plugins).

    Plugins are one of the best feature of the dnscrypt proxy, and allows local logging of DNS queries, compatibility with Umbrella, things like AAAA filtering to make your lookups twice as fast, and keyword filtering (that people keep asking for on this very forum).

    The crypto code is not part of this project any more, and is available separately, including Windows binaries. So the initial Win32 package for 1.3.1 didn't include this.

    I realized that it was confusing, especially if you were used to previous versions.

    Therefore, I splitted the package in two:

    - dnscrypt-proxy-win32 is the traditional, monolithic package, containing just two binaries.

    - dnscrypt-proxy-win32-full is the dynamically linked one, with all the default plugins, and a copy of all the required DLLs.

    I don't always read this forum (especially since it was migrated to this new system) or other forums that may talk about dnscrypt, so please report bugs, questions, suggestion, etc. to the dnscrypt project itself. Go to http://dnscrypt.org and click "support".

    Thanks!

    0
    Comment actions Permalink
  • Avatar
    brelun

    Thanks a lot jedisct1 for this information. dnscrypt-proxy is a marvelous little gem, and taking the time to bring up the details of the Windows builds is kind and most appreciated.

    DnsCrypt, and Dnscrypt-proxy fall into this area where the background is complex yet the output is accessible to a non-techie, the consequence being that as soon as the latter's references change there's like a disturbance :)

    Your comment make things clear. Thanks again.

    0
    Comment actions Permalink
  • Avatar
    rotblitz

    @jedisct1
    Great stuff! Thanks for these explanations.

    I know, there is some documentation about plugins: https://github.com/jedisct1/dnscrypt-proxy/blob/master/README-PLUGINS.markdown
    But it would be useful to include this and also the Windows specific things like --install as a README or MAN file in the package.

    0
    Comment actions Permalink
  • Avatar
    maintenance

    @jedisct1

    Indeed, that was poorly worded on my part. There were the example plugins and some header files so... source! Simple, at the expense of being wrong. :p

    So, the binary in the -full package was in fact expecting to find the _example_ libraries, hence the error message, if I understand correctly this rather moot point.

    0
    Comment actions Permalink
  • Avatar
    brelun

    @maintenance, you took the words out of my keyboard :)

    @rotblitz, I agree with the idea of a descriptive README file. Until now I didn't even know, conceive dnscrypt-proxy to be "plugable", and as for what I read of jedisct1's explanations, sounds exciting, yet requiring if applicable a "how to" ...

     

    0
    Comment actions Permalink

Please sign in to leave a comment.