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: Fri, 09 Nov 2007 12:07:31 -0500 [thread overview]
Message-ID: <473493D3.9030200@redhat.com> (raw)
In-Reply-To: <1194627412.3630.2.camel@vogon>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Stefan Schulze Frielinghaus wrote:
> On Thu, 2007-11-08 at 15:10 -0500, Daniel J Walsh wrote:
> [...]
>> 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?
>
> Yeah your right. There is a different. The AVCs are only generated when
> I log in as a staff_t. I created a test user logged in as user_t and no
> AVCs where generated.
>
> Hope you have more ideas because I run out of them ;-)
>
Well for now I would just ignore or dontaudit them. Since I believe
nothing used keyrings and the way it is setup in pam is all wrong right
now.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFHNJPSrlYvE4MpobMRAtwOAJ4lVduXNjmMGp+BD+/sO1b2H66GIgCg46rN
7b1lN9q9nynOZwCa6+4LUJI=
=mlVE
-----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.
prev parent reply other threads:[~2007-11-09 17:07 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
2007-11-09 16:56 ` Stefan Schulze Frielinghaus
2007-11-09 17:07 ` Daniel J Walsh [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=473493D3.9030200@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.