<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Selinux on It&#39;s a Binary World 2.0</title>
    <link>https://www.ericsbinaryworld.com/tags/selinux/</link>
    <description>Recent content in Selinux on It&#39;s a Binary World 2.0</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 11 Nov 2019 06:06:53 +0000</lastBuildDate>
    <atom:link href="https://www.ericsbinaryworld.com/tags/selinux/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Attempting a podman play on another VM</title>
      <link>https://www.ericsbinaryworld.com/2019/11/11/attempting-a-podman-play-on-another-vm/</link>
      <pubDate>Mon, 11 Nov 2019 06:06:53 +0000</pubDate>
      <guid>https://www.ericsbinaryworld.com/2019/11/11/attempting-a-podman-play-on-another-vm/</guid>
      <description> &lt;p&gt;The podman saga continues. The podman equivalent of a docker-compose.yml can be created from a pod with the following command:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;podman generate kube (name of pod) &amp;gt; (filename).yaml&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;So I did that with the pod that I&amp;rsquo;d created with an SELinux context. Now it was time to try it on another Fedora 31 VM to see if it would work. To be on the safe side, I started off creating the phpIPAM folder, chowning it to nobody and chmoding it to 777.&lt;/p&gt; <p><a href="https://www.ericsbinaryworld.com/2019/11/11/attempting-a-podman-play-on-another-vm/">Full post</a></p></description>
    </item>
    <item>
      <title>SELinux and Podman</title>
      <link>https://www.ericsbinaryworld.com/2019/11/10/selinux-and-podman/</link>
      <pubDate>Sun, 10 Nov 2019 05:18:15 +0000</pubDate>
      <guid>https://www.ericsbinaryworld.com/2019/11/10/selinux-and-podman/</guid>
      <description> &lt;p&gt;&lt;a href=&#34;https://www.ericsbinaryworld.com/2019/11/03/second-followup-to-podman-and-phpipam/&#34;&gt;Last time I messed around with Podman&lt;/a&gt;, I finally got things working and had what I think was a pretty good understanding of how to go forward. But in order to get things working, I&amp;rsquo;d had to turn off SELinux. Now it was time to see what I had to do to make Podman work with SELinux. I&amp;rsquo;ve got some ideas based on some Googling and might also need to try a program called udica to create the right contexts.&lt;/p&gt; <p><a href="https://www.ericsbinaryworld.com/2019/11/10/selinux-and-podman/">Full post</a></p></description>
    </item>
    <item>
      <title>Fedora Print Debugging Tip</title>
      <link>https://www.ericsbinaryworld.com/2015/08/18/fedora-print-debugging-tip/</link>
      <pubDate>Wed, 19 Aug 2015 01:38:01 +0000</pubDate>
      <guid>https://www.ericsbinaryworld.com/2015/08/18/fedora-print-debugging-tip/</guid>
      <description> &lt;p&gt;I was having trouble printing and couldn&amp;rsquo;t figure out what was going on. I tried everything, including reinstalling the printer and reinstalling the driver. I was getting a misleading &amp;ldquo;you are using the wrong driver&amp;rdquo; message. Turns out SELinux was to blame! I happened to check dmesg and see some audit messages. Then I did a&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;setenforce 0&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;to turn it off and printing worked. I tried some restorecons on some directories, but I don&amp;rsquo;t think that fixed it. What I think fixed it was going into the policycoreutils gui and checking as active the cups module &amp;ldquo;Allow cups execmem/execstack.&amp;rdquo; Obviously, I turned setenforce back on after checking the box.&lt;/p&gt; <p><a href="https://www.ericsbinaryworld.com/2015/08/18/fedora-print-debugging-tip/">Full post</a></p></description>
    </item>
  </channel>
</rss>
