From: "Mark Müller" <trusted@web.de>
To: SELinux Mailing List <SELinux@tycho.nsa.gov>
Subject: Re: How to make sftp work?
Date: Sun, 28 Jul 2002 10:42:06 +0200 [thread overview]
Message-ID: <3D43AE5E.8020506@web.de> (raw)
In-Reply-To: 20020727164605.9240D265@lyta.coker.com.au
Russell Coker wrote:
> I suggest that the /usr/lib/ssh directory have type lib_t (which it has in
> the default policy file context files). sshd_t already has search and
> getattr access to lib_t directories.
I changed that due to another AVC denied message and placed sftp in
sshd_t through a domain transition. Now I switched back to lib_t again.
> It seems that the default domain for the root account on your system is
> user_t which does not have access to the root home directory. Not much you
> can do about this.
I can change with newrole, however this doesn't help me further as you
said before. sshd spawns bash/sftp not in the proper context concerning
my situation.
> I believe that ssh runs the user's shell and uses that for all further
> operations. The SE Linux policy for ssh is based around domain transitions
> when running the shell...
>
> I'm not sure why anyone wants sftp, between regular ftp, scp, and sendfile I
> think that all requirements are covered...
It is just for convenience. We got used to spawn the sftp-server
automatically from sshd and don't run ftp. I thought I could extend the
policy so that the sftp-server subsystem is placed in the proper domain
when started from sshd. Otherwise we will use ftp instead.
--
You have received this message because you are subscribed to the selinux list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2002-07-28 8:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-27 16:24 How to make sftp work? Mark Müller
2002-07-27 16:46 ` Russell Coker
2002-07-28 8:42 ` Mark Müller [this message]
2002-07-29 13:19 ` Stephen Smalley
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=3D43AE5E.8020506@web.de \
--to=trusted@web.de \
--cc=SELinux@tycho.nsa.gov \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.