[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [PATCH] Better handling of wrong passwords or no passwords for client certificates.

From: Ben Reser <ben_at_reser.org>
Date: 2003-11-30 04:36:34 CET

On Sat, Nov 29, 2003 at 08:31:12PM +0000, Philip Martin wrote:
> Thanks! See r7872, I also made some other changes to tidy up the
> code.
> Questions (not specifically for Ben)
> - do we need to notify the user if the decrypt fails?

I was wondering why there wasn't a retry setup for at least the pw if
not the certificate. I think it makes a lot of sense to take and allow
clients to specify a retry limit. They can't really be sure that the
certificate or the password were good.

The other question is how do you notify the user that the decrypt
failed? I don't think there's really any good way of telling the client
that and printing to STDERR from the library doesn't seem right either.

So I'd say we should have a retry limit, asking for the cert/pw again is
pretty intuitive that there's something wrong with what you gave before.

Ben Reser <ben@reser.org>
"Conscience is the inner voice which warns us somebody may be looking."
- H.L. Mencken
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Nov 30 04:37:08 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.