[Mono-bugs] [Bug 615445] New: Microsoft F# dll needs to be re-signed on Mono

[bugzilla_noreply at novell.com]

http://bugzilla.novell.com/show_bug.cgi?id=615445

http://bugzilla.novell.com/show_bug.cgi?id=615445#c0


           Summary: Microsoft F# dll needs to be re-signed on Mono
    Classification: Mono
           Product: Mono: Tools
           Version: 2.6.x
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: gacutil
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: laurentlb at gmail.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---


Created an attachment (id=370100)
 --> (http://bugzilla.novell.com/attachment.cgi?id=370100)
FSharp.Core.dll from Microsoft website

User-Agent:       Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1;
Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729;
Media Center PC 6.0; InfoPath.3; .NET4.0C; .NET4.0E)

Look at the attached file "FSharp.Core.dll" (coming from http://fsharp.net -
the .zip release).

Following a discussion on mono-devel-list:

On Fri, Jun 18, 2010 at 2:24 PM, Sebastien Pouliot
> I have been
> told that: "Mono runtime currently automatically maps anything signed
> with Microsoft keys to the key they sign their Mono provided versions
> of the binaries with.  That makes sense for most Microsoft things,
> which they need to reimplement themselves.  But for FSharp.Core, they
> do not implement it themselves, and users need to be able to run the
> Microsoft signed version of that binary on Mono directly.  The ideal
> fix here is for Mono to know this and make it possible to skip this
> auto-redirecting of strong name."
>
> I'd like to know what Mono developers plan to do, and what are your suggestions.
> I could also package the Mono-signed binary,

For the future please open a bug report (bugzilaa.novell.com) and attach
the .dll on it. I'll take a look to see which key is being and how we
could handle this case.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

-- 
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.