cryptography - Encryption: How to turn an 8 character string into a 128-bit key, 256-bit key, etc? -
I have tried to research it, but still some questions were left unanswered. I was finding out how an 8-character password would change in a high-bit encryption key. During my research, I get articles that will talk about salt prices.
Assume that you can find all 256 characters to play, then an 8-character password will be 64-bit long. Therefore, the remaining 64 bits have only one salt value. And, if I am wrong then correct me, but it is done that if anybody all was going to try potential values (Brahma force), then they have to try all the bits from 128 Even salt is also unknown.
My question is in fact related to this 'salt' value:
- When someone makes an application, then does it contain hard working salt? And if so, can not it be achieved through executable reverse engineering?
- If salt is produced at random, then I think there should be a way to duplicate it, then it is not the work that makes a random salt reverse engineer, so that it gets the salt value Can be forced to duplicate?
- It may be outside the scope, but if the value of a salt is generated on a server side (of the client / server relationship), will it have to be shared with the client, so that they Can I decrypt the data sent? And, if it is being sent to the customer, can it not be useless, which makes it worthless?
- Is there any other way which is used in addition to this 'salt' value which is a 8-character string in a strong encryption key?
1) Each password is salty in a different way, and with salt hash Is deposited.
2) It is archived.
3) No, customers never decrypt anything. It sends the password, which salts the server, hash and compares.
4) Yes, I will add some links
Comments
Post a Comment