[Mono-bugs] [Bug 654637] Wrong PublicKey when accessing missing keycontainer

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Thu Nov 18 10:27:30 EST 2010



Sebastien Pouliot <spouliot at novell.com> changed:

           What    |Removed                     |Added
                 CC|                            |spouliot at novell.com

--- Comment #1 from Sebastien Pouliot <spouliot at novell.com> 2010-11-18 15:27:29 UTC ---
Mono use managed code (from the fx) to handle strong names while MS only has an
unmanaged API. However the behavior from the both (unmanaged and managed) API

The FX (which Mono re-use) will create a new key pair for a unknown (empty)
container. We cannot change this behavior as this is the only way to create new
key pairs (in containers) using the FX. OTOH the unmanaged API use CryptoAPI
which has a more direct control over creation of the containers.

Anyway that, in turns means, there will always be a public key available for
any container - so creating a StrongNameKeyPair won't fail (on Mono) for
un-existing key/containers.

note: I'll check if recent FX version added some flags to cover this... they
did not exists when this got implemented but there's a slight chance this has
evolved (but don't hold your breath ;-)

Configure bugmail: https://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.

More information about the mono-bugs mailing list