Hi, I am not an expert on cryptography, thus take this with a grain of salt :)
I thought the purpose of a private key is for you to de-crypt messages encrypted with your public key. If my logic is correct, then wouldn't the remote service give you their public key to encrypt the message (sent from you to the web service). Isn't your task to send a message, Are you sure you are using the correct key? Next, the output of a cipher differs from instance to instance. Thus, the encrypted output being different is expected? Did the server send you any details. That's what I meant by stack trace (poor wording on my part). Did the server indicate specifically that it didn't recognize the encryption format (e.g a padding exception)? Good Luck Jason On Sunday, January 13, 2013 2:50:48 PM UTC-6, mbarbiero wrote: > > > > Em domingo, 13 de janeiro de 2013 18h17min29s UTC-2, jason_gates escreveu: >> >> Hi, >> Thank you for the response :) So, the private key is not part of the >> issue, right? Wouldn't your private key only be used to decode a message >> sent from the web service to you? Per your message, that's not your issue. >> > >> Your saying the remote web service is rejecting the message you are >> sending, I assume you are using the public key of the web service to encode >> the message (you are sending)? Is that correct? >> > > -> I sign the XML with my PrivateKey and send a copy of my PublicKey. The > access to webservice is in HTTPS. > > >> Have you compared the xml sent from both clients (android and doNet). Is >> the result of that verification, the only difference is the >> "SignatureValue"? In other words, the xml structure from both clients are >> identical. >> >> -> Yes, SignatureValue is the unique difference. > > Do you have a stack trace from the server that we can translate? I'm just >> trying to see if there are any more clues. >> > > -> Unfortunately not! > >> >> What I've found is, different versions of the BouncyCastle library are >> incompatible. If you encode a value with an earlier version of BouncyCastle >> and then try to decode the value with a later version of BouncyCastle, an >> exception is raised. >> >> Do you have access to the source code of your "doNet" client. Can you see >> which library (and version) the other client is using and which algorithm >> (the algorithm should be published). >> > > -> Tomorow I'll seek the source code and post here > > Thanks. > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
