From: Bill Stewart <bstewart@iname.com>
To: cygwin@cygwin.com
Subject: Re: sshd privsep user still required?
Date: Wed, 13 Mar 2019 15:58:00 -0000 [thread overview]
Message-ID: <CANV9t=RxeKVye=uJ9s=7ncp6jHbyMxAUsRGKa6zEc1VdkCfu+g@mail.gmail.com> (raw)
In-Reply-To: <20190313152901.GA18873@calimero.vinschen.de>
On Wed, Mar 13, 2019 at 9:29 AM Corinna Vinschen wrote:
> > However: It's still the case that the user cannot bypass OS security
even
> > if he or she "escapes" from the jail, right?
> >
> > My goal is to restrict sftp browsing on the client side.
> >
> > Using ChrootDirectory with "ForceCommand internal-sftp" in sshd_config
> > seems to accomplish this.
> >
> > Is this not correct?
>
> It seems like it, but I wouldn't bet on it. The fact that /cygdrive and
> /dev directories are still visible inside the chroot jail speaks against
> that.
So to summarize: Even though the fake chroot doesn't increase security, it
doesn't reduce it, either.
In other words, even if the user "escapes" the jail, he or she can still
only do what the underlying OS permits.
Bill
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2019-03-13 15:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 22:31 Bill Stewart
2019-01-17 14:23 ` Corinna Vinschen
2019-01-17 23:04 ` Charles Russell
2019-03-12 22:21 ` Bill Stewart
2019-03-13 8:56 ` Corinna Vinschen
2019-03-13 15:12 ` Bill Stewart
2019-03-13 15:29 ` Corinna Vinschen
2019-03-13 15:58 ` Bill Stewart [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANV9t=RxeKVye=uJ9s=7ncp6jHbyMxAUsRGKa6zEc1VdkCfu+g@mail.gmail.com' \
--to=bstewart@iname.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).