« first day (3290 days earlier)      last day (49 days later) » 

12:10 PM
So, we always say to sanitize data before saving to prevent mysql injection and so on. But I'm wondering, do I have to do this even when I'm saving data from a reputable source ( such as a google or amazon api)?
 
In cryptography and computer security, a man-in-the-middle attack (MITM) is an attack where the attacker secretly relays and possibly alters the communications between two parties who believe they are directly communicating with each other. One example of a MITM attack is active eavesdropping, in which the attacker makes independent connections with the victims and relays messages between them to make them believe they are talking directly to each other over a private connection, when in fact the entire conversation is controlled by the attacker. The attacker must be able to intercept all relevant...
 
12:26 PM
But it's an HTTPS connection? Are we really to consider the possibility of someone deciphering a 1024bit encrypted connection too?
 
 
5 hours later…
5:06 PM
@JackJohansson yes, always. Whats the worst thing that might happen, that you spent another hour developing it and a waste of few CPU cycles handling each request? Compare this with the damage caused by inserting wrong data into the DB which causes it to be unustable.
this is not even about security, just having your system more resilient
This ofcourse do not mean that you need to check the correctness of the CRC in the TCP/IP packet. If you use API that you can relay on, there is no point in checking its inner working, but you always need to be ready that the data you get back might be corrupted for whatever reason.
 
 
2 hours later…
7:38 PM
even without a MITM attack you don't know for sure that the 3rd party is secure
or that the data really matches your expectations
or that the data recieved actually came from a connection from google, it could have been modified on your server by other means
 

« first day (3290 days earlier)      last day (49 days later) »