http - Shared Secret Key Length -
I am trying to create an authenticated HTTP service endpoint using shared secrets.
Is a good example.
I want to know what is the best public key and secret key length ? I'm pretty sure people will say arbitrary, but want to know what the general opinion is and why.
Another question, Flickr uses MD5 to generate "signature". I have read that MD5 is no longer safe, are MD5 options ? And as the service users will need to make this signature, bonus points and multi-platform library support for ease of use.
How secure is your service? What if someone would force the death of the father? And if you are really worried, why are not you using SSL with client-side certificates?
These are common questions that you need to answer for your particular project, before you can decide the best way to encrypt. Case study: In the application I am developing, I must encrypt (not hash) key data using the DES (Yes, plain DES), and all the URLs decrypted by the service must be generated by the server. , Which contains the shared key. There is an optional timestamp for limiting the validity of the URL: If you access the service with any Exercise URL, you get 403 backgrounds. If the data in question is relatively low, and encryption is broken, then no betrayal will be considered.
Can it break down from consumer devices? Sure.
Is there a high payoff to break it? off course not.
Why not just send data in plain text? Because we want to ensure some level of control, my primary goal is to keep the script KVD from continuous service insinuation with repeated inserts / updates.
Incidentally, communication between client and server does not appear elsewhere. This means that, even if an animal receives the power of the keys, then for them to learn some estimates have to be implemented that they have broken the key, through the invisibility, yes, but sometimes the blindness is useful .
Comments
Post a Comment