Re: Searching for a special challenge&response algorithm



David Sharpe schrieb:

Mr. Unruh is right. You're making this problem needlessly
complex/imagining a problem that is hardly there.

That may be. But from my point of view you are making too many assumptions
which are incorrect in my case.

Server side, only accept an authentication request PER ACCOUNT once
every thirty seconds.

That is a nice way if your accountnames can not be easily guessed.
Otherwise it is a perfect starting point for a DOS attack...

In other words, each user needs his OWN private
authentication key.

As I said I don't talk about SSH. I do not have to possibility to use
public key authentication and I do not have personalized accounts.

If you are trying to consider an account where multiple users are using
the same key, then your security problem is already bigger than a
simple brute force attack. However, if you NEED this to be the case,
then yes, as Mr. Moreno goes on to say: block per IP. One thousand
connections would require one thousand IPs.

And clients which connect through a proxy are seen on this per-IP-basis as
one client which is definitely wrong. This is why I want to use something
which belongs only to one client.

Jan
.



Relevant Pages

  • Re: OpenSSH: force password authentication
    ... > server to run an automated backup job. ... > close the ssh connection, ... client in the default location for the client identity. ... Or just disable public key authentication. ...
    (comp.security.ssh)
  • SSH "failed none" syslog entries causing Linux failed login counter to advance.
    ... When looking at the syslog entries it shows a failed ... I have turned off rhost and even public key authentication in both the ... client and server configuration files. ... What is SSH attempting before the password is entered, ...
    (comp.security.ssh)
  • Re: Public Key authentication not responding to public key?
    ... > I'm having difficulties setting up public key authentication ... whereas I have set up PKA between ... You don't say which client or server you're using. ... Good judgement comes with experience. ...
    (comp.security.ssh)
  • Re: sftp
    ... client. ... will be using the sftp and none of them are savvy enough ... Public key authentication ... Transmission is equally secure. ...
    (microsoft.public.security)
  • Re: [SLE] stopping dictionary attacks on sshd
    ... >> make use of public key authentication. ... With no chance to log in, ... Create key pair, in client. ... Send public part (server_dsa.pub) to server. ...
    (SuSE)