I have captured request content of a mobile app (iphone) through a proxy (Charles Proxy), but the content seems to be encoded which I want to decode into human-readable format. As the source of the encoding format is not known, I cannot decode it, I have tried several online tools with different source formats but none of it decode it properly. How to decode such content properly?
pv8WkNKPolGj6EgiYKNXzlGAOjGku5ewenklAlyQ58wpWcLBH7y4S0ZZ12JODvWSLpvoJbeffKgDxvaTMTt17qLUNKsiTroaldStWO5n+H1BdI+IXLFusgipOtpUUvnvbA52x0Gwi349bfXNCD9EamQBEPD8J+zreVtYwvgL9b7ohgvnoq2WXpOeHs9hTJnWEwAiLzPTocVDzr3kzLsMsB6N10X+pnJ/QODY3RDklqQeb5o6vzvTapgs5G/R2ZjsvzBTJ/u+DuLxulVfNUAKXGjh4CVAWjWzsymuxo1CaI7s3nPW17Kx9BNYxw37r4TKAqTMA+A0uP+NPi17KsC9ag==
UPDATE:
The request/response content is encrypted by java cryptography before sending it in the network using the AES cipher algorithm and cipher transformation is done with AES/CBC/PKCS5Padding. I am able to decrypt it by debugging APK code and finding the secret key used to encrypt the content. It's really another level of encryption before sending it in the network.
Related
I am trying to simulate email from a secure email account using Jmeter.
Any attachments that I send are not being encrypted using Base64 as the emails are when sent from the same email address manually. this is causing a problem whereby the application that picks up the attachment to process fails to decode the email.
How can I get Jmeter to submit the email with attachment with content-transfer-encoding of base64?
If all you need to do is to perform base64-encoding of the message body - you can perform it via __base64Encode() function available via Custom JMeter Functions bundle and can be installed using JMeter Plugins Manager.
However be aware that it can be easily decoded back even using online tools so I doubt that it makes sense to rely on Base64 for security.
You can always call underlying Java Mail API functions from JSR223 Test Elements if JMeter cannot fully fulfill your requirements.
In HTTPS, only server hold the private key and is able to decode the message.
My doubt is whether server will encode the response before sending it to client?
If so, how does the client decode it, since it does not have the private key?
If not, how does it prevent others from tampering the response message?
I think I can answer my question by myself. The server will encrypt the response with public-key and send it to client. Other than that, the server will send a checksum as well, which acts as the signature. The checksum is generated based on the private-key that only server knows, therefore it is hard for others to fabricate it. Thus, if anyone trying tampering the message, it won't match the checksum.
In a IDP initiated environment the payload is not able to decode it.
Getting exception in decoder.decode(samlContext);
So after analysing I found that the payload is encrypted with URL encoding after Base64 encoding.
Any way there if I can consume this payload and decode it.
This issue I was facing due to some copy paste issue, now solved.
I'm trying to debug a problem with some HTTPS requests that the Firefox developer tools are sending (specifically, the source maps - if I turn on "Show original sources" I get a 404 error instead of JS source).
I've captured some HTTPS logs with dumpcap + firefox + SSLKEYLOGFILE, but now it feels like the tools are falling apart.
I've got the decrypted SSL data, but the content is gzipped! I can't read this!
How do I get Wireshark to parse the decoded SSL data as an HTTP stream?
The Follow SSL Stream option is a generic SSL dissector feature that displays the raw contents of SSL plaintext data. In your capture, the HTTP response body is compressed, but that is completely opaque to the SSL dissector.
Wireshark can decompress the compressed HTTP response body, be sure to enable it at Preferences -> Protocols -> HTTP -> Uncompress entity bodies. After that, there will be a Uncompressed entity body tab on the bottom of the byte view in the main window.
In our application we are reading mail body which client have replied to our mail address and saved it to our database table.
When some clients reply on our email address mail body contains base64 string with header Content-Transfer-Encoding: base64.
Can I know if there is any configuration setting on mail server that it will convert the base64 string into image.
This problem occurs only with some clients not all. I am guessing that these clients have base64 image in their signature.
Any help will be much appreciated.
Please check below image for what response we get in our application.
It isn't the server that needs to convert anything. base64 encoded images are already images.
It is your client, whatever you are using to view the emails that needs to interpret the embedded base64 encoding and display it as an image to you.