All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: Stefan Schulze Frielinghaus <stefan@seekline.net>
Cc: selinux@tycho.nsa.gov
Subject: Re: type class key
Date: Thu, 08 Nov 2007 15:10:27 -0500	[thread overview]
Message-ID: <47336D33.4010606@redhat.com> (raw)
In-Reply-To: <1194529933.3293.7.camel@vogon>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stefan Schulze Frielinghaus wrote:
> Every time I log into my system via ssh an audit is generated:
> 
> audit(1194529539.754:7803673): avc:  denied  { link } for  pid=9526
> comm="sshd" scontext=system_u:system_r:sshd_t:s0-s0:c0.c1023
> tcontext=system_u:system_r:dovecot_t:s0 tclass=key
> 
> and after logout the following:
> 
> audit(1194529580.969:7803674): avc:  denied  { search } for  pid=9526
> comm="sshd" scontext=system_u:system_r:sshd_t:s0-s0:c0.c1023
> tcontext=system_u:system_r:dovecot_t:s0 tclass=key
> 
> Quite frankly I even do not know what a type class "key" is. Can someone
> explain to me what a type class "key" is? And maybe any suggestions why
> ssh tries to access dovecot's key (which is an imap server).
> 
> cheers,
> Stefan
> 
> PS: I'm running CentOS 5 with the latest updates and strict policy.
> 
> 
> --
> This message was distributed to subscribers of the selinux mailing 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.
key is the SELinux mapping of the kernel keyring.  No app currently uses
the kernel keyring, to the best of my knowledge.  And the pam
configurations up to now are setup incorrectly.

When any confined app runs it gets handed a keyring and does a search
access on the app that created the key ring.

The avc's you are reporting above are very strange.  They look like
dovecot created a keyring, probably though pam_keyinit.  And now sshd is
trying to access it.  I think you are running in permissive mode and
your context is messed up.

When you login are you getting user_t or staff_t?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFHM20yrlYvE4MpobMRAoY/AJ43FAim2WQEt1yrpHMsWMjKnpJoWQCfSemn
ihtmBI+3TyCb09sQIX+ssnU=
=/Ad8
-----END PGP SIGNATURE-----

--
This message was distributed to subscribers of the selinux mailing 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.

  reply	other threads:[~2007-11-08 20:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-08 13:52 type class key Stefan Schulze Frielinghaus
2007-11-08 20:10 ` Daniel J Walsh [this message]
2007-11-09 16:56   ` Stefan Schulze Frielinghaus
2007-11-09 17:07     ` Daniel J Walsh

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=47336D33.4010606@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=selinux@tycho.nsa.gov \
    --cc=stefan@seekline.net \
    /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.