X
X
xmoonlight2013-02-03 08:31:50
Algorithms
xmoonlight, 2013-02-03 08:31:50

Login algorithm with protection of authorization data from being used when intercepted on the channel?

I am making a user zone on a website with an increased security system.
It is necessary to implement without installing a certificate or token, as well as any "hardware" (except for the standard ones: "mouse" and keyboard), an input with protection of authorization data from being used when they are intercepted on the channel.
Those. the usual way: login and password.
Registration (once) and authorization (periodically) is required. (standard requirements...)
Any thoughts? What algorithms to watch, tell me.
In advance, thank you all for your help.

Answer the question

In order to leave comments, you need to log in

7 answer(s)
A
Andrew, 2013-02-04
@xmoonlight

Tell me, what additional threats do not allow using something like primitive CRAM-MD5 (quickly, everything is on the client and on the server)?

A
Alexey Huseynov, 2013-02-03
@kibergus

I understand correctly that you want to improve the security of the system without changing anything in the authentication / authorization mechanism? Then, apart from using SSL encryption of the channel, you can not advise anything.

B
bypasser, 2013-02-03
@bypasser

Joining HTTPS.

V
Vitaly Peretyatko, 2013-02-03
@viperet

Read about authentication with salt habrahabr.ru/post/121021/

@
@ntkt, 2013-02-03
_

Use HTTPS + authentication with SRP-6, as suggested by colleagues above.
1. Properly configured HTTPS will provide reasonable security for the communication channel (if users are minimally conscious).
2. SRP-6 does not allow intercepted data to be reused and does not allow guessing the original password based on them.
Even if an attacker bypasses SSL, for example, gains access to the private key from your server certificate, or from a higher one in the certificate chain, up to the root ones, and conducts a MITM attack using a fake SSL certificate that is legitimate from the point of view of the client browser, then the intercepted the attacker will still not have enough information to authenticate instead of the user.
Instead of SRP-6, you can use weaker standards like htdigest (HTTP digest authentication, rfc2617, is available in Apache out of the box, however, in the simplest use case, it will look like an ugly standard pop-up window to the client in the browser).

A
Alex, 2017-06-09
@asilonos

Login , password and one time password totp, based on Google Authenticator

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question