Mango issue

Oct 11, 2011 at 10:40 AM
Edited Oct 11, 2011 at 10:41 AM

Hi,

When switching from the 7.0 WP7 framework to 7.1 Mango, the generated signature doesn't seem to match the signature of the desktop .NET Framework RSACryptoService provider.

Any news on that?

 Thanks,

Bart

Coordinator
Oct 11, 2011 at 1:08 PM
No but I'll have David test it. There shouldn't be any difference in the signature generation. Could you provide us sample code for how you're using it so we can confirm?
Oct 12, 2011 at 9:29 AM

We first suspected that the RSACrypto class behaved differently, but we missed to see that the signed XML missed some cariage returns.

So the RSACrypto class does it's job well at Mango also.

The problem was that 7.1 creates it's xml differently than the 7.0.

Thanks.

Coordinator
Oct 12, 2011 at 1:32 PM
Awesome, thanks for letting me know. It's interesting that the carriage returns would make a difference... the XML should be able to be parsed regardless of whether there are carriage returns between the elements.

On Wed, Oct 12, 2011 at 3:29 AM, BartVB <notifications@codeplex.com> wrote:

From: BartVB

We first suspected that the RSACrypto class behaved differently, but we missed to see that the signed XML missed some cariage returns.

So the RSACrypto class does it's job well at Mango also.

The problem was that 7.1 creates it's xml differently than the 7.0.

Thanks.

Read the full discussion online.

To add a post to this discussion, reply to this email (scrypt@discussions.codeplex.com)

To start a new discussion for this project, email scrypt@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe or change your settings on codePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com