Skip to main content
Information Security

Return to Question

Bumped by Community user
Bumped by Community user
Bumped by Community user
Bumped by Community user
deleted 395 characters in body; edited tags
Source Link
schroeder ♦
schroeder ♦
  • 132.1k
  • 55
  • 307
  • 348

I'm working on a project in college in which our objective isproject to understand how the IOS Applicationapplication sends the password in the REQUEST already encrypted in AES128, what is its key, and send a REQUEST with our string transformed into a password encrypted with AES128 in the same way, did. We were not specifygiven any specific method in which we should actto accomplish this, we are free to use whatever is useful to accomplish this.

No response from the application's requests returns the password encryption key.

The question I want to ask you, with all due respect, based on your experiences, what method would you use to discover this key?

Remembering that reverse engineering methods with Traffic CaptureWe have performed traffic capture and SSL Pinning in IOS has already been performed.

Me and my designated team already have a hot head trying to resolve this issue, our last hope was to appeal to this forum with people more experienced than us.

WouldWhat method would you be willinguse to embark ondiscover this journeykey?

Other teams have already succeeded, but the information cannot be shared, the purpose of the task is precisely for the teams to use the methods they have chosen to send a request with encryption encoded in its string.

I'm working on a project in college in which our objective is to understand how the IOS Application sends the password in the REQUEST already encrypted in AES128, what is its key, and send a REQUEST with our string transformed into a password encrypted with AES128 in the same way, did not specify any method in which we should act, we are free to use whatever is useful to accomplish this.

No response from the application's requests returns the password encryption key.

The question I want to ask you, with all due respect, based on your experiences, what method would you use to discover this key?

Remembering that reverse engineering methods with Traffic Capture and SSL Pinning in IOS has already been performed.

Me and my designated team already have a hot head trying to resolve this issue, our last hope was to appeal to this forum with people more experienced than us.

Would you be willing to embark on this journey?

Other teams have already succeeded, but the information cannot be shared, the purpose of the task is precisely for the teams to use the methods they have chosen to send a request with encryption encoded in its string.

I'm working on a college project to understand how the IOS application sends the password in the REQUEST already encrypted in AES128, what is its key, and send a REQUEST with our string transformed into a password encrypted with AES128 in the same way. We were not given any specific method to accomplish this, we are free to use whatever is useful.

No response from the application's requests returns the password encryption key.

We have performed traffic capture and SSL Pinning in IOS.

What method would you use to discover this key?

Other teams have already succeeded, but the information cannot be shared, the purpose of the task is precisely for the teams to use the methods they have chosen to send a request with encryption encoded in its string.

Source Link
nav4rro
nav4rro
  • 1
  • 1

Discovering already encrypted REQUEST key AES128 and sending already encrypted REQUEST with other data

I'm working on a project in college in which our objective is to understand how the IOS Application sends the password in the REQUEST already encrypted in AES128, what is its key, and send a REQUEST with our string transformed into a password encrypted with AES128 in the same way, did not specify any method in which we should act, we are free to use whatever is useful to accomplish this.

No response from the application's requests returns the password encryption key.

The question I want to ask you, with all due respect, based on your experiences, what method would you use to discover this key?

Remembering that reverse engineering methods with Traffic Capture and SSL Pinning in IOS has already been performed.

Me and my designated team already have a hot head trying to resolve this issue, our last hope was to appeal to this forum with people more experienced than us.

Would you be willing to embark on this journey?

Other teams have already succeeded, but the information cannot be shared, the purpose of the task is precisely for the teams to use the methods they have chosen to send a request with encryption encoded in its string.