Intercepted request log shows user's entered information without encryption about angularjs-crypto HOT 1 CLOSED

Hi,

you are right. This logging is there for developing purpose.
I think of to cut it out or make it configurable. Tomorrow
morning i change this or feeling free to submit a
change request.

Thanks for this advice.
Regards
Frank

Von meinem iPhone gesendet

Am 29.04.2015 um 17:47 schrieb Amir Al Take [email protected]:

Hey,

I found that when I send a request which contains data that is supposed to be encrypted by using POST, in the console log it shows the raw data even though default parameter (_enc) was added at the end of specific field that is wanted to be encrypted and following code was added to the app.js of web application:

.run(['cfCryptoHttpInterceptor', function(cfCryptoHttpInterceptor) {
cfCryptoHttpInterceptor.base64Key = "16rdKQfqN3L4TY7YktgxBw==";
}]);
This happens in line number 20 in file angularjs-crypto.js. Here's an example:

Let's suppose that I want to send following object to the backend:

{id: 1, data_enc: "Hello"}
When you run your application and try to send that object, first is called angularjs-crypto.js library and it goes the code through until it comes to line 20, which is:

console.log("intercept request " + angular.toJson(data));
Here data is simply:

var data = request.data;
At this phase it will expose the raw data that is wanted to be sent with request and which must also be encrypted. Once you have run your application and open console log for example with Chrome, it shows following at angularjs-crypto line 20:

intercept request {"id": "1", "data_enc":"Hello"}
This is something that could be fixed.

—
Reply to this email directly or view it on GitHub.

from angularjs-crypto.