[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: ssh+svn vs. bash security bug?

From: Stefan Sperling <stsp_at_elego.de>
Date: Thu, 25 Sep 2014 11:08:31 +0300

On Wed, Sep 24, 2014 at 07:30:57PM -0400, Nico Kadel-Garcia wrote:
> Setting up a chroot for Subversion for just this purpose gets...
> potentially adventuresome. The maintainers of OpenSSH have generically
> refused to support chroot changes, so it's a bit awkward to even set
> up. Various folks have published patches or integration kits to
> support genuine chroot cages: heck, even I used to publish patches for
> OpenSSH to provide them.

I have to admit that while I did successfully chroot svnserve with
svn:// once, I've never tried to chroot svn+ssh://

But I'd be surprised if OpenSSH was making this difficult.
The ChrootDirectory configuration option of OpenSSH won't do?
If so, why not?

Upgrading bash is a better solution to this particular problem,
of course, but using a chroot containing the minimum components
could still be a good idea in general.
Received on 2014-09-25 10:09:15 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.