> 'u's meaning is left up to the callback. It could be a prompt phrase a
> window handle or ignored. It was added because there was a
> need to send
> info to the callback.
I do nothing with u yet... I'm just hard-coding the passphrase till I can
get something to work.
> There is an additional
to. If the operation
> fails return 0.
>
> strcpy( buf, password );
> return strlen( buf );
>
> I think size is the length of buf if you want to make overflow checks.
>
> > -Original Message-
> > From: Randall Ward [mailto:[EMAIL PROTECTED]]
> >
I know know lots and lots about client authentication and certificates.
Thanks everyone for your help!
Now: there's one big thing that I don't understand. If I am going to be
building an https client that will authenticate itself with a certificate of
some kind, does that client need to have acce
I've been building a small https client & everything has gone quite well.
Now I've been told that I need to include support for client authentication
using a standard x.509 certificate & I am stumped.
Is the certificate just going to be a file? Do I just have to set a path to
it, or is there some
