On 25 Nov 2002, Ben Collins-Sussman wrote:
> <rbb@apache.org> writes:
>
> > I am working on adding SSL server-key verification to the svn client, but
> > it requires interaction with the user. Is there a standard way of doing
> > this or should I just use APR's stdin/stdout handles?
>
> Very cool, glad you're doing this!
>
> I think we need more context from you, more specifics about what you
> want to see happen.
I am basically following the comments in session.c in libsvn_ra_dav.
Basically, once the SSL cert is received, we check it against a cert file
in the ~/.svn directory. If the cert is valid, we are good. Otherwise,
we prompt the user to determine if we should accept the cert for the
session, forever, or reject it. I think I know how to do all of this, but
prompting the user was stopping me.
> Here's a preliminary answer: only a client application (i.e. the user
> of libsvn_client) is allowed to interact with the user directly and
> use stdout/stdin. Up till now, this has been extremely rare.
> libsvn_client has defined specific callbacks for this. For example, a
> client application has to provide a function of type
> "svn_client_prompt_t" so that libsvn_client is able to ask users for
> names/passwords whenever neon receives a challenge. I'm guessing you
> would want to define more callbacks like this.
Great! This is exactly what I was looking for.
> Also, you might want to investigate if your changes tie into a larger
> project -- the creation of libsvn_auth. gstein has a Grand Plan to
> move all our auth code in there and make it very pretty. He can talk
> more about that. Right now, that library is just a hollow shell.
I'm not really ready to get into SVN this much yet. I may look into this
after I have the patch, but I need to get my feet wet first.
Ryan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Nov 25 18:21:30 2002