Ah, I'm no crypto expert (I'll defer to the gurus) but if memory serves AES did not adopt Rijndael to the letter, it made some modifications so the output of both functions would expectedly differ.
Glad you found your solution. Regards, Joel > -----Original Message----- > From: monodroid-boun...@lists.ximian.com [mailto:monodroid- > boun...@lists.ximian.com] On Behalf Of bjarke > Sent: Friday, 13 July, 2012 2:59 PM > To: monodroid@lists.ximian.com > Subject: Re: [mono-android] Is AesCryptoServiceProvider not implemented? > > Hi thank you for the enlightening answer. > > My problem was that at first i used the RijndaelManaged which not gave the > exact same result as AesCryptoServiceProvider which i use in a webservice. > However using the AesManaged gave the the same results and therefore i use > this for my implementation. > > -- > View this message in context: http://mono-for- > android.1047100.n5.nabble.com/Is-AesCryptoServiceProvider-not-implemented- > tp5710843p5710858.html > Sent from the Mono for Android mailing list archive at Nabble.com. > _______________________________________________ > Monodroid mailing list > Monodroid@lists.ximian.com > > UNSUBSCRIBE INFORMATION: > http://lists.ximian.com/mailman/listinfo/monodroid _______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
