It is

Made a C/S system used in local LAN.
A ADODC connection,
Then the server password periodically change over there,
So the password each client have to change on a regular basis.

The password stored in each client with what method is better? With that kind of encryption method?

CodePudding user response:

Two kinds of methods, one wearing a ASP before each connection, even the ASP, ASP after verification to the corresponding server password, or directly on the server to generate a connection file, just add some password, every time even, take over,

CodePudding user response:

Can again a little bit advanced server automatically change the password after each of the connection is successful, then the password can be generated through your client request access to an encrypted

CodePudding user response:

With a disrupted clock order BASE64 processing is enough,

CodePudding user response:

Ask the user to enter a password each time

CodePudding user response:

Must have to put a fixed location, program take the password to a fixed place,

CodePudding user response:

Password is not stored in the program, after encryption stored in file, when read into to decrypt,
So unless some people understand the reverse or cracking,

This open compilation good EXE binary is directly see the password

CodePudding user response:

Security chip chip (password) I do this line, also engaged in the social security card before such as business, also know to card, social security card works, the various life cycle

In theory, the password (password) stored in the PC, for professional attackers, equals to him, even if is encrypted,

The most cheap and safe way, using a smart card (CPU card), using two-way authentication login, must use the password way (if security requirements is not high), can be set up in the card with the same password generation protocol server,

In addition, there is a kind of dynamic password key, including real time clock chip, generate different password per minute, as long as the server has the same generation algorithm with it,

CodePudding user response:

To eliminate a human brain to remember password?
Biological characteristics such as fingerprint identification, gait recognition, face recognition? Copying fingerprint, fingerprint refers to the set, instability and to authorize others to use not convenient...
Mixer password card... Be copied, easily lost, forgotten, or break...
Documents, can be forged
I guess at least 50 years,

CodePudding user response:

The original poster is to want to "cache user password," password on the server did not change, automatic connection?
If this is the case, the local file encryption must use "reversible encryption algorithm",

If it is to validate user input password is correct, that it is best to save the irreversible "the algorithm",
I think it just doesn't make sense, because the server password will change, but change the "client" you may not know,
When "local authentication failed, you can not be sure is password mistyped, or because the password has been change,
Of course, all of the password, change through your "client" except when operating;
This situation can be considered to local, local through again after the server authentication way,