On Wed, 29 Apr 2009, webpost_at_tigris.org wrote:
> Trying to repo-browse an svn+ssh:// repository, using TortoisePlink as
> the SSH backend, I was prompted for my password. Since I never use
> passwords generally (only keys), I knew I hadn't set something up
> properly. So, to correct the situation, I tried to cancel, and was
> prompted for my password half a dozen more times (sshd_config has the
> default MaxAuthTries 6). Then I was prompted again... seemingly without
> It'd be nice if TortoisePlink would propagate the 'Cancel' up to the
> Repository Browser (rather than treating it the same as a failed auth
> attempt). I eventually had to kill it via Procexp.
(That was me reporting via the web interface.)
After I submitted that, I found a message from Stefan Küng on 2009-01-24:
> > [original reporter was "Joe"]
> > [...]
> > a password lockout, so it just keeps asking and asking. I don't think
> > being locked out of the server would be good either. All I can do is
> > close the TortoiseProc and TortoisePlink with the task manager.
> That's how Plink is implemented. And actually, Cancel sends an empty
> string back to indicate the cancel. If the server doesn't react to that
> (or reacts wrong) there's nothing Plink can do - and TortoisePlink is
> just an UI patch to Plink.
This still seems broken to me. "Cancel sends an empty string back to
indicate the cancel"? If I pick up some tuits, I may try and patch this.
( trunk/src/TortoisePlink/LoginDialog.cpp looks like the starting point,
if not the endpoint )
Otherwise, at least it's explained (and can probably be a WONTFIX --
certainly not high priority).
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-04-30 16:15:15 CEST