Page 1 of 3 123 LastLast
Results 1 to 10 of 21

Thread: SELinux

  1. #1

    Default SELinux

    I am running v 11.1 x86. I am using this thread to install SELinux: SELinux - openSUSE. I get to the part where it says "file /etc/selinux/config should have the following content:". I open the file in nano, and there is no text whatsoever. So far as I know, I have done everything correct up to that point, but I am at a loss as what to do.

    I put the text in /etc/selinux/config that is supposed to be there, but that seems to make no difference.

    Any ideas?

  2. #2
    brassy NNTP User

    Default Re: SELinux

    > Any ideas?

    are you saying that after you put the content config (exactly as in
    the instructions), and rebooted to the GUI (i only assume that you are
    running KDE or Gnome) as a normal user...and, THEN logged into a
    terminal as root and run setstatus...then what came back to the
    terminal was not as expected (from the instructions on the cite page
    you gave)...is that what you mean by "that seems to make no difference."

    if that is true, then why not go ahead and copy paste exactly the
    output of setstatus back to this thread...

    --
    brassy

  3. #3

    Default Re: SELinux

    >"are you saying that after you put the content config (exactly as in
    >the instructions), and rebooted to the GUI (i only assume that you are
    >running KDE or Gnome) as a normal user...and, THEN logged into a
    >terminal as root and run setstatus..."

    Yes, I did all of that in the correct order as per the instructions.

    The odd thing here is what setstatus returns: "bash: setstatus: command not found"

  4. #4
    brassy NNTP User

    Default Re: SELinux

    > The odd thing here is what setstatus returns: "bash: setstatus: command
    > not found"


    the instructions say:

    "reboot the machine, login as root and run setstatus command, the
    output should be:"

    so you rebooted the machine and it automatically booted to KDE or
    Gnome (which?) right??

    then you opened a terminal, typed 'setstatus', pressed enter and it
    said "command not found" right?

    if so you only missed becoming root prior to issuing the command, so
    do this:

    Code:
    su -
    don't miss the one space following the u, and then the dash -

    it will then ask for your root password, type it in (you will not see
    what you type) press enter, and your command prompt will (depending on
    WHICH version of openSUSE you are using) turn red (meaning CAREFUL)
    and add this symbol #....NOW you are logged into the terminal as root,
    do this:

    Code:
    setstatus
    what is the output now? how does it compare to that in the instructions?

    if it remains 'command not found', do this:

    Code:
    which setstatus

    --
    brassy

  5. #5

    Default Re: SELinux

    >so you rebooted the machine and it automatically booted to KDE or
    >Gnome (which?) right??

    Yes, logged into GNOME.

    And I have been doing the 'su -' when typing 'setstatus.'

    'setstatus' remains unfound. 'which setstatus' returns: 'which: no setstatus in (/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/opt/kde3/bin:/usr/lib/jvm/jre/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin)'

  6. #6
    Join Date
    Jan 2009
    Location
    Somewhere in Fictionland
    Posts
    1,479

    Default Re: SELinux

    I was curious, so I followed the howto and got to the end.
    Setstatus:
    linux-pc3:~ # setstatus
    -bash: setstatus: command not found

    linux-pc3:~ # which setstatus
    which: no setstatus in (/sbin:/usr/sbin:/usr/local/sbin:/opt/kde3/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/opt/kde3/bin:/usr/lib/jvm/jre/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin)
    linux-pc3:~ #

    running KDE 3.5

    So yes, there is something missing.

  7. #7

    Default Re: SELinux

    I really don't know enough about it, but I am guessing that there must be something wrong with the packages that the howto calls for...

  8. #8
    Join Date
    Jan 2009
    Location
    Somewhere in Fictionland
    Posts
    1,479

    Default Re: SELinux

    Why do you think so? The only thing happened to me was a "vendor change" for two packages (since it is buildservice).

    I rather observed a permission problem. In the terminal the OS complained that a permission was wrongly set (if I recall 7500) and was substituted.

    A permission problem could be for me a candidate.
    The package source itself installed fine and did not miss any dependencies....

    But I am like you......just curious to try....but really quite clueless.

  9. #9

    Default Re: SELinux

    The only reason I would guess that a package was off would be because I didn't get any text at all when the howto told me to open /etc/selinux/config. In fact, when I opened it in nano, nano said that it was a new file when the howto said there would be text there.

    That in combination with my problem of setstatus not being a recognized command makes me wonder if there is a problem with a package.

    PURE speculation as I have almost NO idea how openSUSE does this sort of thing, 'under the hood' as it were.

    I guess the worst thing that would happen is not being able to config SELinux. Not really that big of a problem as I was just messing with it...^_^

  10. #10
    Join Date
    Jan 2009
    Location
    Somewhere in Fictionland
    Posts
    1,479

    Lightbulb Re: SELinux

    This seems to be a typo in the howto. Try:
    sestatus and NOT setstatus

    This gives me:
    linux-pc3:~ # sestatus
    SELinux status: disabled
    linux-pc3:~ # which sestatus
    /usr/sbin/sestatus

    Ok at least I know that it is still disabled. I guess your's too.
    Now we can find out why......

Page 1 of 3 123 LastLast

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •