Re: Verifying Signed Files Downloaded via HTTP

From: DaveW (david_wender_at_yahoo.com)
Date: 06/27/05

  • Next message: Tony Amos: "Network File Access" 
    Date: 27 Jun 2005 07:50:50 -0700

    > What is the exact exception type and message? (The full output of the
    > exception's ToString method would be best, if you can provide it.)

    I do not have the full exception message at this time because when the
    error occurs, we need to get the user back up and running immediately
    (it is a derivatives pricing/risk-management system). We know that
    clearing all of the files and allowing the Launcher to download again
    works. Next time it happens, I will try to get the full text.

    > Attempt to load the assembly using Assembly.Load, Assembly.LoadFrom, or
    > Assembly.LoadFile.

    Thanks. I will do that after I download each file. In preliminary
    testing, it seems to work nicely.

    > It would be rather surprising to see exceptions related to the strong name
    > being thrown because of any problem with the authenticode signature. A
    > couple of more likely causes might be the following:
    >
    > 1. The assemblies are delay-signed rather than fully signed.
    > 2. An unexpected/incorrect version of a dependant assembly is being used by
    > the client.

    The assemblies are signed in the AssemblyInfo.vb file as such:
    <Assembly: AssemblyVersion("2.0.14.0")>
    <Assembly: AssemblyKeyFile("W:\mycerts\mykeys\mykey.snk")>
    It is possible that unexpected/incorrect versions of dependent
    assemblies are being called. I will try using the
    GetReferencedAssemblies method on the main application to verify that
    the versions match.

    Thank you very much for your help.

    Dave.

  • Next message: Tony Amos: "Network File Access"