I'm excited to play with SASL. But will the repository format change again
the way that it did in 1.4? We've worked hard on triggers in java with
svnkit. If the format changes and svnkit breaks, I could be in hot water ;]
Dave
On 12/7/06, Dave_Thomas mailing lists <davelist@peoplemerge.com> wrote:
>
> I'll take this up with my team. I don't see a problem other than the fact
> that we're going to need to move our system into production in the coming
> months. Prerelease code + production system = a bad idea.
>
> Any rough ETA on 1.5?
>
> Dave
>
> On 12/6/06, Ben Collins-Sussman <sussman@red-bean.com> wrote:
> >
> > Maybe Dave Thomas would like to deploy our trunk code, as an early
> > tester of svnserve-SASL? :-)
> >
> >
> > On 12/6/06, Vlad Georgescu <vgeorgescu@gmail.com> wrote:
> > > On 12/6/06, Dave_Thomas mailing lists <davelist@peoplemerge.com >
> > wrote:
> > > > Hi,
> > > >
> > > > I see recent active discussions. Has a SASL-enabled server been
> > > > implemented?
> > >
> > > Yes, support for Cyrus SASL authentication is already integrated into
> > > Subversion /trunk, and will hopefully make it into the next minor
> > > release (1.5.0). Cyrus SASL supports several password-checking
> > > mechanisms that use encrypted passwords, such as:
> > >
> > > - GSSAPI (Kerberos)
> > > - authentication mechanisms that use non-plaintext secrets, such as
> > > OTP (One-time Passwords) or SRP (Secure Remote Password)
> > > - PAM, /etc/shadow (however this would also require SSL support,
> > > otherwise the password _transmission_ wouldn't be secure)
> > >
> > > --
> > > Vlad
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> > > For additional commands, e-mail: dev-help@subversion.tigris.org
> > >
> > >
> >
>
>
Received on Thu Dec 7 20:59:03 2006