All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: imsand@puzzle.ch
Cc: Daniel J Walsh <dwalsh@redhat.com>,
	Chad Sellers <csellers@tresys.com>,
	selinux@tycho.nsa.gov
Subject: Re: Context settings after ssh login
Date: Fri, 22 Oct 2010 23:28:27 -0700	[thread overview]
Message-ID: <4CC2808B.40200@gmail.com> (raw)
In-Reply-To: <35906.193.5.216.100.1287584724.squirrel@mail.puzzle.ch>

o.k. cleaned up this thread due to it becoming cluttered..

Right now I went and installed sles11.1 unto my machine, and got the 
policy up and running.(just have not defined any allow rules yet).

when using my iphone to sshd into the sles11.1 system Im going into the 
proper context that it should, as well as using another machine with 
SELinux on it.
If I sshd with sles11.1 into the other machine with SELinux I have the 
wrong login context, as well as using the iphone..
both give this:
iphone/sles11.1 sshd too------>other machine with SELinux gives:
id -Z
system_u:system_r:unconfined_t:s0-s0:c0.c1023

from what I remember I was doing vnc/sshd a few months ago with ipsec, 
and this was working..

abit late over here now, but what I can do is reload the system that I 
compressed and know works, to see if things are running properly, then 
see if I can narrow this down to a bisect or something.

as for sles11.1 itself the only real packages I needed to grab from the 
opensuse repos was git for the kernel, the rest is on the dvd..
(mixing sles11.1 and opensuse 11.1 breaks lots of things...)

Justin P. Mattock

--
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.

  parent reply	other threads:[~2010-10-25 12:46 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-04  8:03 Context settings after ssh login imsand
2010-10-04 17:13 ` Justin P. Mattock
2010-10-05  6:30   ` imsand
2010-10-05 13:29     ` Justin P. Mattock
2010-10-05 13:38       ` imsand
2010-10-05 14:29         ` Justin P. Mattock
2010-10-06  6:43           ` imsand
2010-10-06  7:06             ` Justin P. Mattock
2010-10-06  7:29               ` imsand
2010-10-06 13:50                 ` Justin P. Mattock
2010-10-06 13:50                   ` [refpolicy] " Justin P. Mattock
2010-10-07 14:40                 ` Chad Sellers
2010-10-07 16:11                   ` Daniel J Walsh
2010-10-07 17:24                     ` Justin P. Mattock
2010-10-19 14:42                       ` imsand
2010-10-19 14:55                         ` Justin P. Mattock
2010-10-19 15:47                           ` imsand
2010-10-19 16:38                             ` Justin P. Mattock
2010-10-20  8:42                               ` imsand
2010-10-20 12:27                                 ` Daniel J Walsh
2010-10-20 13:46                                 ` Justin P. Mattock
2010-10-20 14:25                                   ` imsand
2010-10-20 14:52                                     ` Justin P. Mattock
2010-10-21 12:09                                       ` imsand
2010-10-21 13:33                                         ` Justin P. Mattock
2010-10-24 23:43                                         ` Russell Coker
2010-10-23  6:28                                     ` Justin P. Mattock [this message]
2010-10-23 20:05                                     ` Justin P. Mattock
2010-10-25  7:09                                       ` imsand
2010-10-25  7:57                                         ` Justin P. Mattock
2010-10-25  8:22                                           ` Justin P. Mattock
2010-10-26  8:27                                             ` imsand
2010-10-26 14:26                                               ` Justin P. Mattock
2010-10-28 13:23                                               ` Justin P. Mattock

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=4CC2808B.40200@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=csellers@tresys.com \
    --cc=dwalsh@redhat.com \
    --cc=imsand@puzzle.ch \
    --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.