On Wed, Apr 02, 2008 at 11:05:30AM -0400, Mark Phippard wrote:
> This is probably a question for Windows builds more than anything, but
> it applies everywhere to some degree. Is there an ideal Neon
> configuration to use when building? For example, it seems like Neon
> is supporting more features with GnuTLS than it does with OpenSSL.
> Should we be building Neon using this instead of OpenSSL? What about
> things like GSSAPI support? Are there other components that we ought
> to be incorporating when we build Neon.
For Windows it would be good to be enabling SSPI support, it doesn't
look like that is done out of the box in neon.mak, though I don't know
if that adds some hard DLL dependency or whatever. I haven't tested
neon with GnuTLS on Windows nor is it that combination supported in
neon.mak.
For Unix it is hard to make any general recommendations for a binary
distribution. GSSAPI support is enabled out of the box on systems with
the GSSAPI libraries present at configure-time. That is a shared
library dependency like any other.
On Unix, neon's basic SSL interface has 99% feature parity between
GnuTLS versions >= 2.x and OpenSSL; SVN doesn't currently use the 1%
that is missing in GnuTLS, so you can choose either. I would generally
recommend GnuTLS over OpenSSL, since I prefer the API, code, and license
of GnuTLS, but YMMV.
w.r.t. PKCS#11 (smartcard) support in neon, that will not work on
Windows currently (pakchois would need to be ported), and I'm not sure
if it even makes sense to use PKCS#11 on Windows.
jow
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-04-03 00:01:17 CEST