<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Fedora on Shaaf's blog</title><link>https://shaaf.dev/tags/fedora/</link><description>Recent content in Fedora on Shaaf's blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 18 Jan 2020 00:00:00 +0000</lastBuildDate><atom:link href="https://shaaf.dev/tags/fedora/index.xml" rel="self" type="application/rss+xml"/><item><title>Setup docker on Fedora 33</title><link>https://shaaf.dev/post/2020-01-18-setting-up-docker-fedora-33/</link><pubDate>Sat, 18 Jan 2020 00:00:00 +0000</pubDate><guid>https://shaaf.dev/post/2020-01-18-setting-up-docker-fedora-33/</guid><description>&lt;p>I use Fedora as my regular Linux. And I have been doing that for years now, even though I am a developer its simple and straight forward enough to get my way around. It has some great features and spins. You should check it out at &lt;a href="https://getfedora.org/">Fedora project&lt;/a>&lt;/p>
&lt;p>Here is a quick list of things that worked for me to setup docker on Fedora 33.
I followed the guidelines &lt;a href="https://docs.docker.com/engine/install/fedora/">here&lt;/a>.
Plus some more to config the firewall and user access.&lt;/p></description></item><item><title>Howto setup ssh with selinux and firewalld</title><link>https://shaaf.dev/post/2013-07-20-howto-change-ssh-with-selinux/</link><pubDate>Sat, 20 Jul 2013 14:40:47 +0200</pubDate><guid>https://shaaf.dev/post/2013-07-20-howto-change-ssh-with-selinux/</guid><description>&lt;p>While running fedora, if you want to change the port for your ssh, just changing the firewall rules will not make a difference.
If you are running selinux its important that you change the policy to allow a different port as well. I did learn it the hard way though, hopefully the following guide should be helpful.&lt;/p>
&lt;p>Lets start by an introduction to semanage.&lt;/p>
&lt;p>From man&lt;/p>
&lt;p>&lt;strong>Description&lt;/strong>&lt;/p>
&lt;p>semanage is used to configure certain elements of SELinux policy without requiring modification to or recompilation from policy sources. This includes the mapping from Linux usernames to SELinux user identities (which controls the initial security context assigned to Linux users when they login and bounds their authorized role set) as well as security context mappings for various kinds of objects, such as network ports, interfaces, and nodes (hosts) as well as the file context mapping. See the EXAMPLES section below for some examples of common usage. Note that the semanage login command deals with the mapping from Linux usernames (logins) to SELinux user identities, while the semanage user command deals with the mapping from SELinux user identities to authorized role sets. In most cases, only the former mapping needs to be adjusted by the administrator; the latter is principally defined by the base policy and usually does not require modification.&lt;/p></description></item><item><title>FedUp and Fedora 18</title><link>https://shaaf.dev/post/2013-04-19-fedup-and-fedora-18/</link><pubDate>Fri, 19 Apr 2013 07:07:22 +0200</pubDate><guid>https://shaaf.dev/post/2013-04-19-fedup-and-fedora-18/</guid><description>&lt;p>Just now I made the update from Fedora 17 to 18. I didnt know that fedora 18 has a new update util called fedUp.
If you are interested you could read here: &lt;a href="https://fedoraproject.org/wiki/FedUp">https://fedoraproject.org/wiki/FedUp&lt;/a>&lt;/p>
&lt;p>Just do the following&lt;/p>
&lt;pre>&lt;code>yum --enablerepo=updates-testing install fedup
&lt;/code>&lt;/pre>
&lt;p>And then&lt;/p>
&lt;pre>&lt;code>fedup --network 18
&lt;/code>&lt;/pre>
&lt;p>It should ask for a reboot after some downloads, and that should just do the trick. atleast it did for me.&lt;/p></description></item></channel></rss>