You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Mark Phippard <ma...@gmail.com> on 2008/04/02 15:05:30 UTC
Ideal Neon configuration?
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.
By "we" I am referring to those of us that are building Subversion
binaries. It seems like Neon has grown in features beyond what we
describe in our SVN INSTALL document. So I am just wondering if there
are features and build options that we are not all aware of if we do
not follow Neon separately. Also, does our SVN build process support
building Neon this way. On Windows we build Neon as part of SVN
build.
I know there are users out there want to use things like Kerberos or
Smart Cards etc. I'd like to offer builds that enabled these
features. Of course, these same build would presumably need to still
work with more conventional setups.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Ideal Neon configuration?
Posted by Mark Phippard <ma...@gmail.com>.
On Thu, Apr 3, 2008 at 11:19 AM, Stefan Küng <to...@gmail.com> wrote:
> Joe Orton wrote:
>
>
> > 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.
> >
>
> To enable SSPI with neon, define HAVE_SSPI in config.hw.
> It does not add a dll dependency which isn't available on all Windows
> versions anyway, so no need to ship additional dlls.
Doe the SVN build on Windows not do this by default? I thought it
did, but maybe it was pulled back when there were some SSPI problems.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Ideal Neon configuration?
Posted by Stefan Küng <to...@gmail.com>.
Joe Orton wrote:
> 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.
To enable SSPI with neon, define HAVE_SSPI in config.hw.
It does not add a dll dependency which isn't available on all Windows
versions anyway, so no need to ship additional dlls.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Re: Ideal Neon configuration?
Posted by Joe Orton <jo...@manyfish.co.uk>.
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@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org