FEED Validator

Congratulations!

This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

• line 22, column 0: Use of unknown namespace: com-wordpress:feed-additions:1 (11 occurrences) [help]

  <site xmlns="com-wordpress:feed-additions:1">58617187</site>	<item>
  

• line 57, column 0: content:encoded should not contain fetchpriority attribute [help]

• line 57, column 0: content:encoded should not contain decoding attribute (16 occurrences) [help]

• line 57, column 0: content:encoded should not contain sizes attribute (16 occurrences) [help]

• line 660, column 0: style attribute contains potentially dangerous content: padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap; (4 occurrences) [help]

• line 1111, column 0: content:encoded should not contain loading attribute (13 occurrences) [help]

Source: https://fedoramagazine.org/feed/

1. <?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
2. xmlns:content="http://purl.org/rss/1.0/modules/content/"
3. xmlns:wfw="http://wellformedweb.org/CommentAPI/"
4. xmlns:dc="http://purl.org/dc/elements/1.1/"
5. xmlns:atom="http://www.w3.org/2005/Atom"
6. xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
7. xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
8. >
9.  
10. <channel>
11. <title>Fedora Magazine</title>
12. <atom:link href="https://fedoramagazine.org/feed/" rel="self" type="application/rss+xml" />
13. <link>https://fedoramagazine.org/</link>
14. <description>Guides, information, and news about the Fedora operating system for users, developers, system administrators, and community members.</description>
15. <lastBuildDate>Tue, 23 Sep 2025 17:23:57 +0000</lastBuildDate>
16. <language>en-US</language>
17. <sy:updatePeriod>
18. hourly </sy:updatePeriod>
19. <sy:updateFrequency>
20. 1 </sy:updateFrequency>
21. <generator>https://wordpress.org/?v=6.8.2</generator>
22. <site xmlns="com-wordpress:feed-additions:1">58617187</site> <item>
23. <title>From Zero to Web Server: Building with Image mode for Fedora Linux &#038; Caddy</title>
24. <link>https://fedoramagazine.org/from-zero-to-web-server-building-with-image-mode-for-fedora-linux-caddy/</link>
25. <comments>https://fedoramagazine.org/from-zero-to-web-server-building-with-image-mode-for-fedora-linux-caddy/#respond</comments>
27. <dc:creator><![CDATA[Clément Verna]]></dc:creator>
28. <pubDate>Wed, 24 Sep 2025 08:00:00 +0000</pubDate>
29. <category><![CDATA[Fedora Project community]]></category>
30. <guid isPermaLink="false">https://fedoramagazine.org/?p=42570</guid>
31.  
32. <description><![CDATA[Image mode for Fedora Linux leverages bootable containers. This technology enables OCI containers to serve as a transport and delivery mechanism for operating system content. This article will guide you through how to use that technology to quickly create a Web Server using Caddy Introduction Bootable containers leverage existing OCI container tools (like Podman and [&#8230;]]]></description>
33. <content:encoded><![CDATA[
34. <p>Image mode for Fedora Linux leverages <a href="https://containers.github.io/bootable/" target="_blank" rel="noreferrer noopener">bootable containers</a>. This technology enables<a href="https://containers.github.io/bootable/" target="_blank" rel="noreferrer noopener"> OCI containers to serve as a transport and delivery mechanism for operating system content</a>. This article will guide you through how to use that technology to quickly create a Web Server using <a href="http://caddyserver.com" target="_blank" rel="noreferrer noopener">Caddy</a></p>
35.  
36.  
37.  
38. <span id="more-42570"></span>
39.  
40.  
41.  
42. <h2 class="wp-block-heading has-large-font-size">Introduction</h2>
43.  
44.  
45.  
46. <p>Bootable containers leverage existing OCI container tools (like Podman and Docker) and transport protocols for operating system management. This streamlines the configuration and distribution of operating systems through Containerfiles and container registries. The <a href="https://github.com/ublue-os" target="_blank" rel="noreferrer noopener">Universal Blue (ublue) community</a> has embraced this technology, offering diverse operating systems. They also provide a <a href="https://github.com/ublue-os/image-template" target="_blank" rel="noreferrer noopener">project template</a> to simplify the creation of custom operating systems.</p>
47.  
48.  
49.  
50. <h2 class="wp-block-heading has-large-font-size">Using the image-template repository</h2>
51.  
52.  
53.  
54. <p>We will begin by using the image-template GitHub repository to create our own repository. For this guide I have named it <em>fedora-web-server.</em><br /></p>
55.  
56.  
57.  
58. <figure class="wp-block-image size-large"><a href="https://fedoramagazine.org/wp-content/uploads/2025/09/image.png"><img fetchpriority="high" decoding="async" width="1024" height="115" src="https://fedoramagazine.org/wp-content/uploads/2025/09/image-1024x115.png" alt="" class="wp-image-42571" srcset="https://fedoramagazine.org/wp-content/uploads/2025/09/image-1024x115.png 1024w, https://fedoramagazine.org/wp-content/uploads/2025/09/image-300x34.png 300w, https://fedoramagazine.org/wp-content/uploads/2025/09/image-768x86.png 768w, https://fedoramagazine.org/wp-content/uploads/2025/09/image-1536x172.png 1536w, https://fedoramagazine.org/wp-content/uploads/2025/09/image-816x91.png 816w, https://fedoramagazine.org/wp-content/uploads/2025/09/image.png 1600w" sizes="(max-width: 1024px) 100vw, 1024px" /></a></figure>
59.  
60.  
61.  
62. <p>If you don&#8217;t have a GitHub account, you can simply clone the repository to your local machine and rename it to reflect your project&#8217;s name.</p>
63.  
64.  
65.  
66. <pre class="wp-block-preformatted">$ git clone git@github.com:&lt;username&gt;/fedora-web-server.git<br />$ cd fedora-web-server</pre>
67.  
68.  
69.  
70. <h2 class="wp-block-heading has-large-font-size">Using Fedora Bootc 42 as base image</h2>
71.  
72.  
73.  
74. <p>Image-template simplifies custom OS creation by providing a pre-built structure and essential files. To begin building our web server, we need to choose a base image. While image-template defaults to the ublue Bazzite image, we&#8217;ll switch to <em>quay.io/fedora/fedora-bootc:42</em>. Make this change by editing the Containerfile (see immediately below) and replacing the default <em>Base Image</em>.</p>
75.  
76.  
77.  
78. <pre class="wp-block-preformatted"># Allow build scripts to be referenced without being copied into the final image<br />FROM scratch AS ctx<br />COPY build_files /<br /><br /># Base Image<br />FROM quay.io/fedora/fedora-bootc:42<br /><br />RUN --mount=type=bind,from=ctx,source=/,target=/ctx \<br />   --mount=type=cache,dst=/var/cache \<br />   --mount=type=cache,dst=/var/log \<br />   --mount=type=tmpfs,dst=/tmp \<br />   /ctx/build.sh<br />  <br />### LINTING<br />## Verify final image and contents are correct.<br />RUN bootc container lint</pre>
79.  
80.  
81.  
82. <p><em>fedora-bootc</em> is a minimal image designed for customized installations. For this project, I&#8217;ll install <em>cloud-init</em> to facilitate deployment and testing both in the cloud and locally. I&#8217;ll modify the <em>build_files/build.sh</em> script, which is executed from within the <em>Containerfile</em>, to incorporate <em>cloud-init</em> into our customized OS.</p>
83.  
84.  
85.  
86. <p>The <em>build.sh </em>file will appear as follow:</p>
87.  
88.  
89.  
90. <pre class="wp-block-preformatted">#!/bin/bash<br /><br />set -ouex pipefail<br /><br />### Install packages<br />dnf5 install -y --setopt=install_weak_deps=0 cloud-init<br /></pre>
91.  
92.  
93.  
94. <p>Since I want to keep my OS minimal I am not installing weak dependencies.</p>
95.  
96.  
97.  
98. <h2 class="wp-block-heading has-large-font-size">Installing Caddy</h2>
99.  
100.  
101.  
102. <p>Caddy is an open-source, modern web server known for its simplicity, security, and automatic configuration—it &#8220;just works.&#8221; For our Fedora Bootc server, we&#8217;ll run Caddy using its container image, <em>docker.io/caddy</em>. We&#8217;ll leverage quadlet for seamless integration with systemd, allowing our Caddy container to operate like any other systemd service. Create the following file:</p>
103.  
104.  
105.  
106. <pre class="wp-block-preformatted">$ cd build_files
107. $ touch caddy.container</pre>
108.  
109.  
110.  
111. <p>and enter the following text into <em>caddy.contatiner</em> :</p>
112.  
113.  
114.  
115. <pre class="wp-block-preformatted">[Unit]
116. Description=Caddy Web Server
117. After=network-online.target
118.  
119. [Container]
120. Image=docker.io/caddy:2-alpine
121. PublishPort=80:80
122. PublishPort=443:443
123. Memory=512m
124. Volume=/var/caddy-data/:/data:Z
125. Volume=/var/caddy-config/:/config:Z
126. Volume=/var/log/caddy/:/var/log/caddy:Z
127. Volume=/etc/caddy:/etc/caddy:Z
128. Volume=/var/www/:/var/www:Z
129.  
130. [Service]
131. Restart=always
132.  
133. [Install]
134. # Start by default on boot
135. WantedBy=multi-user.target</pre>
136.  
137.  
138.  
139. <p>For those familiar with systemd services, the syntax and directives will be recognizable. The [Container] section declares the image to be used, the ports to be published, and the volumes to be shared between the host and the container.<br /><br />We can now modify the <em>build.sh</em> to copy that file in our custom OS, as shown here:</p>
140.  
141.  
142.  
143. <pre class="wp-block-preformatted">#!/bin/bash
144.  
145. set -ouex pipefail
146.  
147. ### Install packages
148. dnf5 install -y --setopt=install_weak_deps=0 cloud-init
149.  
150. # Copy caddy.container to /etc/containers/systemd/caddy.container
151. cp /ctx/caddy.container /etc/containers/systemd/caddy.container</pre>
152.  
153.  
154.  
155. <h2 class="wp-block-heading has-large-font-size">Configuring Caddy</h2>
156.  
157.  
158.  
159. <p>The final step to create a working Caddy server is to add the configuration file. Let’s create a Caddyfile: </p>
160.  
161.  
162.  
163. <pre class="wp-block-preformatted">$ touch Caddyfile</pre>
164.  
165.  
166.  
167. <p>and enter the text  shown below: </p>
168.  
169.  
170.  
171. <pre class="wp-block-preformatted"># Caddy configuration with automatic Let's Encrypt certificates<br /># Replace 'your-domain.com' with your actual domain name<br /><br /># For automatic HTTPS with Let's Encrypt, use your domain name instead of :80<br /># your-domain.com {<br />#    root * /var/www<br />#    file_server<br />#    log {<br />#        output file /var/log/caddy/access.log<br />#    }<br /># }<br /><br /># For local development (HTTP only)<br />:80 {<br />     root * /var/www<br />     file_server<br />     log {<br />         output file /var/log/caddy/access.log<br />     }<br />}</pre>
172.  
173.  
174.  
175. <p>We can now copy that file in our OS, by editing <em>build.sh</em></p>
176.  
177.  
178.  
179. <pre class="wp-block-preformatted">#!/bin/bash
180.  
181. set -ouex pipefail
182.  
183. ### Install packages
184. dnf5 install -y --setopt=install_weak_deps=0 cloud-init
185.  
186. # Copy caddy.container to /etc/containers/systemd/caddy.container
187. cp /ctx/caddy.container /etc/containers/systemd/caddy.container
188.  
189.  
190. # Create /etc/caddy directory and copy Caddyfile
191. mkdir -p /etc/caddy
192. cp /ctx/Caddyfile /etc/caddy/Caddyfile
193. </pre>
194.  
195.  
196.  
197. <p>To complete the setup, we&#8217;ll use systemd.tmpfiles to create Caddy&#8217;s necessary internal directories. This approach is essential because /var in bootable containers is mutable through overlayfs, meaning it&#8217;s only created at runtime and isn&#8217;t part of the container build process. Systemd.tmpfiles provides a straightforward solution to this limitation. Modify your <em>build.sh</em> file as follow:</p>
198.  
199.  
200.  
201. <pre class="wp-block-preformatted">#!/bin/bash
202. set -ouex pipefail
203.  
204. ### Install packages
205. dnf5 install -y --setopt=install_weak_deps=0 cloud-init
206.  
207. # Copy caddy.container to /etc/containers/systemd/caddy.container
208. cp /ctx/caddy.container /etc/containers/systemd/caddy.container
209.  
210. # Create /etc/caddy directory and copy Caddyfile
211. mkdir -p /etc/caddy
212. cp /ctx/Caddyfile /etc/caddy/Caddyfile
213.  
214. # Create tmpfiles.d configuration to set up /var directories at runtime
215. cat > /usr/lib/tmpfiles.d/caddy.conf << 'EOF'
216. # Create Caddy directories at runtime
217. d /var/log/caddy 0755 root root -
218. d /var/caddy-data 0755 root root -
219. d /var/caddy-config 0755 root root -
220. EOF
221. </pre>
222.  
223.  
224.  
225. <p>That’s it. We now have a <em>Containerfile</em> using fedora-bootc:42 as base image, a build script installing cloud-init and installing Caddy via quadlet and copying the Caddy configuration as well as setting up Caddy’s internal directories.</p>
226.  
227.  
228.  
229. <p>We can now build our custom operating system. The process involved a <em>Containerfile</em> based on fedora-bootc:42, a build script that installed cloud-init and Caddy (configured via quadlet), and the necessary Caddy configuration and directory setup.<br />If you want your Caddy web server to serve a custom html page, you can copy the following files <a href="https://github.com/cverna/fedora-web-server/tree/main/build_files/web" target="_blank" rel="noreferrer noopener">https://github.com/cverna/fedora-web-server/tree/main/build_files/web</a> and edit the build.sh script as follows:</p>
230.  
231.  
232.  
233. <pre class="wp-block-preformatted">#!/bin/bash
234.  
235. set -ouex pipefail
236.  
237. ### Install packages
238. dnf5 install -y --setopt=install_weak_deps=0 cloud-init
239.  
240. # Copy caddy.container to /etc/containers/systemd/caddy.container
241. cp /ctx/caddy.container /etc/containers/systemd/caddy.container
242.  
243. # Create /etc/caddy directory and copy Caddyfile
244. mkdir -p /etc/caddy
245. cp /ctx/Caddyfile /etc/caddy/Caddyfile
246.  
247. # Copy web content to /usr/share for the base image
248. mkdir -p /usr/share/caddy/web
249. cp -r /ctx/web/* /usr/share/caddy/web/
250.  
251. # Create tmpfiles.d configuration to set up /var directories at runtime
252. cat > /usr/lib/tmpfiles.d/caddy.conf << 'EOF'
253. # Create Caddy directories at runtime
254. d /var/log/caddy 0755 root root -
255. d /var/caddy-data 0755 root root -
256. d /var/caddy-config 0755 root root -
257.  
258. # Copy web content from /usr/share to /var at runtime
259. d /var/www 0755 root root -
260. C /var/www/index.html 0644 root root - /usr/share/caddy/web/index.html
261. C /var/www/fedora-logo.png 0644 root root - /usr/share/caddy/web/fedora-logo.png
262. C /var/www/caddy-logo.svg 0644 root root - /usr/share/caddy/web/caddy-logo.svg
263. EOF</pre>
264.  
265.  
266.  
267. <h2 class="wp-block-heading has-large-font-size">Building the bootable container</h2>
268.  
269.  
270.  
271. <p>The image-template repositories equip you with the necessary tools for local image construction. Let&#8217;s begin by verifying that all dependencies are in place.</p>
272.  
273.  
274.  
275. <pre class="wp-block-preformatted">$ sudo dnf install just git jq podman</pre>
276.  
277.  
278.  
279. <p>Then we can run <em>just</em> to build the container. The following shows the just command and subsequent output:</p>
280.  
281.  
282.  
283. <pre class="wp-block-preformatted">$ just build fedora-web-server latest
284. [1/2] STEP 1/2: FROM scratch AS ctx
285. [1/2] STEP 2/2: COPY build_files /
286. --> Using cache 94ec17d1689b09a362814ab08530966be4aced972050fedcd582b65f174af3a3
287. --> 94ec17d1689b
288. [2/2] STEP 1/3: FROM quay.io/fedora/fedora-bootc:42
289. [2/2] STEP 2/3: RUN --mount=type=bind,from=ctx,source=/,target=/ctx     --mount=type=cache,dst=/var/cache     --mount=type=cache,dst=/var/log     --mount=type=tmpfs,dst=/tmp     /ctx/build.sh &&     ostree container commit
290. --> Using cache 8cac20d690bda884b91ae2a555c4239a71f162fbd4ff36a1e2ed5f35f5dfb05a
291. --> 8cac20d690bd
292. [2/2] STEP 3/3: RUN bootc container lint
293. --> Using cache 5cb978e3db5a2bcd437018a6e97e1029d694180002f5fa098aaf540952941dd4
294. [2/2] COMMIT fedora-web-server:latest
295. --> 5cb978e3db5a
296. Successfully tagged localhost/fedora-web-server:latest
297. </pre>
298.  
299.  
300.  
301. <p><a href="https://github.com/casey/just" target="_blank" rel="noreferrer noopener">Just</a> is a useful tool for running project-specific commands, similar to Makefiles, and uses a &#8216;justfile&#8217;.&nbsp;As the image functions like any other container image, we can inspect it using Podman.</p>
302.  
303.  
304.  
305. <pre class="wp-block-preformatted">$ podman images
306. REPOSITORY                   TAG         IMAGE ID      CREATED      SIZE
307. localhost/fedora-web-server  latest      5cb978e3db5a  4 hours ago  1.95 GB
308. quay.io/fedora/fedora-bootc  42          586b146c456e  2 days ago   1.88 GB
309. </pre>
310.  
311.  
312.  
313. <h2 class="wp-block-heading has-large-font-size">Building a Disk Image</h2>
314.  
315.  
316.  
317. <p>The disk image for our server is built using <em>just</em> as follows:</p>
318.  
319.  
320.  
321. <pre class="wp-block-preformatted">$ just build-vm localhost/fedora-web-server latest
322. </pre>
323.  
324.  
325.  
326. <p>This will use the <a href="https://github.com/osbuild/bootc-image-builder" target="_blank" rel="noreferrer noopener">bootc-image-builder</a> project to build a disk image of our bootable container. Once the command has finished, we have a qcow2 image in the output directory</p>
327.  
328.  
329.  
330. <pre class="wp-block-preformatted">$ ls output/qcow2                                                                                                                                                              
331. disk.qcow2</pre>
332.  
333.  
334.  
335. <p>We can now use that qcow2 image to start a Virtual Machine and run our webserver.</p>
336.  
337.  
338.  
339. <h2 class="wp-block-heading has-large-font-size">Running the Web Server</h2>
340.  
341.  
342.  
343. <p>To run the server we can use any virtualization software. In this case I am using virt-install:</p>
344.  
345.  
346.  
347. <pre class="wp-block-preformatted">$ sudo dnf install virt-install libvirt
348. $ virt-install --cloud-init root-ssh-key=/path/to/ssh/public.key --connect qemu:///system --import --name fedora-web-server --memory 2048 --disk output/qcow2/disk.qcow2 --os-variant fedora41
349. Starting install...
350. Creating domain...
351. ...
352. Fedora Linux 42 (Adams)
353. Kernel 6.16.5-200.fc42.x86_64 on x86_64 (ttyS0)
354.  
355. enp1s0: 192.168.100.199
356. fedora login:</pre>
357.  
358.  
359.  
360. <p>Once the virtual machine is up and running, you can use ssh to login as root, using the local IP address of the virtual machine.</p>
361.  
362.  
363.  
364. <pre class="wp-block-preformatted">$ ssh root@192.168.100.199
365. $ bootc status                                                                                                                                                    
366. ● Booted image: localhost/fedora-web-server:latest                                                                                                                              
367.       Digest: sha256:a813a8da85f48d8e6609289dde87e1d45ff70a713d1a9ec3e4e667d01cb470f2 (amd64)                                                                                  
368.      Version: 42.20250911.0 (2025-09-12T07:36:05Z) </pre>
369.  
370.  
371.  
372. <p>Currently, the server&#8217;s update capability is limited because the images point to the localhost/fedora-web-server:latest container image. This can be resolved by building and pushing these container images to a container registry such as <a href="http://quay.io" target="_blank" rel="noreferrer noopener">quay.io</a> or<a href="http://ghcr.io" target="_blank" rel="noreferrer noopener"> ghcr.io</a>. Detailed instructions for these steps are available in the README file of the<a href="https://github.com/ublue-os/image-template?tab=readme-ov-file#step-2-initial-setup" target="_blank" rel="noreferrer noopener"> ublue-os/image-template repository</a>.</p>
373.  
374.  
375.  
376. <p>To verify that the web server is running successfully, access that same ip address from your web browser and you should get the following web page.</p>
377.  
378.  
379.  
380. <figure class="wp-block-image size-large"><a href="https://fedoramagazine.org/wp-content/uploads/2025/09/image-1.png"><img decoding="async" width="1024" height="698" src="https://fedoramagazine.org/wp-content/uploads/2025/09/image-1-1024x698.png" alt="" class="wp-image-42572" srcset="https://fedoramagazine.org/wp-content/uploads/2025/09/image-1-1024x698.png 1024w, https://fedoramagazine.org/wp-content/uploads/2025/09/image-1-300x204.png 300w, https://fedoramagazine.org/wp-content/uploads/2025/09/image-1-768x523.png 768w, https://fedoramagazine.org/wp-content/uploads/2025/09/image-1-816x556.png 816w, https://fedoramagazine.org/wp-content/uploads/2025/09/image-1.png 1476w" sizes="(max-width: 1024px) 100vw, 1024px" /></a></figure>
381.  
382.  
383.  
384. <h2 class="wp-block-heading">Summary</h2>
385.  
386.  
387.  
388. <p>This guide demonstrates the power of image mode for Fedora Linux using bootc and Caddy to build a lightweight, custom web server. By leveraging container technologies for OS delivery and Caddy for simplified web serving, users can efficiently deploy and manage web applications, setting a strong foundation for future customization. Make sure to check the library of <a href="https://gitlab.com/fedora/bootc/examples/" target="_blank" rel="noreferrer noopener">examples</a> to get ideas on how to use bootc.</p>
389.  
390.  
391.  
392. <p></p>
393. ]]></content:encoded>
395. <wfw:commentRss>https://fedoramagazine.org/from-zero-to-web-server-building-with-image-mode-for-fedora-linux-caddy/feed/</wfw:commentRss>
396. <slash:comments>0</slash:comments>
399. <post-id xmlns="com-wordpress:feed-additions:1">42570</post-id><enclosure url="https://fedoramagazine.org/wp-content/uploads/2025/09/Image_mode_n_Caddy-300x127.jpg" length="21621" type="image/jpg" /> </item>
400. <item>
401. <title>How to rebase to Fedora Silverblue 43 Beta</title>
402. <link>https://fedoramagazine.org/how-to-rebase-to-fedora-silverblue-43-beta/</link>
403. <comments>https://fedoramagazine.org/how-to-rebase-to-fedora-silverblue-43-beta/#comments</comments>
405. <dc:creator><![CDATA[Michal Konečný]]></dc:creator>
406. <pubDate>Mon, 22 Sep 2025 08:00:00 +0000</pubDate>
407. <category><![CDATA[Fedora Project community]]></category>
408. <guid isPermaLink="false">https://fedoramagazine.org/?p=42605</guid>
409.  
410. <description><![CDATA[Silverblue is an operating system for your desktop built on Fedora Linux. It’s excellent for daily use, development, and container-based workflows. It offers numerous advantages such as being able to roll back in case of any problems. This article provides the steps to rebase to the newly released Fedora Linux 43 Beta, and how to revert if anything unforeseen [&#8230;]]]></description>
411. <content:encoded><![CDATA[
412. <p><a href="https://docs.fedoraproject.org/en-US/fedora-silverblue/" target="_blank" rel="noreferrer noopener">Silverblue</a> is an operating system for your desktop built on Fedora Linux. It’s excellent for daily use, development, and container-based workflows. It offers <a href="https://fedoramagazine.org/give-fedora-silverblue-a-test-drive/" target="_blank" rel="noreferrer noopener">numerous advantages</a> such as being able to roll back in case of any problems. This article provides the steps to rebase to the newly released Fedora Linux 43 Beta, and how to revert if anything unforeseen happens.</p>
413.  
414.  
415.  
416. <span id="more-42605"></span>
417.  
418.  
419.  
420. <p>NOTE: Before attempting an upgrade to the Fedora Linux 43 Beta, apply any pending upgrades.</p>
421.  
422.  
423.  
424. <h2 class="wp-block-heading">Updating using the terminal</h2>
425.  
426.  
427.  
428. <p>Because Fedora LInux 43 Beta is not available in GNOME Software, the whole process must be done through a terminal.</p>
429.  
430.  
431.  
432. <p>First, check if the 43 branch is available, which should be true now:</p>
433.  
434.  
435.  
436. <pre class="wp-block-preformatted">$ ostree remote refs fedora</pre>
437.  
438.  
439.  
440. <p>You should see the following line in the output:</p>
441.  
442.  
443.  
444. <pre class="wp-block-preformatted">fedora:fedora/43/x86_64/silverblue</pre>
445.  
446.  
447.  
448. <p>If you want to pin the current deployment (this deployment will stay as an option in GRUB until you remove it), you can do it by running:</p>
449.  
450.  
451.  
452. <pre class="wp-block-preformatted"># 0 is entry position in rpm-ostree status<br />$ sudo ostree admin pin 0</pre>
453.  
454.  
455.  
456. <p>To remove the pinned deployment use following command ( &#8220;2&#8221; corresponds to the entry position in the output from&nbsp;<kbd>rpm-ostree status</kbd>&nbsp;):</p>
457.  
458.  
459.  
460. <pre class="wp-block-preformatted">$ sudo ostree admin pin --unpin 2</pre>
461.  
462.  
463.  
464. <p>Next, rebase your system to the Fedora 43 branch.</p>
465.  
466.  
467.  
468. <pre class="wp-block-preformatted">$ rpm-ostree rebase fedora:fedora/43/x86_64/silverblue</pre>
469.  
470.  
471.  
472. <p>Finally, the last thing to do is restart your computer and boot to Fedora Silverblue 43 Beta.</p>
473.  
474.  
475.  
476. <h2 class="wp-block-heading">How to revert</h2>
477.  
478.  
479.  
480. <p>If anything bad happens — for instance, if you can’t boot to Fedora Silverblue 43 Beta at all — it’s easy to go back. Pick the previous entry in the GRUB boot menu (you need to press ESC during boot sequence to see the GRUB menu in newer versions of Fedora Silverblue), and your system will start in its previous state. To make this change permanent, use the following command:</p>
481.  
482.  
483.  
484. <pre class="wp-block-preformatted">$ rpm-ostree rollback</pre>
485.  
486.  
487.  
488. <p>That’s it. Now you know how to rebase to Fedora Silverblue 43 Beta and fall back. So why not do it today?</p>
489.  
490.  
491.  
492. <h2 class="wp-block-heading">Known issues</h2>
493.  
494.  
495.  
496. <ul class="wp-block-list">
497. <li><a href="https://discussion.fedoraproject.org/t/pam-lastlog-change-crashing-gdm/164467" target="_blank" rel="noreferrer noopener">PAM Lastlog change crashing gdm</a></li>
498. </ul>
499.  
500.  
501.  
502. <h2 class="wp-block-heading">FAQ</h2>
503.  
504.  
505.  
506. <p>Because there are similar questions in comments for each blog about rebasing to newer version of Silverblue I will try to answer them in this section.</p>
507.  
508.  
509.  
510. <p><strong>Question: Can I skip versions during rebase of Fedora Linux? For example from Fedora Silverblue 41 to Fedora Silverblue 43?</strong></p>
511.  
512.  
513.  
514. <p>Answer: Although it could be sometimes possible to skip versions during rebase, it is not recommended. You should always update to one version above (41-&gt;42 for example) to avoid unnecessary errors.</p>
515.  
516.  
517.  
518. <p><strong>Question: I have&nbsp;<a href="https://rpmfusion.org/" target="_blank" rel="noreferrer noopener">rpm-fusion</a>&nbsp;layered and I got errors during rebase. How should I do the rebase?</strong></p>
519.  
520.  
521.  
522. <p>Answer: If you have&nbsp;<a href="https://rpmfusion.org/" target="_blank" rel="noreferrer noopener">rpm-fusion</a>&nbsp;layered on your Silverblue installation, you should do the following before rebase:</p>
523.  
524.  
525.  
526. <pre class="wp-block-preformatted">rpm-ostree update --uninstall rpmfusion-free-release --uninstall rpmfusion-nonfree-release --install rpmfusion-free-release --install rpmfusion-nonfree-release</pre>
527.  
528.  
529.  
530. <p>After doing this you can follow the guide in this article.</p>
531.  
532.  
533.  
534. <p><strong>Question: Could this guide be used for other ostree editions (Fedora Atomic Desktops) as well like Kinoite, Sericea (Sway Atomic), Onyx (Budgie Atomic),…?</strong></p>
535.  
536.  
537.  
538. <p>Yes, you can follow the <em>Updating using the terminal</em> part of this guide for every ostree edition of Fedora. Just use the corresponding branch. For example for Kinoite use <kbd>fedora:fedora/43/x86_64/kinoite</kbd></p>
539.  
540.  
541.  
542. <p></p>
543. ]]></content:encoded>
545. <wfw:commentRss>https://fedoramagazine.org/how-to-rebase-to-fedora-silverblue-43-beta/feed/</wfw:commentRss>
546. <slash:comments>9</slash:comments>
549. <post-id xmlns="com-wordpress:feed-additions:1">42605</post-id><enclosure url="https://fedoramagazine.org/wp-content/uploads/2025/09/silverblue-F43-Beta-rebase-300x127.jpg" length="8501" type="image/jpg" /> </item>
550. <item>
551. <title>Integrating a uTrust FIDO2 Security Key for Full Disk Encryption, Login, and Sudo Access on Fedora 42</title>
552. <link>https://fedoramagazine.org/integrating-utrust-fido2-security-key-for-disk-encryption-login-and-sudo-access-for-fedora-42/</link>
553. <comments>https://fedoramagazine.org/integrating-utrust-fido2-security-key-for-disk-encryption-login-and-sudo-access-for-fedora-42/#comments</comments>
555. <dc:creator><![CDATA[Joe Murphy]]></dc:creator>
556. <pubDate>Fri, 19 Sep 2025 08:00:00 +0000</pubDate>
557. <category><![CDATA[Fedora Project community]]></category>
558. <guid isPermaLink="false">https://fedoramagazine.org/?p=42404</guid>
559.  
560. <description><![CDATA[This guide provides a step-by-step walk-through for integrating a uTrust FIDO2 security key (Identiv uTrust) with Fedora 42 to secure: Audience for this article The guide is intended for instructional cybersecurity labs and intermediate Fedora users. It prioritizes PIN + Touch verification for strong security. NOTE: Since misconfiguration can result in system lockout, readers should [&#8230;]]]></description>
561. <content:encoded><![CDATA[
562. <p>This guide provides a step-by-step walk-through for integrating a uTrust FIDO2 security key (Identiv uTrust) with Fedora 42 to secure:</p>
563.  
564.  
565.  
566. <ul class="wp-block-list">
567. <li>LUKS2 full disk encryption (FDE)</li>
568.  
569.  
570.  
571. <li>Graphical login (LightDM + Cinnamon)</li>
572.  
573.  
574.  
575. <li>Sudo elevation</li>
576. </ul>
577.  
578.  
579.  
580. <span id="more-42404"></span>
581.  
582.  
583.  
584. <h2 class="wp-block-heading">Audience for this article</h2>
585.  
586.  
587.  
588. <p>The guide is intended for instructional cybersecurity labs and intermediate Fedora users. It prioritizes <strong>PIN + Touch</strong> verification for strong security. </p>
589.  
590.  
591.  
592. <p>NOTE: Since misconfiguration can result in system lockout,  readers should work only on non-production systems, maintain a fallback password, and back up all critical data before making changes.</p>
593.  
594.  
595.  
596. <h2 class="wp-block-heading">Background</h2>
597.  
598.  
599.  
600. <p>The following technology is used in this walk-through:</p>
601.  
602.  
603.  
604. <p><strong>FIDO2</strong> (Fast Identity Online 2) is a standard for passwordless or multi-factor authentication using hardware tokens. It relies on public key cryptography and supports PIN or biometric verification. In this setup, FIDO2 provides secure, hardware-backed authentication using a PIN and a required physical touch on the key.</p>
605.  
606.  
607.  
608. <p><strong>LUKS2</strong> (Linux Unified Key Setup 2) is the full-disk encryption format used in modern Linux systems.</p>
609.  
610.  
611.  
612. <p><strong>PAM</strong> (Pluggable Authentication Modules) and <strong>Polkit </strong>(PolicyKit) control authentication for logins and privilege escalation across both GUI and CLI actions.</p>
613.  
614.  
615.  
616. <p>This guide combines these technologies to deliver end-to-end security — from full-disk decryption at boot, to graphical login, to administrative elevation with sudo.</p>
617.  
618.  
619.  
620. <h2 class="wp-block-heading">System Overview</h2>
621.  
622.  
623.  
624. <p>The following hardware/software is used in this implementation:</p>
625.  
626.  
627.  
628. <p><strong>Hardware and Software:</strong></p>
629.  
630.  
631.  
632. <ul class="wp-block-list">
633. <li><strong>Architecture:</strong> x86_64</li>
634.  
635.  
636.  
637. <li><strong>CPU:</strong> Intel Core i7</li>
638.  
639.  
640.  
641. <li><strong>Kernel:</strong> 6.14.9-300.fc42.x86_64</li>
642.  
643.  
644.  
645. <li><strong>Fedora Version:</strong> Fedora 42 (Adams)</li>
646.  
647.  
648.  
649. <li><strong>Desktop Environment:</strong> Cinnamon with LightDM</li>
650. </ul>
651.  
652.  
653.  
654. <p><strong>FIDO2 Key:</strong> Identiv uTrust FIDO2</p>
655.  
656.  
657.  
658. <ul class="wp-block-list">
659. <li>Vendor/Product:
660.  
661. <div class="codecolorer-container text default" style="overflow:auto;white-space:nowrap;border:1px solid #9F9F9F;width:435px;"><div class="text codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap;">0x04e6:0x5a11</div></div>
662.  
663. </li>
664.  
665.  
666.  
667. <li>Protocol: CTAP2 / FIDO_2_0</li>
668.  
669.  
670.  
671. <li>PIN: Required</li>
672.  
673.  
674.  
675. <li>User Presence: Touch required</li>
676.  
677.  
678.  
679. <li>User Verification: PIN only (no biometrics)</li>
680.  
681.  
682.  
683. <li>Device Path:
684.  
685. <div class="codecolorer-container text default" style="overflow:auto;white-space:nowrap;border:1px solid #9F9F9F;width:435px;"><div class="text codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap;">/dev/hidraw0</div></div>
686.  
687. </li>
688. </ul>
689.  
690.  
691.  
692. <p><strong>Disk Setup</strong></p>
693.  
694.  
695.  
696. <ul class="wp-block-list">
697. <li>Btrfs on LUKS2 FDE (
698.  
699. <div class="codecolorer-container text default" style="overflow:auto;white-space:nowrap;border:1px solid #9F9F9F;width:435px;"><div class="text codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap;">/dev/sda3</div></div>
700.  
701. )</li>
702.  
703.  
704.  
705. <li>LUKS UUID:
706.  
707. <div class="codecolorer-container text default" style="overflow:auto;white-space:nowrap;border:1px solid #9F9F9F;width:435px;"><div class="text codecolorer" style="padding:5px;font:normal 12px/1.4em Monaco, Lucida Console, monospace;white-space:nowrap;">8b2f0322-f508-4bed-8b1e-8f05cc784d60</div></div>
708.  
709. <em>(this will differ on each machine)</em></li>
710.  
711.  
712.  
713. <li>Keyslots:</li>
714.  
715.  
716.  
717. <li>0: Passphrase (argon2id)</li>
718.  
719.  
720.  
721. <li>1: FIDO2 credential <em>(note: in testing, only one FIDO2 key could be used at a time)</em></li>
722. </ul>
723.  
724.  
725.  
726. <hr class="wp-block-separator has-alpha-channel-opacity"/>
727.  
728.  
729.  
730. <h2 class="wp-block-heading">Process Flow Overview</h2>
731.  
732.  
733.  
734. <p>The following phases occur during implementation:</p>
735.  
736.  
737.  
738. <ol start="1" class="wp-block-list">
739. <li><strong>System preparation</strong> — Install Fedora 42 with LUKS2 full-disk encryption and update packages.</li>
740.  
741.  
742.  
743. <li><strong>Package installation</strong> — Add the development, PAM, and FIDO2 tools required for integration.</li>
744.  
745.  
746.  
747. <li><strong>FIDO2 key enrollment</strong> — Register the key with LUKS2 for disk unlock.</li>
748.  
749.  
750.  
751. <li><strong>PAM configuration</strong> — Enable FIDO2 authentication for login and sudo.</li>
752.  
753.  
754.  
755. <li><strong>Polkit configuration (optional)</strong> — Extend FIDO2 support to graphical privilege prompts.</li>
756.  
757.  
758.  
759. <li><strong>Testing and verification</strong> — Confirm PIN + Touch authentication at boot, login, and sudo elevation.</li>
760. </ol>
761.  
762.  
763.  
764. <h2 class="wp-block-heading">Implementation Guide</h2>
765.  
766.  
767.  
768. <h3 class="wp-block-heading">Phase 1: System Preparation</h3>
769.  
770.  
771.  
772. <ol start="1" class="wp-block-list">
773. <li>Create a clean install of Fedora 42 with Cinnamon + LightDM</li>
774.  
775.  
776.  
777. <li>During installation/partitioning configure the following:
778. <ul class="wp-block-list">
779. <li>LUKS2 Full Disk Encryption (Btrfs or ext4)</li>
780.  
781.  
782.  
783. <li>No separate /home</li>
784.  
785.  
786.  
787. <li>No auto-login</li>
788.  
789.  
790.  
791. <li>Create an admin user</li>
792. </ul>
793. </li>
794.  
795.  
796.  
797. <li>Update the system: <br /><kbd>sudo dnf upgrade --refresh -y</kbd></li>
798. </ol>
799.  
800.  
801.  
802. <h3 class="wp-block-heading">Phase 2: Required Package Installation</h3>
803.  
804.  
805.  
806. <p>Install required development and security packages:</p>
807.  
808.  
809.  
810. <p><kbd>sudo dnf install -y <br />  gcc make cmake git autoconf automake libtool <br />  pam-devel systemd-devel glibc-devel openssl-devel <br />  libfido2 libfido2-devel fido2-tools u2f-host pam-u2f <br />  pcsc-lite pcsc-lite-ccid pcsc-tools ccid opensc <br />  authselect cryptsetup pam_passwdqc fprintd-pam gnome-keyring-pam</kbd></p>
811.  
812.  
813.  
814. <p>Enable and start the PC/SC daemon for smartcard support:</p>
815.  
816.  
817.  
818. <p><kbd>sudo systemctl enable --now pcscd</kbd></p>
819.  
820.  
821.  
822. <h3 class="wp-block-heading">Phase 3: FIDO2 Key Setup</h3>
823.  
824.  
825.  
826. <ol start="1" class="wp-block-list">
827. <li>Insert the FIDO2 key and verify it is detected: <br /><kbd>lsusb</kbd><br /><kbd>fido2-token -L</kbd><br /><kbd>fido2-token -I /dev/hidraw0</kbd><br />Expected output is:<br /><kbd>Identiv uTrust FIDO2 (0x04e6:0x5a11) with options rk, clientPin.</kbd><br /></li>
828.  
829.  
830.  
831. <li>Troubleshooting considerations if the key isn&#8217;t recognized:
832. <ul class="wp-block-list">
833. <li>Ensure <kbd>/dev/hidraw0 </kbd>exists</li>
834.  
835.  
836.  
837. <li>Run the following to load kernel modules: <br /><kbd>sudo modprobe hid </kbd><br /><kbd>sudo modprobe hid_generic</kbd></li>
838.  
839.  
840.  
841. <li>Replug the key<br /></li>
842. </ul>
843. </li>
844.  
845.  
846.  
847. <li>If FIDO_ERR_INTERNAL (-9) occurs:
848. <ul class="wp-block-list">
849. <li>Create the plugdev group:<br /><kbd>sudo groupadd plugdev</kbd><br /><kbd>sudo usermod -aG plugdev $USER </kbd></li>
850.  
851.  
852.  
853. <li>Apply a udev rule: <br /><kbd>echo 'KERNEL=="hidraw*", ATTRS{idVendor}=="04e6", ATTRS{idProduct}=="5a11", TAG+="uaccess", GROUP="plugdev"' |  sudo tee /etc/udev/rules.d/70-u2f.rules sudo udevadm control --reload-rules &amp;&amp; sudo udevadm trigger </kbd></li>
854.  
855.  
856.  
857. <li>Reboot: <br /><kbd>sudo reboot</kbd><br /></li>
858. </ul>
859. </li>
860.  
861.  
862.  
863. <li>Enroll the FIDO key for LUKS2: <br /><kbd>sudo systemd-cryptenroll --fido2-device=/dev/hidraw0 --fido2-with-client-pin=yes /dev/sda3 </kbd><br /></li>
864.  
865.  
866.  
867. <li>Validate enrollment:<br /><kbd>sudo cryptsetup luksDump /dev/sda3</kbd><br /></li>
868.  
869.  
870.  
871. <li>Update <kbd>/etc/crypttab</kbd>:<br /><kbd>sudo nano /etc/crypttab</kbd><br />Add or modify:<br /><kbd>luks-... UUID UUID=... none fido2-device=auto fido2-with-client-pin=yes discard</kbd></li>
872. </ol>
873.  
874.  
875.  
876. <h3 class="wp-block-heading">Phase 4: PAM Configuration</h3>
877.  
878.  
879.  
880. <ol start="1" class="wp-block-list">
881. <li>Fedora’s pam-u2f package lacks pamu2fcfg. Build pamu2fcfg from source:
882. <ul class="wp-block-list">
883. <li>git clone https://github.com/Yubico/pam-u2f</li>
884.  
885.  
886.  
887. <li>cd pam-u2f</li>
888.  
889.  
890.  
891. <li>mkdir build &amp;&amp; cd build</li>
892.  
893.  
894.  
895. <li>cmake -DBUILD_MANPAGES=OFF ..</li>
896.  
897.  
898.  
899. <li>make</li>
900.  
901.  
902.  
903. <li>sudo cp ./pamu2fcfg/pamu2fcfg /usr/local/bin/</li>
904.  
905.  
906.  
907. <li>sudo chmod +x /usr/local/bin/pamu2fcfg<br /><br /></li>
908. </ul>
909. </li>
910.  
911.  
912.  
913. <li>Generate U2F mapping: <br /><kbd>pamu2fcfg -n -u $(whoami) -o pam://fedora | sudo tee /etc/u2f_mappings</kbd><br />Verify output includes +presence+pin (e.g., <kbd>yourusername:3aaOH5…Base64…,M9hAf2…==,es256,+presence+pin)</kbd><br /></li>
914.  
915.  
916.  
917. <li>Set permissions:<br /><kbd>sudo chmod 600 /etc/u2f_mappings <br />sudo chown root:root /etc/u2f_mappings</kbd><br /></li>
918.  
919.  
920.  
921. <li>Backup PAM files: <br /><kbd>mkdir -p ~/fido2-audit/pam </kbd><br /><kbd>sudo cp /etc/pam.d/{sudo,lightdm,cinnamon-screensaver,system-auth,password-auth,polkit-1} ~/fido2-audit/pam/ </kbd><br /></li>
922.  
923.  
924.  
925. <li>Update PAM files to include FIDO2 authentication. On this system, the working configuration is:
926. <ul class="wp-block-list">
927. <li>/etc/pam.d/sudo
928. <ul class="wp-block-list">
929. <li>auth sufficient pam_u2f.so authfile=/etc/u2f_mappings cue pinverification=always origin=pam://fedora appid=pam://fedora</li>
930.  
931.  
932.  
933. <li>auth required pam_unix.so</li>
934.  
935.  
936.  
937. <li>account include system-auth</li>
938.  
939.  
940.  
941. <li>password include system-auth</li>
942.  
943.  
944.  
945. <li>session optional pam_keyinit.so revoke</li>
946.  
947.  
948.  
949. <li>session required pam_limits.so</li>
950.  
951.  
952.  
953. <li>session include system-auth</li>
954. </ul>
955. </li>
956.  
957.  
958.  
959. <li>/etc/pam.d/lightdm
960. <ul class="wp-block-list">
961. <li>auth sufficient pam_u2f.so authfile=/etc/u2f_mappings cue pinverification=always origin=pam://fedora appid=pam://fedora</li>
962.  
963.  
964.  
965. <li>auth [success=done ignore=ignore default=bad] pam_selinux_permit.so</li>
966.  
967.  
968.  
969. <li>auth required pam_env.so</li>
970.  
971.  
972.  
973. <li>auth substack system-auth</li>
974.  
975.  
976.  
977. <li>auth include postlogin</li>
978.  
979.  
980.  
981. <li>account required pam_nologin.so</li>
982.  
983.  
984.  
985. <li>account include system-auth</li>
986.  
987.  
988.  
989. <li>password include system-auth</li>
990.  
991.  
992.  
993. <li>session required pam_selinux.so close</li>
994.  
995.  
996.  
997. <li>session required pam_loginuid.so</li>
998.  
999.  
1000.  
1001. <li>session required pam_selinux.so open</li>
1002.  
1003.  
1004.  
1005. <li>session optional pam_keyinit.so force revoke</li>
1006.  
1007.  
1008.  
1009. <li>session required pam_namespace.so</li>
1010.  
1011.  
1012.  
1013. <li>session include system-auth</li>
1014.  
1015.  
1016.  
1017. <li>session optional pam_lastlog.so silent</li>
1018.  
1019.  
1020.  
1021. <li>session include postlogin</li>
1022. </ul>
1023. </li>
1024.  
1025.  
1026.  
1027. <li>/etc/pam.d/cinnamon-screensaver
1028. <ul class="wp-block-list">
1029. <li>auth sufficient pam_u2f.so authfile=/etc/u2f_mappings cue pinverification=always origin=pam://fedora appid=pam://fedora</li>
1030.  
1031.  
1032.  
1033. <li>auth include system-auth</li>
1034.  
1035.  
1036.  
1037. <li>account include system-auth</li>
1038.  
1039.  
1040.  
1041. <li>password include system-auth</li>
1042.  
1043.  
1044.  
1045. <li>session include system-auth</li>
1046. </ul>
1047. </li>
1048. </ul>
1049. </li>
1050. </ol>
1051.  
1052.  
1053.  
1054. <pre class="wp-block-preformatted"></pre>
1055.  
1056.  
1057.  
1058. <h3 class="wp-block-heading">Phase 5: Polkit Configuration (Optional)</h3>
1059.  
1060.  
1061.  
1062. <p>Polkit GUI prompts were <strong>not enabled</strong> on my test system (no <kbd>/etc/pam.d/polkit-1</kbd> and no running user agent). If you want FIDO2 for Polkit dialogs, ensure a compatible agent is running (for Cinnamon: <kbd>polkit-gnome-authentication-agent-1</kbd>). In testing, GUI prompts were not enabled by default and required additional configuration.”<br /></p>
1063.  
1064.  
1065.  
1066. <p><strong>Screensaver unlock:</strong> When the screen is locked, Fedora may default to the password prompt. Click the small <strong>two-person icon</strong> to switch to the FIDO2 method. Keep a fall-back password available. In various tests some desktop prompts did not always default to FIDO2.</p>
1067.  
1068.  
1069.  
1070. <h3 class="wp-block-heading">Phase 6: Testing</h3>
1071.  
1072.  
1073.  
1074. <h4 class="wp-block-heading">Reboot the system</h4>
1075.  
1076.  
1077.  
1078. <figure class="wp-block-image size-large"><a href="https://fedoramagazine.org/wp-content/uploads/2025/09/one.jpeg"><img decoding="async" width="970" height="1024" src="https://fedoramagazine.org/wp-content/uploads/2025/09/one-970x1024.jpeg" alt="" class="wp-image-42547" srcset="https://fedoramagazine.org/wp-content/uploads/2025/09/one-970x1024.jpeg 970w, https://fedoramagazine.org/wp-content/uploads/2025/09/one-284x300.jpeg 284w, https://fedoramagazine.org/wp-content/uploads/2025/09/one-768x810.jpeg 768w, https://fedoramagazine.org/wp-content/uploads/2025/09/one-1456x1536.jpeg 1456w, https://fedoramagazine.org/wp-content/uploads/2025/09/one-816x861.jpeg 816w, https://fedoramagazine.org/wp-content/uploads/2025/09/one.jpeg 1849w" sizes="(max-width: 970px) 100vw, 970px" /></a><figcaption class="wp-element-caption">Boot screen asking for LUKS2 token PIN.</figcaption></figure>
1079.  
1080.  
1081.  
1082. <h4 class="wp-block-heading">Confirm functionality</h4>
1083.  
1084.  
1085.  
1086. <p>The following sequence of images shows the following:</p>
1087.  
1088.  
1089.  
1090. <ul class="wp-block-list">
1091. <li>FDE (LUKS Unlock): PIN + Touch prompt appears at boot</li>
1092.  
1093.  
1094.  
1095. <li>GUI Login (LightDM): PIN + Touch required</li>
1096.  
1097.  
1098.  
1099. <li>Sudo: <kbd>sudo echo test</kbd> should prompt for PIN + Touch</li>
1100.  
1101.  
1102.  
1103. <li>Cinnamon lock screen: PIN + Touch (switch input method)</li>
1104.  
1105.  
1106.  
1107. <li>Polkit: GUI software install or <kbd>pkexec</kbd> prompts for PIN + Touch</li>
1108. </ul>
1109.  
1110.  
1111.  
1112. <figure class="wp-block-image size-large"><a href="https://fedoramagazine.org/wp-content/uploads/2025/09/two.jpeg"><img loading="lazy" decoding="async" width="1024" height="768" src="https://fedoramagazine.org/wp-content/uploads/2025/09/two-1024x768.jpeg" alt="" class="wp-image-42546" srcset="https://fedoramagazine.org/wp-content/uploads/2025/09/two-1024x768.jpeg 1024w, https://fedoramagazine.org/wp-content/uploads/2025/09/two-300x225.jpeg 300w, https://fedoramagazine.org/wp-content/uploads/2025/09/two-768x576.jpeg 768w, https://fedoramagazine.org/wp-content/uploads/2025/09/two-1536x1152.jpeg 1536w, https://fedoramagazine.org/wp-content/uploads/2025/09/two-2048x1536.jpeg 2048w, https://fedoramagazine.org/wp-content/uploads/2025/09/two-816x612.jpeg 816w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></a><figcaption class="wp-element-caption">FDE (LUKS Unlock): PIN + Touch prompt appears at boot<br />FIDO2 key lit up, waiting for touch to complete full-disk unlock.</figcaption></figure>
1113.  
1114.  
1115.  
1116. <figure class="wp-block-image size-large"><a href="https://fedoramagazine.org/wp-content/uploads/2025/09/three.jpeg"><img loading="lazy" decoding="async" width="1024" height="768" src="https://fedoramagazine.org/wp-content/uploads/2025/09/three-1024x768.jpeg" alt="" class="wp-image-42545" srcset="https://fedoramagazine.org/wp-content/uploads/2025/09/three-1024x768.jpeg 1024w, https://fedoramagazine.org/wp-content/uploads/2025/09/three-300x225.jpeg 300w, https://fedoramagazine.org/wp-content/uploads/2025/09/three-768x576.jpeg 768w, https://fedoramagazine.org/wp-content/uploads/2025/09/three-1536x1152.jpeg 1536w, https://fedoramagazine.org/wp-content/uploads/2025/09/three-2048x1536.jpeg 2048w, https://fedoramagazine.org/wp-content/uploads/2025/09/three-816x612.jpeg 816w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></a><figcaption class="wp-element-caption">GUI login PIN<br />Fedora LightDM login screen prompting for FIDO2 key PIN.</figcaption></figure>
1117.  
1118.  
1119.  
1120. <figure class="wp-block-image size-large"><a href="https://fedoramagazine.org/wp-content/uploads/2025/09/four.jpeg"><img loading="lazy" decoding="async" width="1024" height="768" src="https://fedoramagazine.org/wp-content/uploads/2025/09/four-1024x768.jpeg" alt="" class="wp-image-42544" srcset="https://fedoramagazine.org/wp-content/uploads/2025/09/four-1024x768.jpeg 1024w, https://fedoramagazine.org/wp-content/uploads/2025/09/four-300x225.jpeg 300w, https://fedoramagazine.org/wp-content/uploads/2025/09/four-768x576.jpeg 768w, https://fedoramagazine.org/wp-content/uploads/2025/09/four-1536x1152.jpeg 1536w, https://fedoramagazine.org/wp-content/uploads/2025/09/four-2048x1536.jpeg 2048w, https://fedoramagazine.org/wp-content/uploads/2025/09/four-816x612.jpeg 816w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></a><figcaption class="wp-element-caption">GUI login key touch<br />Login process with FIDO2 key lit up, requiring touch to proceed.</figcaption></figure>
1121.  
1122.  
1123.  
1124. <figure class="wp-block-image size-large"><a href="https://fedoramagazine.org/wp-content/uploads/2025/09/five.jpeg"><img loading="lazy" decoding="async" width="1024" height="768" src="https://fedoramagazine.org/wp-content/uploads/2025/09/five-1024x768.jpeg" alt="" class="wp-image-42543" srcset="https://fedoramagazine.org/wp-content/uploads/2025/09/five-1024x768.jpeg 1024w, https://fedoramagazine.org/wp-content/uploads/2025/09/five-300x225.jpeg 300w, https://fedoramagazine.org/wp-content/uploads/2025/09/five-768x576.jpeg 768w, https://fedoramagazine.org/wp-content/uploads/2025/09/five-1536x1152.jpeg 1536w, https://fedoramagazine.org/wp-content/uploads/2025/09/five-2048x1536.jpeg 2048w, https://fedoramagazine.org/wp-content/uploads/2025/09/five-816x612.jpeg 816w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></a><figcaption class="wp-element-caption">GUI login completion<br />Login screen showing successful authentication, ready to “Log In.”</figcaption></figure>
1125.  
1126.  
1127.  
1128. <figure class="wp-block-image size-large"><a href="https://fedoramagazine.org/wp-content/uploads/2025/09/six.jpeg"><img loading="lazy" decoding="async" width="1024" height="768" src="https://fedoramagazine.org/wp-content/uploads/2025/09/six-1024x768.jpeg" alt="" class="wp-image-42542" srcset="https://fedoramagazine.org/wp-content/uploads/2025/09/six-1024x768.jpeg 1024w, https://fedoramagazine.org/wp-content/uploads/2025/09/six-300x225.jpeg 300w, https://fedoramagazine.org/wp-content/uploads/2025/09/six-768x576.jpeg 768w, https://fedoramagazine.org/wp-content/uploads/2025/09/six-1536x1152.jpeg 1536w, https://fedoramagazine.org/wp-content/uploads/2025/09/six-2048x1536.jpeg 2048w, https://fedoramagazine.org/wp-content/uploads/2025/09/six-816x612.jpeg 816w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></a><figcaption class="wp-element-caption">Sudo escalation (terminal)<br />Example of sudo test requiring PIN + touch in terminal.</figcaption></figure>
1129.  
1130.  
1131.  
1132. <figure class="wp-block-image size-large"><a href="https://fedoramagazine.org/wp-content/uploads/2025/09/seven.jpeg"><img loading="lazy" decoding="async" width="1024" height="768" src="https://fedoramagazine.org/wp-content/uploads/2025/09/seven-1024x768.jpeg" alt="" class="wp-image-42541" srcset="https://fedoramagazine.org/wp-content/uploads/2025/09/seven-1024x768.jpeg 1024w, https://fedoramagazine.org/wp-content/uploads/2025/09/seven-300x225.jpeg 300w, https://fedoramagazine.org/wp-content/uploads/2025/09/seven-768x576.jpeg 768w, https://fedoramagazine.org/wp-content/uploads/2025/09/seven-1536x1152.jpeg 1536w, https://fedoramagazine.org/wp-content/uploads/2025/09/seven-2048x1536.jpeg 2048w, https://fedoramagazine.org/wp-content/uploads/2025/09/seven-816x612.jpeg 816w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></a><figcaption class="wp-element-caption">Locked screen where the user may need to click the person icon to switch back to FIDO2 login.</figcaption></figure>
1133.  
1134.  
1135.  
1136. <h4 class="wp-block-heading">Confirm the fallback password login remains functional</h4>
1137.  
1138.  
1139.  
1140. <figure class="wp-block-image size-large"><a href="https://fedoramagazine.org/wp-content/uploads/2025/09/eight.jpeg"><img loading="lazy" decoding="async" width="1024" height="768" src="https://fedoramagazine.org/wp-content/uploads/2025/09/eight-1024x768.jpeg" alt="" class="wp-image-42540" srcset="https://fedoramagazine.org/wp-content/uploads/2025/09/eight-1024x768.jpeg 1024w, https://fedoramagazine.org/wp-content/uploads/2025/09/eight-300x225.jpeg 300w, https://fedoramagazine.org/wp-content/uploads/2025/09/eight-768x576.jpeg 768w, https://fedoramagazine.org/wp-content/uploads/2025/09/eight-1536x1152.jpeg 1536w, https://fedoramagazine.org/wp-content/uploads/2025/09/eight-2048x1536.jpeg 2048w, https://fedoramagazine.org/wp-content/uploads/2025/09/eight-816x612.jpeg 816w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></a><figcaption class="wp-element-caption">Locked screen PIN entry<br />Re-login screen asking for FIDO2 key PIN to unlock session.</figcaption></figure>
1141.  
1142.  
1143.  
1144. <h2 class="wp-block-heading">Recovery and Backup</h2>
1145.  
1146.  
1147.  
1148. <p><strong>Backup:</strong></p>
1149.  
1150.  
1151.  
1152. <pre class="wp-block-preformatted"><kbd>mkdir -p ~/fido2-audit/pam_restore<br />for file in sudo lightdm cinnamon-screensaver system-auth password-auth polkit-1; <br />do<br />  sudo cp ~/fido2-audit/pam/$file ~/fido2-audit/pam_restore/$file<br />done</kbd></pre>
1153.  
1154.  
1155.  
1156. <p><strong>Restore if needed</strong> using TTY or Live USB.</p>
1157.  
1158.  
1159.  
1160. <p><strong>Emergency Login:</strong></p>
1161.  
1162.  
1163.  
1164. <ul class="wp-block-list">
1165. <li>Use a high-entropy admin password</li>
1166.  
1167.  
1168.  
1169. <li>Store the password securely off-line or in encrypted container</li>
1170. </ul>
1171.  
1172.  
1173.  
1174. <h2 class="wp-block-heading">Troubleshooting</h2>
1175.  
1176.  
1177.  
1178. <p><strong>Multiple FIDO2 Keys:</strong></p>
1179.  
1180.  
1181.  
1182. <pre class="wp-block-preformatted">lsusb
1183. sudo usbreset /dev/bus/usb/001/003</pre>
1184.  
1185.  
1186.  
1187. <h2 class="wp-block-heading">Warnings</h2>
1188.  
1189.  
1190.  
1191. <ul class="wp-block-list">
1192. <li>Never test on production systems</li>
1193.  
1194.  
1195.  
1196. <li>Back up <kbd>/etc/crypttab</kbd> and  <kbd>/etc/pam.d/*</kbd></li>
1197.  
1198.  
1199.  
1200. <li>Avoid running <kbd>dracut --force</kbd> unless ready</li>
1201. </ul>
1202.  
1203.  
1204.  
1205. <h2 class="wp-block-heading">Security Notes</h2>
1206.  
1207.  
1208.  
1209. <p><strong>Strengths:</strong></p>
1210.  
1211.  
1212.  
1213. <ul class="wp-block-list">
1214. <li>Hardware-backed auth</li>
1215.  
1216.  
1217.  
1218. <li>PIN + Touch = Strong 2FA</li>
1219. </ul>
1220.  
1221.  
1222.  
1223. <p><strong>Risks:</strong></p>
1224.  
1225.  
1226.  
1227. <ul class="wp-block-list">
1228. <li>Loss of key</li>
1229.  
1230.  
1231.  
1232. <li>System updates may break compatibility</li>
1233. </ul>
1234.  
1235.  
1236.  
1237. <p><strong>Recommendations:</strong></p>
1238.  
1239.  
1240.  
1241. <ul class="wp-block-list">
1242. <li>Always keep a fall-back passphrase</li>
1243.  
1244.  
1245.  
1246. <li>Register a backup FIDO2 key</li>
1247.  
1248.  
1249.  
1250. <li>Back up <kbd>/etc/u2f_mappings</kbd> and test after upgrades</li>
1251. </ul>
1252.  
1253.  
1254.  
1255. <h2 class="wp-block-heading">Performance Considerations</h2>
1256.  
1257.  
1258.  
1259. <figure class="wp-block-table"><table class="has-fixed-layout"><tbody><tr><th>Component</th><th>Delay Added</th></tr><tr><td>Boot (FDE)</td><td>~5–10 seconds</td></tr><tr><td>GUI Login</td><td>~2–3 seconds</td></tr><tr><td>Sudo/Polkit</td><td>~1–2 seconds</td></tr></tbody></table></figure>
1260.  
1261.  
1262.  
1263. <h2 class="wp-block-heading">Conclusion</h2>
1264.  
1265.  
1266.  
1267. <p>This guide demonstrates the successful integration of a uTrust FIDO2 security key with Fedora 42 for secure authentication across <strong>LUKS2 full-disk encryption, LightDM login, </strong>and<strong> sudo elevation</strong>. The setup is stable, reproducible, and well-suited for labs or intermediate Fedora users.</p>
1268.  
1269.  
1270.  
1271. <p>Polkit integration is optional and may vary by desktop environment. In testing, GUI prompts were not enabled by default and required additional configuration.</p>
1272.  
1273.  
1274.  
1275. <p><br /><br /><br /><br /><br /></p>
1276. ]]></content:encoded>
1278. <wfw:commentRss>https://fedoramagazine.org/integrating-utrust-fido2-security-key-for-disk-encryption-login-and-sudo-access-for-fedora-42/feed/</wfw:commentRss>
1279. <slash:comments>8</slash:comments>
1282. <post-id xmlns="com-wordpress:feed-additions:1">42404</post-id><enclosure url="https://fedoramagazine.org/wp-content/uploads/2025/07/FIDO_LUKS_sudo-300x127.jpg" length="9947" type="image/jpg" /> </item>
1283. <item>
1284. <title>Introducing complyctl for Effortless Compliance in Fedora</title>
1285. <link>https://fedoramagazine.org/effortless-flexible-scalable-and-standardized-compliance-checks-for-fedora-using-complyctl/</link>
1286. <comments>https://fedoramagazine.org/effortless-flexible-scalable-and-standardized-compliance-checks-for-fedora-using-complyctl/#comments</comments>
1288. <dc:creator><![CDATA[Marcus Burghardt]]></dc:creator>
1289. <pubDate>Wed, 17 Sep 2025 08:00:00 +0000</pubDate>
1290. <category><![CDATA[Fedora Project community]]></category>
1291. <category><![CDATA[For System Administrators]]></category>
1292. <category><![CDATA[CompliancAsCode]]></category>
1293. <category><![CDATA[complyctl]]></category>
1294. <category><![CDATA[ComplyTime]]></category>
1295. <guid isPermaLink="false">https://fedoramagazine.org/?p=42553</guid>
1296.  
1297. <description><![CDATA[complyctl is a powerful command-line utility implementing the principles of “ComplianceAsCode” (CaC) with high scalability and adaptability for security compliance. In today&#8217;s rapidly evolving digital landscape, maintaining a robust security posture isn&#8217;t just a best practice &#8211; it is a necessity. For Fedora users, system administrators, and developers, ensuring that your systems meet various security [&#8230;]]]></description>
1298. <content:encoded><![CDATA[
1299. <p><em>complyctl</em> is a powerful command-line utility implementing the principles of “ComplianceAsCode” (CaC) with high scalability and adaptability for security compliance.</p>
1300.  
1301.  
1302.  
1303. <span id="more-42553"></span>
1304.  
1305.  
1306.  
1307. <p>In today&#8217;s rapidly evolving digital landscape, maintaining a robust security posture isn&#8217;t just a best practice &#8211; it is a necessity. For Fedora users, system administrators, and developers, ensuring that your systems meet various security and regulatory requirements can often feel like a daunting, manual task. But what if you could standardize and automate much of this process, making compliance checks faster, easier to audit, and seamlessly integrated into your workflows?</p>
1308.  
1309.  
1310.  
1311. <p>This is now a reality enabled with multiple <a href="https://github.com/complytime" target="_blank" rel="noreferrer noopener">ComplyTime</a> projects. These focus on specific tasks designed to be easily integrated. They allow a robust, flexible, and scalable combination of microservices communicating with standardized formats that ultimately allow a powerful capability to much more easily adapt to the compliance demands. This also allow faster adoption of new technologies. There are multiple exciting projects actively and quickly evolving under the umbrella of <a href="https://github.com/complytime" target="_blank" rel="noreferrer noopener">ComplyTime</a> organization. In this article I would like to highlight <a href="https://github.com/complytime/complyctl" target="_blank" rel="noreferrer noopener">complyctl</a>, the ComplyTime CLI for Fedora, and its main features that make it an excellent option to easily maintain a robust security posture in your Fedora systems.</p>
1312.  
1313.  
1314.  
1315. <p><em>complyctl</em> is a powerful command-line utility available since Fedora 42. It&#8217;s design uses the principles of &#8220;ComplianceAsCode&#8221; (CaC) with high scalability and adaptability. It contains a technology agnostic core and is easily extended with plugins. This allows users to use the best of every available underlying technology with a simple and standardized user interface.</p>
1316.  
1317.  
1318.  
1319. <h3 class="wp-block-heading">The Power of ComplianceAsCode with complyctl</h3>
1320.  
1321.  
1322.  
1323. <p>At its heart, <em>complyctl</em> is a tool for performing compliance assessment activities, scaled by a flexible plugin system that allows users to perform compliance check activities with a flexible combination of the best available assessment technologies.</p>
1324.  
1325.  
1326.  
1327. <p>The <em>complyclt</em> plugin architecture allows quick adoption and combination of different scanner technologies. The core design is technology agnostic with standardizing inputs and outputs using machine readable formats that allow high reusability and shareability of compliance artifacts. Currently it leverages the <a href="https://pages.nist.gov/OSCAL/" target="_blank" rel="noreferrer noopener">Open Security Controls Assessment Language (OSCAL)</a> and its anti-fragile architecture also allows a smooth adoption of future standards, making it a reliable and continuous modern solution for the long-term.</p>
1328.  
1329.  
1330.  
1331. <p>&nbsp;This might sound technical, but the benefits are simple:</p>
1332.  
1333.  
1334.  
1335. <ol class="wp-block-list">
1336. <li><strong>Automation and Speed:</strong> Traditional compliance audits can be slow, manual, complex and prone to human error. <em>complyctl</em> relies on standardized machine readable formats, allowing automation without technology or vendor lock-in.</li>
1337.  
1338.  
1339.  
1340. <li><strong>Accuracy and Consistency:</strong> Machines are inherently more consistent than human reviewers. <em>complyctl&#8217;s</em> reliance on OSCAL provides a standardized format for expressing security controls, assessment plans, and results. This standardization is crucial for interoperability. It allows consistent processing and understanding of compliance data across different tools and systems.</li>
1341.  
1342.  
1343.  
1344. <li><strong>Scalability and Integration:</strong> <em>complyctl</em> simplifies compliance checks integration in your development and deployment pipelines. An <a href="https://pages.nist.gov/OSCAL/learn/concepts/layer/assessment/" target="_blank" rel="noreferrer noopener">OSCAL Assessment Plan</a> can be created and customized once and reused across multiple systems. Ultimately compliance checks can be implemented faster and compliance gaps are caught earlier. This prevents non-compliant configurations from reaching production environments.</li>
1345.  
1346.  
1347.  
1348. <li><strong>Extensibility with Plugins (including OpenSCAP):</strong> The plugin-based architecture of <em>complyctl</em> makes it incredibly versatile. An example is the <em>complyctl-openscap-plugin</em>, which extends <em>complyctl&#8217;s</em> capabilities to use OpenSCAP Scanner and the rich content provided by <a href="https://src.fedoraproject.org/rpms/scap-security-guide" target="_blank" rel="noreferrer noopener">scap-security-guide</a> package. This allows an immediate and smooth adoption of <em>complyctl</em> using a well-established assessment engine while providing a modern, OSCAL-driven workflow for managing and executing security compliance checks. It also allows a smooth and gradual transition to other scanner technologies.</li>
1349. </ol>
1350.  
1351.  
1352.  
1353. <p>By embracing <em>complyctl</em>, Fedora users can more easily maintain a strong security posture.</p>
1354.  
1355.  
1356.  
1357. <h3 class="wp-block-heading">Getting Started with complyctl: A Practical Tutorial</h3>
1358.  
1359.  
1360.  
1361. <p>Ready to put <em>complyctl</em> to work? It is likely simpler than you expect. The following is a step-by-step guide to start using <em>complyctl</em> on your Fedora system.</p>
1362.  
1363.  
1364.  
1365. <h4 class="wp-block-heading">1. Installation</h4>
1366.  
1367.  
1368.  
1369. <p>First, install <em>complyctl</em>, if necessary. It is <a href="https://src.fedoraproject.org/rpms/complyctl" target="_blank" rel="noreferrer noopener">available as an RPM package</a> in official repositories:</p>
1370.  
1371.  
1372.  
1373. <pre class="wp-block-preformatted">sudo dnf install complyctl</pre>
1374.  
1375.  
1376.  
1377. <h4 class="wp-block-heading">2. Understanding the Workflow</h4>
1378.  
1379.  
1380.  
1381. <p><em>complyctl</em> follows a logical, sequential workflow:</p>
1382.  
1383.  
1384.  
1385. <ul class="wp-block-list">
1386. <li><strong>list</strong>: Discover available compliance frameworks.</li>
1387.  
1388.  
1389.  
1390. <li><strong>plan</strong>: Create an OSCAL <a href="https://pages.nist.gov/OSCAL/learn/concepts/layer/assessment/assessment-plan/" target="_blank" rel="noreferrer noopener">Assessment Plan</a> based on a chosen framework. This plan acts as your assessment configuration.</li>
1391.  
1392.  
1393.  
1394. <li><strong>generate</strong>: Generate executable policy artifacts for each installed plugin based on the OSCAL Assessment Plan.</li>
1395.  
1396.  
1397.  
1398. <li><strong>scan</strong>: Call the installed plugins to scan the system using their respective policies and finally aggregate the results in a single OSCAL <a href="https://pages.nist.gov/OSCAL/learn/concepts/layer/assessment/assessment-results/" target="_blank" rel="noreferrer noopener">Assessment Results</a> file.</li>
1399. </ul>
1400.  
1401.  
1402.  
1403. <p>Let&#8217;s walk through these commands.</p>
1404.  
1405.  
1406.  
1407. <h4 class="wp-block-heading">3. Step-by-Step Tutorial</h4>
1408.  
1409.  
1410.  
1411. <p><strong>Step 1: List Available Frameworks</strong></p>
1412.  
1413.  
1414.  
1415. <p>To begin, you need to know which compliance frameworks <em>complyctl</em> can assess your system against. Currently the <em>complyctl</em> package includes the <a href="https://github.com/ComplianceAsCode/content/blob/master/controls/cusp_fedora.yml" target="_blank" rel="noreferrer noopener">CUSP Profile</a>  out-of-the-box.</p>
1416.  
1417.  
1418.  
1419. <p>Use the <em>list</em> command to show the available frameworks:</p>
1420.  
1421.  
1422.  
1423. <pre class="wp-block-preformatted">complyctl list</pre>
1424.  
1425.  
1426.  
1427. <p>This command will output a table, showing the available frameworks. Look for the <em>Framework ID</em> column, as you&#8217;ll need this for the next step.</p>
1428.  
1429.  
1430.  
1431. <p>Example:</p>
1432.  
1433.  
1434.  
1435. <figure class="wp-block-image size-large"><a href="https://fedoramagazine.org/wp-content/uploads/2025/09/complyctl_list.png"><img loading="lazy" decoding="async" width="1024" height="299" src="https://fedoramagazine.org/wp-content/uploads/2025/09/complyctl_list-1024x299.png" alt="" class="wp-image-42574" srcset="https://fedoramagazine.org/wp-content/uploads/2025/09/complyctl_list-1024x299.png 1024w, https://fedoramagazine.org/wp-content/uploads/2025/09/complyctl_list-300x88.png 300w, https://fedoramagazine.org/wp-content/uploads/2025/09/complyctl_list-768x225.png 768w, https://fedoramagazine.org/wp-content/uploads/2025/09/complyctl_list-816x239.png 816w, https://fedoramagazine.org/wp-content/uploads/2025/09/complyctl_list.png 1149w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></a></figure>
1436.  
1437.  
1438.  
1439. <p>Optionally, you can also include the <kbd>--plain</kbd> option for simplified output.</p>
1440.  
1441.  
1442.  
1443. <p><strong>Step 2: Create an Assessment Plan</strong></p>
1444.  
1445.  
1446.  
1447. <p>Once you&#8217;ve identified a <em>Framework ID</em>, you can create an OSCAL Assessment Plan. This plan defines what will be assessed. The <em>plan</em> command will generate an <em>assessment-plan.json</em> file in the complytime directory.</p>
1448.  
1449.  
1450.  
1451. <pre class="wp-block-preformatted">complyctl plan cusp_fedora</pre>
1452.  
1453.  
1454.  
1455. <p>This command creates the user workspace in the &#8220;complytime&#8221; directory:</p>
1456.  
1457.  
1458.  
1459. <pre class="wp-block-preformatted">tree complytime
1460. complytime/
1461. └── assessment-plan.json</pre>
1462.  
1463.  
1464.  
1465. <p>The JSON file is a machine-readable representation of your chosen compliance policy.</p>
1466.  
1467.  
1468.  
1469. <p><strong>Step 3: Install a plugin</strong></p>
1470.  
1471.  
1472.  
1473. <p>In this tutorial we will use OpenSCAP Scanner as the underlying technology for compliance checks. So, we also want to install the OpenSCAP plugin for <em>complyctl</em> as well the OpenSCAP content delivered by <em>scap-security-guide</em> package:</p>
1474.  
1475.  
1476.  
1477. <pre class="wp-block-preformatted">sudo dnf install complyctl-openscap-plugin scap-security-guide</pre>
1478.  
1479.  
1480.  
1481. <p><strong>Step 4: Generate Policy Artifacts</strong></p>
1482.  
1483.  
1484.  
1485. <p>With your <em>assessment-plan.json</em> in place, and the desired plugins installed, the <em>generate</em> command  translates this declarative plan into policy artifacts for the installed plugins. These are the actual plugin specific instructions <em>complyctl</em> plugins will use to perform the checks.</p>
1486.  
1487.  
1488.  
1489. <pre class="wp-block-preformatted">complyctl generate</pre>
1490.  
1491.  
1492.  
1493. <p>This command prepares the assessment for execution.</p>
1494.  
1495.  
1496.  
1497. <pre class="wp-block-preformatted">tree complytime/
1498.  
1499. complytime/
1500. ├── assessment-plan.json
1501. └── openscap
1502.     ├── policy
1503.     │   └── tailoring_policy.xml
1504.     ├── remediations
1505.     │   ├── remediation-blueprint.toml
1506.     │   ├── remediation-playbook.yml
1507.     │   └── remediation-script.sh
1508. &nbsp;&nbsp;&nbsp;&nbsp;└── results</pre>
1509.  
1510.  
1511.  
1512. <p><strong>Step 5: Execute the Compliance Scan</strong></p>
1513.  
1514.  
1515.  
1516. <p>Finally, the <em>scan</em> command runs the assessment using the installed plugins. The results will appear in the <em>assessment-results.json</em>, file by default.</p>
1517.  
1518.  
1519.  
1520. <pre class="wp-block-preformatted">complyctl scan</pre>
1521.  
1522.  
1523.  
1524. <p>For human-readable output, which is useful for review and reporting, you can add the <kbd>--with-md</kbd> option. This will generate both <em>assessment-results.json</em> and <em>assessment-results.md</em> files.</p>
1525.  
1526.  
1527.  
1528. <pre class="wp-block-preformatted">complyctl scan --with-md</pre>
1529.  
1530.  
1531.  
1532. <p>This Markdown file provides a clear, digestible summary of your system&#8217;s compliance status, making it easy to share with auditors or other stakeholders.</p>
1533.  
1534.  
1535.  
1536. <pre class="wp-block-preformatted">tree complytime/
1537. complytime/
1538. ├── assessment-plan.json
1539. ├── assessment-results.json
1540. ├── assessment-results.md
1541. └── openscap
1542.    ├── policy
1543.    │   └── tailoring_policy.xml
1544.    ├── remediations
1545.    │   ├── remediation-blueprint.toml
1546.    │   ├── remediation-playbook.yml
1547.    │   └── remediation-script.sh
1548.    └── results
1549.        ├── arf.xml
1550.        └── results.xml</pre>
1551.  
1552.  
1553.  
1554. <h3 class="wp-block-heading"><strong>Final thoughts</strong></h3>
1555.  
1556.  
1557.  
1558. <p><em>complyctl</em> is an open-source tool built for and by the community. We encourage you to give it a try.</p>
1559.  
1560.  
1561.  
1562. <ul class="wp-block-list">
1563. <li>Find us on GitHub at <a href="https://github.com/complytime/complyctl" target="_blank" rel="noreferrer noopener">complyctl repository</a>.</li>
1564.  
1565.  
1566.  
1567. <li>If you find an issue or have a feature request, please open an issue, propose a PR, or contact the maintainers. Your feedback will help shape the future of this tool.</li>
1568.  
1569.  
1570.  
1571. <li>Collaboration on <a href="https://github.com/ComplianceAsCode/content" target="_blank" rel="noreferrer noopener">ComplianceAsCode/content</a> community is also welcome to help us shaping <a href="https://github.com/ComplianceAsCode/oscal-content/tree/main" target="_blank" rel="noreferrer noopener">Compliance profiles</a> for Fedora.</li>
1572. </ul>
1573.  
1574.  
1575.  
1576. <p></p>
1577. ]]></content:encoded>
1579. <wfw:commentRss>https://fedoramagazine.org/effortless-flexible-scalable-and-standardized-compliance-checks-for-fedora-using-complyctl/feed/</wfw:commentRss>
1580. <slash:comments>6</slash:comments>
1583. <post-id xmlns="com-wordpress:feed-additions:1">42553</post-id><enclosure url="https://fedoramagazine.org/wp-content/uploads/2025/09/intro_2_complyctl-300x127.jpg" length="7400" type="image/jpg" /> </item>
1584. <item>
1585. <title>Announcing Fedora Linux 43 Beta</title>
1586. <link>https://fedoramagazine.org/announcing-fedora-linux-43-beta/</link>
1588. <dc:creator><![CDATA[Aoife Moloney]]></dc:creator>
1589. <pubDate>Tue, 16 Sep 2025 14:05:00 +0000</pubDate>
1590. <category><![CDATA[Fedora Project community]]></category>
1591. <category><![CDATA[Beta]]></category>
1592. <category><![CDATA[F43]]></category>
1593. <category><![CDATA[Fedora Linux 43]]></category>
1594. <guid isPermaLink="false">https://fedoramagazine.org/?p=42576</guid>
1595.  
1596. <description><![CDATA[On Tuesday, 16 September 2025, it is our pleasure to announce the availability of Fedora Linux 43 Beta! This release comes packed with the latest version upgrades of existing features, plus a few new ones too. As with every beta release, this is your opportunity to test out the upcoming Fedora Linux release and give [&#8230;]]]></description>
1597. <content:encoded><![CDATA[
1598. <p>On Tuesday, 16 September 2025, it is our pleasure to announce the availability of Fedora Linux 43 Beta! This release comes packed with the latest version upgrades of existing features, plus a few new ones too. As with every beta release, this is your opportunity to test out the upcoming Fedora Linux release and give some feedback to help us fine tune F43 final. We hope you enjoy this latest version of Fedora!</p>
1599.  
1600.  
1601.  
1602. <span id="more-42576"></span>
1603.  
1604.  
1605.  
1606. <h2 class="wp-block-heading">How to get the beta release</h2>
1607.  
1608.  
1609.  
1610. <p>You can download F43 Beta, or our pre-release edition versions, from any of the following places:</p>
1611.  
1612.  
1613.  
1614. <ul class="wp-block-list">
1615. <li><a href="https://fedoraproject.org/workstation/download/?beta" target="_blank" rel="noreferrer noopener">Fedora Workstation 43 Beta</a></li>
1616.  
1617.  
1618.  
1619. <li><a href="https://fedoraproject.org/kde/download/?beta" target="_blank" rel="noreferrer noopener">Fedora KDE Plasma Desktop 43 Beta</a></li>
1620.  
1621.  
1622.  
1623. <li><a href="https://fedoraproject.org/server/download/?beta" target="_blank" rel="noreferrer noopener">Fedora Server 43 Beta</a></li>
1624.  
1625.  
1626.  
1627. <li><a href="https://fedoraproject.org/iot/download/?beta" target="_blank" rel="noreferrer noopener">Fedora IoT 43 Beta</a></li>
1628.  
1629.  
1630.  
1631. <li><a href="https://fedoraproject.org/cloud/download/?beta" target="_blank" rel="noreferrer noopener">Fedora Cloud 43 Beta</a></li>
1632. </ul>
1633.  
1634.  
1635.  
1636. <p>The Fedora CoreOS “next” stream moves to the beta release one week later, but content for F43 is still available from their current <a href="https://builds.coreos.fedoraproject.org/browser?stream=branched&amp;arch=x86_64" target="_blank" rel="noreferrer noopener">branched</a> stream to enjoy now.</p>
1637.  
1638.  
1639.  
1640. <p>You can also update an existing system to the beta using&nbsp;<a href="https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/" target="_blank" rel="noreferrer noopener">DNF system-upgrade</a>.</p>
1641.  
1642.  
1643.  
1644. <p>The F43 Beta release content is also available for Fedora <a href="https://fedoraproject.org/spins?beta" target="_blank" rel="noreferrer noopener">Spins</a> and <a href="https://fedoraproject.org/labs?beta" target="_blank" rel="noreferrer noopener">Labs</a>, with the exception of the following:</p>
1645.  
1646.  
1647.  
1648. <ul class="wp-block-list">
1649. <li>Mate &#8211; not currently available on any architectures with F43 content</li>
1650.  
1651.  
1652.  
1653. <li>i3 &#8211; not currently available on aarch64 only with F43 content</li>
1654. </ul>
1655.  
1656.  
1657.  
1658. <h2 class="wp-block-heading">F43 Beta highlights</h2>
1659.  
1660.  
1661.  
1662. <h3 class="wp-block-heading"><strong>Installer and desktop Improvements</strong></h3>
1663.  
1664.  
1665.  
1666. <p><strong>Anaconda WebUI for Fedora Spins by default:</strong> This creates a consistent and modern installation experience across all Fedora desktop variants. It brings us closer to eventually replacing the older GTK installer. This ensures all Fedora users can benefit from the same polished and user-friendly interface.</p>
1667.  
1668.  
1669.  
1670. <p><strong>Switch Anaconda installer to DNF5:</strong> This change provides better support and debugging for package-based applications within Anaconda. It is a bigger step towards the eventual deprecation or removal of DNF4, which is now in maintenance mode.</p>
1671.  
1672.  
1673.  
1674. <p><strong>Enable auto-updates by default in Fedora Kinoite:</strong> This change ensures that users are consistently running a system with the latest bug fixes and features after a simple reboot. Updates are applied automatically in the background.</p>
1675.  
1676.  
1677.  
1678. <p><strong>Set Default Monospace Fallback Font: </strong>  This change ensures that when a specified monospace font is missing, a consistent fallback font is used. Font selection also remains stable and predictable, even when the user installs new font packages. No jarring font changes should occur as appeared in previous versions.</p>
1679.  
1680.  
1681.  
1682. <h3 class="wp-block-heading"><strong>System enhancements</strong></h3>
1683.  
1684.  
1685.  
1686. <p><strong>GNU Toolchain Update:</strong> The updates to the GNU Toolchain ensures Fedora stays current with the latest features, improvements, and bug and security fixes from the upstream gcc, glibc, binutils, and gdb projects. They guarantees a working system compiler, assembler, static and dynamic linker, core language runtimes, and debugger.</p>
1687.  
1688.  
1689.  
1690. <p><strong>Package-specific RPM Macros For Build Flags:</strong> This change provides a consistent and standard way for packages to add to the default list of compiler flags. It also offers a cleaner and simpler method for package maintainers to make per-package adjustments to build flags. This avoids the need to manually edit and re-export environmental variables, and prevents potential issues that could arise from the old manual method. It ensures the consistent applications of flag adjustments.</p>
1691.  
1692.  
1693.  
1694. <p><strong>Build Fedora CoreOS using Containerfile:</strong> This change brings the FCOS build process under a standard container image build, moving away from the custom tool, CoreOS Assembler. It also means that anyone with Podman installed can build FCOS. This simplifies the process for both individual users and automated pipelines.</p>
1695.  
1696.  
1697.  
1698. <h3 class="wp-block-heading"><strong>Upgrades and removals</strong></h3>
1699.  
1700.  
1701.  
1702. <p><strong>Deprecate The Gold Linker:</strong> Deprecate the binutils-gold subpackage. This change simplifies the developer experience by reducing the number of available linkers from four to three. It streamlines choices for projects, and moves towards safeguarding the project against potential issues from &#8220;bitrot&#8221; where a package&#8217;s quality can decline and become unbuildable or insecure over time.</p>
1703.  
1704.  
1705.  
1706. <p><strong>Retire python-nose:</strong> The python-nose package will be removed in F43. This prevents  the creation of new packages with a dependency on an unmaintained test runner. Developers are encouraged to migrate to actively maintained testing frameworks such as python3-pytest or python3-nose2.</p>
1707.  
1708.  
1709.  
1710. <p><strong>Retire gtk3-rs, gtk-rs-core v0.18, and gtk4-rs v0.7:</strong>&nbsp; This change prevents Fedora from continuing to depend on old, unmaintained versions of these bindings. It also prevents shipping obsolete software and fewer unmaintained versions of packages.</p>
1711.  
1712.  
1713.  
1714. <p><strong>Python 3.14:</strong> Updating the Python stack in F43. This means that by building Fedora packages against an in-development version, critical bugs can be identified and reported before the final 3.14.0 release. This helps the entire Python ecosystem. Developers also gain access to the latest features in this release. More information is available at https://docs.python.org/3.14/whatsnew/3.14.html.</p>
1715.  
1716.  
1717.  
1718. <p><strong>Golang 1.25:</strong> This change provides Fedora Linux 43 Beta with the latest new features in Go. These include that <kbd>go build -asan </kbd>now defaults to leak detection at program exit, the <kbd>go doc -http </kbd>option starts a documentation server, and subdirectories of a repository can now be used as a module root. Since Fedora will keep as close to upstream as possible, this means we will continue to provide a reliable development platform for the Go language and projects written in it.&nbsp;</p>
1719.  
1720.  
1721.  
1722. <p><strong>Idris 2:</strong> Users gain access to new features in Idris 2. These include Quantitative Type Theory (QTT), which enables type-safe concurrent programming and fine-grained control over resource usage. It also has a new core language, a more minimal prelude library, and a new target to compile to, Chez Scheme.<br /></p>
1723.  
1724.  
1725.  
1726. <h2 class="wp-block-heading">More information</h2>
1727.  
1728.  
1729.  
1730. <p>Details and more information on the many great changes landing in Fedora Linux 43 are available on the <a href="https://fedoraproject.org/wiki/Releases/43/ChangeSet" target="_blank" rel="noreferrer noopener">Change Set</a> page.</p>
1731. ]]></content:encoded>
1735. <post-id xmlns="com-wordpress:feed-additions:1">42576</post-id><enclosure url="https://fedoramagazine.org/wp-content/uploads/2025/09/fl43b-300x127.jpg" length="10721" type="image/jpg" /> </item>
1736. <item>
1737. <title>Contribute at the Fedora Linux 43 i18n Test Week</title>
1738. <link>https://fedoramagazine.org/contribute-at-the-fedora-linux-43-i18n-test-week/</link>
1739. <comments>https://fedoramagazine.org/contribute-at-the-fedora-linux-43-i18n-test-week/#comments</comments>
1741. <dc:creator><![CDATA[Sumantro Mukherjee]]></dc:creator>
1742. <pubDate>Sun, 07 Sep 2025 21:45:27 +0000</pubDate>
1743. <category><![CDATA[Fedora Project community]]></category>
1744. <category><![CDATA[testing]]></category>
1745. <guid isPermaLink="false">https://fedoramagazine.org/?p=42536</guid>
1746.  
1747. <description><![CDATA[The i18n team is testing changes for Fedora Linux 43 (Use COLR for Noto Color Emoji, Set Default Monospace Fallback Font , and many more). As a result, the i18n and QA teams organized a test week to run from Tuesday, September 09, 2025, to Monday, September 15, 2025. The wiki page in this article [&#8230;]]]></description>
1748. <content:encoded><![CDATA[
1749. <p>The i18n team is testing changes for Fedora Linux 43 (<a href="https://fedoraproject.org/wiki/Changes/Use_COLR_for_Noto_Color_Emoji" target="_blank" rel="noreferrer noopener">Use COLR for Noto Color Emoji</a>,<a href="https://fedoraproject.org/wiki/Changes/SetDefaultMonospaceFallbackFont" target="_blank" rel="noreferrer noopener"> Set Default Monospace Fallback Font </a>, and many more). As a result, the i18n and QA teams organized a test week to run from <strong>Tuesday, September 09, 2025, </strong>to<strong> Monday, September 15, 2025</strong>. The wiki page in this article contains links to the test images you’ll need to participate. Please continue reading for details.</p>
1750.  
1751.  
1752.  
1753. <span id="more-42536"></span>
1754.  
1755.  
1756.  
1757. <h2 class="wp-block-heading"><strong>How does a test week work?</strong></h2>
1758.  
1759.  
1760.  
1761. <p>A test week is an event where anyone can help ensure changes in Fedora Linux work well in an upcoming release. Fedora community members often participate, and the public is welcome at these events. If you’ve never contributed before, this is a perfect way to get started.</p>
1762.  
1763.  
1764.  
1765. <p>To contribute, you only need to be able to do the following things:</p>
1766.  
1767.  
1768.  
1769. <ul class="wp-block-list">
1770. <li>Download test materials, which include some large files</li>
1771.  
1772.  
1773.  
1774. <li>Read and follow directions step by step</li>
1775. </ul>
1776.  
1777.  
1778.  
1779. <p>The <a href="https://fedoraproject.org/wiki/Test_Day:2025-09-09_I18N_Test_Day" target="_blank" rel="noreferrer noopener">wiki page</a> for the i18n test week is your source of information on what and how to test. After you’ve done some testing, you can log your results in the test week <a href="https://testdays.fedoraproject.org/testday/5" target="_blank" rel="noreferrer noopener">web application</a>. If you’re available on or around the days of the event, please do some testing and report your results.</p>
1780.  
1781.  
1782.  
1783. <p>Happy testing, and we hope to see you on one of the test days.</p>
1784.  
1785.  
1786.  
1787. <p></p>
1788. ]]></content:encoded>
1790. <wfw:commentRss>https://fedoramagazine.org/contribute-at-the-fedora-linux-43-i18n-test-week/feed/</wfw:commentRss>
1791. <slash:comments>3</slash:comments>
1794. <post-id xmlns="com-wordpress:feed-additions:1">42536</post-id><enclosure url="https://fedoramagazine.org/wp-content/uploads/2022/06/test-days-300x127.jpg" length="8214" type="image/jpg" /> </item>
1795. <item>
1796. <title>Tips and Tricks: man Command</title>
1797. <link>https://fedoramagazine.org/tips-and-tricks-man-command/</link>
1798. <comments>https://fedoramagazine.org/tips-and-tricks-man-command/#comments</comments>
1800. <dc:creator><![CDATA[abdulrahman mubarak]]></dc:creator>
1801. <pubDate>Mon, 11 Aug 2025 08:00:00 +0000</pubDate>
1802. <category><![CDATA[Fedora Project community]]></category>
1803. <guid isPermaLink="false">https://fedoramagazine.org/?p=42484</guid>
1804.  
1805. <description><![CDATA[The man command, is short for manual. It provides access to the various up-to-date on-board documentation pages. This helps users utilize the Linux/Unix operating systems in a better manner. What is man ? The man command is a manual pager which provides the user with documentation about specific functions, system calls, and commands. The man [&#8230;]]]></description>
1806. <content:encoded><![CDATA[
1807. <p>The <strong>man</strong> command, is short for <strong>manual</strong>. It provides access to the various up-to-date on-board documentation pages. This helps users utilize the Linux/Unix operating systems in a better manner.</p>
1808.  
1809.  
1810.  
1811. <span id="more-42484"></span>
1812.  
1813.  
1814.  
1815. <h2 class="wp-block-heading">What is man ?</h2>
1816.  
1817.  
1818.  
1819. <p>The <em>man</em> command is a manual pager which provides the user with documentation about specific functions, system calls, and commands. The <em>man</em> command uses the <em>less</em> pager by default. (See <em>man less</em> for more information.) </p>
1820.  
1821.  
1822.  
1823. <p>Note that a <strong>man</strong> page is likely to contain better up-to-date information compared to what can be found on the internet. It is wise to compare the <em>man</em> page usage and options with that found on the web.</p>
1824.  
1825.  
1826.  
1827. <h2 class="wp-block-heading">How to use man ?</h2>
1828.  
1829.  
1830.  
1831. <p>To use the <em>man</em> command effectively we have to know the <strong>manual pages system</strong>. The manual pages are distributed in 8 sections. Each provides documentation on particular topics.</p>
1832.  
1833.  
1834.  
1835. <h3 class="wp-block-heading">What are the manual page sections ?</h3>
1836.  
1837.  
1838.  
1839. <ol class="wp-block-list">
1840. <li>Programs, shell commands and daemons.</li>
1841.  
1842.  
1843.  
1844. <li>System calls.</li>
1845.  
1846.  
1847.  
1848. <li>Library calls.</li>
1849.  
1850.  
1851.  
1852. <li>Special files, drivers, and hardware.</li>
1853.  
1854.  
1855.  
1856. <li>Configuration files.</li>
1857.  
1858.  
1859.  
1860. <li>Games.</li>
1861.  
1862.  
1863.  
1864. <li>Miscellaneous commands.</li>
1865.  
1866.  
1867.  
1868. <li>System administration commands and daemons.</li>
1869. </ol>
1870.  
1871.  
1872.  
1873. <h2 class="wp-block-heading">Examples</h2>
1874.  
1875.  
1876.  
1877. <p>To get the printf library function documentation (section 3):</p>
1878.  
1879.  
1880.  
1881. <pre class="wp-block-preformatted"># man 3 printf</pre>
1882.  
1883.  
1884.  
1885. <p>To get the printf shell builtin documentation (section 1):</p>
1886.  
1887.  
1888.  
1889. <pre class="wp-block-preformatted"># man 1 printf</pre>
1890.  
1891.  
1892.  
1893. <p>You can learn more about the man command and its options:</p>
1894.  
1895.  
1896.  
1897. <pre class="wp-block-preformatted"># man man</pre>
1898.  
1899.  
1900.  
1901. <h2 class="wp-block-heading">How to manage the index caches database </h2>
1902.  
1903.  
1904.  
1905. <p>To update the existing database, or to create it, use the <strong>-c</strong> or <strong>&#8211;create</strong> flag  with the <em>mandb</em> command:</p>
1906.  
1907.  
1908.  
1909. <pre class="wp-block-preformatted"># mandb --create</pre>
1910.  
1911.  
1912.  
1913. <p>To do a correctness check on the documentation database use the <strong>-t</strong> or <strong>&#8211;test</strong> flag:</p>
1914.  
1915.  
1916.  
1917. <pre class="wp-block-preformatted"># mandb --test</pre>
1918.  
1919.  
1920.  
1921. <h2 class="wp-block-heading">How to export manual pages</h2>
1922.  
1923.  
1924.  
1925. <p>To export a man page, use the <strong>-t </strong>flag with the <em>man</em> command:</p>
1926.  
1927.  
1928.  
1929. <pre class="wp-block-preformatted">man -t 5 dnf.conf &gt; manual.ps  </pre>
1930.  
1931.  
1932.  
1933. <p>This will create a PostScript file with the contents of the dnf.conf man page from section 5.</p>
1934.  
1935.  
1936.  
1937. <p>Alternatively, if you want to output a PDF file, use something like this instead:</p>
1938.  
1939.  
1940.  
1941. <pre class="wp-block-preformatted">man -Tpdf 5 dnf.conf &gt; dnf.conf.pdf </pre>
1942.  
1943.  
1944.  
1945. <p>You will need the <kbd>groff-perl</kbd> package installed for this command to work.</p>
1946.  
1947.  
1948.  
1949. <h2 class="wp-block-heading">Summary</h2>
1950.  
1951.  
1952.  
1953. <p>The need to get information about <strong>commands</strong>, <strong>daemon</strong>s, <strong>shell builtins</strong>, etc. to make them do what they are intended to do correctly, motivates us to use the system manual to learn not everything but the required knowledge to reach our goal.</p>
1954.  
1955.  
1956.  
1957. <p></p>
1958.  
1959.  
1960.  
1961. <p></p>
1962. ]]></content:encoded>
1964. <wfw:commentRss>https://fedoramagazine.org/tips-and-tricks-man-command/feed/</wfw:commentRss>
1965. <slash:comments>17</slash:comments>
1968. <post-id xmlns="com-wordpress:feed-additions:1">42484</post-id><enclosure url="https://fedoramagazine.org/wp-content/uploads/2025/08/man_tips_tricks-300x127.jpg" length="15544" type="image/jpg" /> </item>
1969. <item>
1970. <title>Kernel 6.16 Test Week: August 10 &#8211; 16</title>
1971. <link>https://fedoramagazine.org/kernel-6-16-test-week-august-10-16/</link>
1973. <dc:creator><![CDATA[Aoife Moloney]]></dc:creator>
1974. <pubDate>Fri, 08 Aug 2025 08:00:00 +0000</pubDate>
1975. <category><![CDATA[Fedora Project community]]></category>
1976. <guid isPermaLink="false">https://fedoramagazine.org/?p=42407</guid>
1977.  
1978. <description><![CDATA[Join us to test the 6.16 kernel for Fedora Linux 43 during August 10 &#8211; 16! What is a test week? Test weeks are organised by the Fedora QA team per release cycle and are a great way to get involved in developing the upcoming Fedora Linux release. Instructions and test cases are provided for [&#8230;]]]></description>
1979. <content:encoded><![CDATA[
1980. <p>Join us to test the 6.16 kernel for Fedora Linux 43 during August 10 &#8211; 16!</p>
1981.  
1982.  
1983.  
1984. <h2 class="wp-block-heading">What is a test week?</h2>
1985.  
1986.  
1987.  
1988. <p>Test weeks are organised by the Fedora QA team per release cycle and are a great way to get involved in developing the upcoming Fedora Linux release. Instructions and test cases are provided for you, plus you will also be mentioned and thanked in the &#8216;<a href="https://communityblog.fedoraproject.org/heroes-of-fedora-fedora-40-contributions/" target="_blank" rel="noreferrer noopener">Heroes of Fedora</a>&#8216; blog at the end of the release. For more information on how to get involved, check out the <a href="https://fedoraproject.org/wiki/QA/Test_Days" target="_blank" rel="noreferrer noopener">Fedora Test Days wiki</a>, and to participate in the upcoming Kernel 6.16 test week, read on!</p>
1989.  
1990.  
1991.  
1992. <span id="more-42407"></span>
1993.  
1994.  
1995.  
1996. <h2 class="wp-block-heading">Kernel 6.16 Test Week</h2>
1997.  
1998.  
1999.  
2000. <p>The kernel team is working on final integration for Linux kernel 6.16. This recently released kernel version will arrive soon in Fedora Linux. As a result, the Fedora Linux kernel and QA teams have organized a test week from <strong>Sunday, August 10, 2025 </strong>to<strong> Saturday, August 16, 2025</strong>.</p>
2001.  
2002.  
2003.  
2004. <p>The <a href="https://fedoraproject.org/wiki/Test_Day:2025-08-10_Kernel_6.16_Test_Week">wiki page</a> contains links to the test images you’ll need to participate. The results can be submitted in the <a href="https://testdays.fedoraproject.org/testday/1" target="_blank" rel="noreferrer noopener">test day app</a>.</p>
2005.  
2006.  
2007.  
2008. <p>What are we looking for?</p>
2009.  
2010.  
2011.  
2012. <ul class="wp-block-list">
2013. <li>Regressions when rebasing</li>
2014.  
2015.  
2016.  
2017. <li>Issues when installing from USB on VM and/or bare metal systems (file under &#8216;exploratory)</li>
2018. </ul>
2019.  
2020.  
2021.  
2022. <h2 class="wp-block-heading">What do I need to do?</h2>
2023.  
2024.  
2025.  
2026. <p>To contribute, you only need to be able to do the following things:</p>
2027.  
2028.  
2029.  
2030. <ul class="wp-block-list">
2031. <li>Make sure you have a <a href="https://accounts.fedoraproject.org/" target="_blank" rel="noreferrer noopener">Fedora Account</a> (FAS)</li>
2032.  
2033.  
2034.  
2035. <li>Download test materials in advance where applicable, which may include some large files</li>
2036.  
2037.  
2038.  
2039. <li>Read and follow directions step by step in the <a href="https://fedoraproject.org/wiki/Test_Day:2025-08-10_Kernel_6.16_Test_Week" target="_blank" rel="noreferrer noopener">wiki test page</a></li>
2040.  
2041.  
2042.  
2043. <li>Report your findings in the <a href="https://testdays.fedoraproject.org/testday/1" target="_blank" rel="noreferrer noopener">app</a></li>
2044. </ul>
2045. ]]></content:encoded>
2049. <post-id xmlns="com-wordpress:feed-additions:1">42407</post-id><enclosure url="https://fedoramagazine.org/wp-content/uploads/2022/08/test-days-kernel-5.19-300x127.jpg" length="8214" type="image/jpg" /> </item>
2050. <item>
2051. <title>Anaconda Web UI Installer for Spins and Editions Test Days: August 4 &#8211; 8 2025</title>
2052. <link>https://fedoramagazine.org/anaconda-web-ui-installer-for-spins-and-editions-test-days-august-4-8-2025/</link>
2053. <comments>https://fedoramagazine.org/anaconda-web-ui-installer-for-spins-and-editions-test-days-august-4-8-2025/#comments</comments>
2055. <dc:creator><![CDATA[Aoife Moloney]]></dc:creator>
2056. <pubDate>Tue, 05 Aug 2025 15:07:55 +0000</pubDate>
2057. <category><![CDATA[Fedora Project community]]></category>
2058. <guid isPermaLink="false">https://fedoramagazine.org/?p=42450</guid>
2059.  
2060. <description><![CDATA[Join us this week for the Anaconda Web UI Installer test week where we are focusing testing on Anacondas brand new WebUI for KDE and Spins live images. What is a test week? Test weeks are organised by the Fedora QA team per release cycle and are a great way to get involved in developing [&#8230;]]]></description>
2061. <content:encoded><![CDATA[
2062. <p>Join us this week for the Anaconda Web UI Installer test week where we are focusing testing on Anacondas brand new WebUI for KDE and Spins live images. </p>
2063.  
2064.  
2065.  
2066. <h2 class="wp-block-heading">What is a test week?</h2>
2067.  
2068.  
2069.  
2070. <p>Test weeks are organised by the Fedora QA team per release cycle and are a great way to get involved in developing the upcoming Fedora Linux release. Instructions and test cases are provided for you, plus you will  be mentioned and thanked in the &#8216;<a href="https://communityblog.fedoraproject.org/heroes-of-fedora-fedora-40-contributions/" target="_blank" rel="noreferrer noopener">Heroes of Fedora</a>&#8216; blog at the end of the release. More information on how to get involved is located on the <a href="https://fedoraproject.org/wiki/QA/Test_Days" target="_blank" rel="noreferrer noopener">Fedora Test Days wiki</a>. To participate in the upcoming Kernel 6.16 test week, read on!</p>
2071.  
2072.  
2073.  
2074. <h2 class="wp-block-heading">Anaconda Web UI Installer Test Week</h2>
2075.  
2076.  
2077.  
2078. <p>The Anaconda WebUI became the default installer interface in the previous Fedora release for Fedora Workstation. This Test Day extends that effort to ensure the WebUI works smoothly across the broader Fedora ecosystem, especially in various Spin environments and Fedora KDE. As a result, the Anaconda and QA teams have organized a test week from <strong>Monday August 4, 2025 </strong>to<strong> Friday August 8, 2025</strong>.</p>
2079.  
2080.  
2081.  
2082. <p>The <a href="https://fedoraproject.org/wiki/Test_Day:2025-08-04_Anaconda_WebUI_for_Fedora_Spins_and_KDE" target="_blank" rel="noreferrer noopener">wiki page</a> contains links to the test images you’ll need to participate. The results can be submitted in the <a href="https://testdays.fedoraproject.org/testday/4" target="_blank" rel="noreferrer noopener">test day app</a>.</p>
2083.  
2084.  
2085.  
2086. <h2 class="wp-block-heading">What are we looking for?</h2>
2087.  
2088.  
2089.  
2090. <ul class="wp-block-list">
2091. <li>How partitioning is working</li>
2092.  
2093.  
2094.  
2095. <li>Cockpit Storage Editor performance</li>
2096.  
2097.  
2098.  
2099. <li>Internalisation</li>
2100.  
2101.  
2102.  
2103. <li>Issues not mentioned in the test cases &#8211; file those findings under &#8216;exploratory&#8217;.</li>
2104. </ul>
2105.  
2106.  
2107.  
2108. <h2 class="wp-block-heading">What do I need to do?</h2>
2109.  
2110.  
2111.  
2112. <p>To contribute, you only need to be able to do the following things:</p>
2113.  
2114.  
2115.  
2116. <ul class="wp-block-list">
2117. <li>Make sure you have a <a href="https://accounts.fedoraproject.org/" target="_blank" rel="noreferrer noopener">Fedora Account</a> (FAS)</li>
2118.  
2119.  
2120.  
2121. <li>Download test materials in advance where applicable, which may include some large files</li>
2122.  
2123.  
2124.  
2125. <li>Read and follow directions step by step in the <a href="https://fedoraproject.org/wiki/Test_Day:2025-08-04_Anaconda_WebUI_for_Fedora_Spins_and_KDE" target="_blank" rel="noreferrer noopener">wiki test page</a></li>
2126.  
2127.  
2128.  
2129. <li>Report your findings in the <a href="https://testdays.fedoraproject.org/testday/4">app</a></li>
2130. </ul>
2131.  
2132.  
2133.  
2134. <p>The Anaconda team are available in their matrix room <a href="https://matrix.to/#/#anaconda:fedora.im" target="_blank" rel="noreferrer noopener">https://matrix.to/#/#anaconda:fedora.im</a> to provide support to participating users.</p>
2135.  
2136.  
2137.  
2138. <p>Thank you for taking part in the testing of Fedora Linux 43!</p>
2139. ]]></content:encoded>
2141. <wfw:commentRss>https://fedoramagazine.org/anaconda-web-ui-installer-for-spins-and-editions-test-days-august-4-8-2025/feed/</wfw:commentRss>
2142. <slash:comments>3</slash:comments>
2145. <post-id xmlns="com-wordpress:feed-additions:1">42450</post-id><enclosure url="https://fedoramagazine.org/wp-content/uploads/2022/06/test-days-300x127.jpg" length="8214" type="image/jpg" /> </item>
2146. <item>
2147. <title>Fedora for Architects: Open Source Tools for Architectural Design</title>
2148. <link>https://fedoramagazine.org/fedora-for-architects-open-source-tools-for-architectural-design/</link>
2149. <comments>https://fedoramagazine.org/fedora-for-architects-open-source-tools-for-architectural-design/#comments</comments>
2151. <dc:creator><![CDATA[Arman Arisman]]></dc:creator>
2152. <pubDate>Mon, 04 Aug 2025 08:00:00 +0000</pubDate>
2153. <category><![CDATA[Fedora Project community]]></category>
2154. <guid isPermaLink="false">https://fedoramagazine.org/?p=42396</guid>
2155.  
2156. <description><![CDATA[Why Fedora for Architects Architects depend on digital tools for every stage of design, from sketching to modelling and documentation. But many popular tools are expensive, closed-source, or limited to specific platforms. Fedora offers a fast, stable, and open environment for professional design work. With a growing ecosystem of free and open source software, architects [&#8230;]]]></description>
2157. <content:encoded><![CDATA[
2158. <h2 class="wp-block-heading">Why Fedora for Architects</h2>
2159.  
2160.  
2161.  
2162. <p>Architects depend on digital tools for every stage of design, from sketching to modelling and documentation. But many popular tools are expensive, closed-source, or limited to specific platforms.</p>
2163.  
2164.  
2165.  
2166. <p>Fedora offers a fast, stable, and open environment for professional design work. With a growing ecosystem of free and open source software, architects can build a complete work-flow on Fedora, without sacrificing capability or control.</p>
2167.  
2168.  
2169.  
2170. <p>As an architect, I’d like to introduce how we can use Fedora for architectural design.</p>
2171.  
2172.  
2173.  
2174. <h2 class="wp-block-heading">Fedora as Design Platform</h2>
2175.  
2176.  
2177.  
2178. <p>Fedora Workstation is a solid choice for creative professionals. It is fast, up to date, and well-supported on a wide range of hardware, including laptops commonly used in architecture, like ThinkPads.</p>
2179.  
2180.  
2181.  
2182. <p>Fedora gives you access to a wide selection of open source applications through <strong>DNF</strong>, <strong>Flatpak</strong>, and <strong>COPR</strong>. Whether you&#8217;re installing stable packages or testing the latest versions, Fedora’s software ecosystem is flexible and developer-friendly.</p>
2183.  
2184.  
2185.  
2186. <p>With Wayland by default, good pen tablet support, and modern graphics drivers, Fedora handles demanding design tasks smoothly. It is a platform that gets out of the way, letting you focus on your ideas.</p>
2187.  
2188.  
2189.  
2190. <h2 class="wp-block-heading">Open Source Tools for Architectural Design</h2>
2191.  
2192.  
2193.  
2194. <p>Fedora supports a wide range of open source applications that can cover every stage of the architectural design process. From early sketching to 3D modelling, documentation, and even BIM. The following are some tools I use in practice.</p>
2195.  
2196.  
2197.  
2198. <h3 class="wp-block-heading">Sketching and Early Concepts</h3>
2199.  
2200.  
2201.  
2202. <p>Early-stage design relies on speed, intuition, and flexibility. On Fedora, you can use <strong>Krita</strong> for freehand sketching and expressive form exploration. Its brush engine and tablet support make it feel natural, especially when working through visual ideas. For quick annotations or tracing over site plans, <strong>Xournal++</strong> offers a fast and lightweight interface. When you need to build simple diagrams or zoning layouts, <strong>LibreOffice Draw</strong> lets you combine shapes and text easily. These tools support a fluid design process, helping you stay focused on ideas, not technical barriers.</p>
2203.  
2204.  
2205.  
2206. <h3 class="wp-block-heading">Drawing, Modelling, and Visualization</h3>
2207.  
2208.  
2209.  
2210. <p>As your design develops, modelling becomes a way to explore space, proportion, and materiality. On Fedora, <strong>Blender</strong> offers a robust environment for 3D modelling, rendering, and animation. You can build conceptual massing studies, detailed geometry, and even walk-throughs or camera animations to communicate spatial experience. Real-time rendering in Blender with the Eevee rendering engine and photo-realistic output using the Cycles rendering engine make it possible to move quickly from model to image or video.</p>
2211.  
2212.  
2213.  
2214. <figure class="wp-block-image size-large"><a href="https://fedoramagazine.org/wp-content/uploads/2025/07/blender.png"><img loading="lazy" decoding="async" width="1024" height="538" src="https://fedoramagazine.org/wp-content/uploads/2025/07/blender-1024x538.png" alt="Blender" class="wp-image-42435" srcset="https://fedoramagazine.org/wp-content/uploads/2025/07/blender-1024x538.png 1024w, https://fedoramagazine.org/wp-content/uploads/2025/07/blender-300x158.png 300w, https://fedoramagazine.org/wp-content/uploads/2025/07/blender-768x404.png 768w, https://fedoramagazine.org/wp-content/uploads/2025/07/blender-1536x807.png 1536w, https://fedoramagazine.org/wp-content/uploads/2025/07/blender-816x429.png 816w, https://fedoramagazine.org/wp-content/uploads/2025/07/blender.png 1920w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></a></figure>
2215.  
2216.  
2217.  
2218. <p>For precise 2D drafting, <strong>QCAD</strong> provides a clean and efficient workspace. It is useful for early layout studies, plans, and diagrams where clear lines matter more than complex parametrics.</p>
2219.  
2220.  
2221.  
2222. <figure class="wp-block-image size-large"><a href="https://fedoramagazine.org/wp-content/uploads/2025/07/qcad_3lXfSn2YlQ.png"><img loading="lazy" decoding="async" width="1024" height="633" src="https://fedoramagazine.org/wp-content/uploads/2025/07/qcad_3lXfSn2YlQ-1024x633.png" alt="QCAD" class="wp-image-42437" srcset="https://fedoramagazine.org/wp-content/uploads/2025/07/qcad_3lXfSn2YlQ-1024x633.png 1024w, https://fedoramagazine.org/wp-content/uploads/2025/07/qcad_3lXfSn2YlQ-300x185.png 300w, https://fedoramagazine.org/wp-content/uploads/2025/07/qcad_3lXfSn2YlQ-768x475.png 768w, https://fedoramagazine.org/wp-content/uploads/2025/07/qcad_3lXfSn2YlQ-1536x949.png 1536w, https://fedoramagazine.org/wp-content/uploads/2025/07/qcad_3lXfSn2YlQ-816x504.png 816w, https://fedoramagazine.org/wp-content/uploads/2025/07/qcad_3lXfSn2YlQ.png 1631w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></a></figure>
2223.  
2224.  
2225.  
2226. <p>These tools help you move from form to image — and from image to motion — using an entirely open work-flow in the open source ecosystem.</p>
2227.  
2228.  
2229.  
2230. <h3 class="wp-block-heading">Parametric and Algorithmic Design</h3>
2231.  
2232.  
2233.  
2234. <p>Parametric design lets you build geometry through rules and relationships — making form more flexible and responsive. While visual tools like Grasshopper aren’t natively available on Linux, <strong>Blender</strong> offers a few promising options.</p>
2235.  
2236.  
2237.  
2238. <p>The Geometry Nodes system in Blender supports procedural modelling based on attributes, modifiers, and data flows. For a more Grasshopper-like experience, the Sverchok add-on brings node-based parametric design into Blender — allowing you to create complex structures with visual logic. You can learn more about Sverchok at <a href="https://nortikin.github.io/sverchok/" target="_blank" rel="noreferrer noopener">https://nortikin.github.io/sverchok/</a></p>
2239.  
2240.  
2241.  
2242. <p>If you prefer scripting, Blender’s built-in Python API gives you full control for custom modelling and automation. While the ecosystem is still evolving, these tools offer a solid foundation for algorithmic thinking in open work-flows.</p>
2243.  
2244.  
2245.  
2246. <h3 class="wp-block-heading">Building Information Modelling (BIM)</h3>
2247.  
2248.  
2249.  
2250. <p>If you work with BIM, Fedora supports open source tools that follow open standards like IFC. <strong>FreeCAD</strong> includes an Arch workbench designed for architectural model modelling, with objects like walls, windows, and sections that carry semantic data. It also supports parametric editing and IFC export, making it suitable for early-stage modelling and coordination. You can learn more about FreeCAD BIM Workbench at <a href="https://wiki.freecad.org/BIM_Workbench/" target="_blank" rel="noreferrer noopener">https://wiki.freecad.org/BIM_Workbench/</a>.</p>
2251.  
2252.  
2253.  
2254. <figure class="wp-block-image size-full is-resized"><a href="https://fedoramagazine.org/wp-content/uploads/2025/07/Photos_zjjBCvB29J.png"><img loading="lazy" decoding="async" width="783" height="427" src="https://fedoramagazine.org/wp-content/uploads/2025/07/Photos_zjjBCvB29J.png" alt="FreeCAD BIM Workbench" class="wp-image-42439" style="width:840px;height:auto" srcset="https://fedoramagazine.org/wp-content/uploads/2025/07/Photos_zjjBCvB29J.png 783w, https://fedoramagazine.org/wp-content/uploads/2025/07/Photos_zjjBCvB29J-300x164.png 300w, https://fedoramagazine.org/wp-content/uploads/2025/07/Photos_zjjBCvB29J-768x419.png 768w" sizes="auto, (max-width: 783px) 100vw, 783px" /></a></figure>
2255.  
2256.  
2257.  
2258. <p>Bonsai, an add-on for Blender, brings IFC-based modelling and data editing into a powerful 3D environment. You can create, inspect, and modify BIM models directly in Blender, with full control over geometry and metadata — without relying on proprietary formats. You can learn more about Bonsai at <a href="https://bonsaibim.org/" target="_blank" rel="noreferrer noopener">https://bonsaibim.org/</a>.</p>
2259.  
2260.  
2261.  
2262. <figure class="wp-block-image size-large"><a href="https://fedoramagazine.org/wp-content/uploads/2025/07/banner-image2.png"><img loading="lazy" decoding="async" width="1024" height="563" src="https://fedoramagazine.org/wp-content/uploads/2025/07/banner-image2-1024x563.png" alt="" class="wp-image-42438" srcset="https://fedoramagazine.org/wp-content/uploads/2025/07/banner-image2-1024x563.png 1024w, https://fedoramagazine.org/wp-content/uploads/2025/07/banner-image2-300x165.png 300w, https://fedoramagazine.org/wp-content/uploads/2025/07/banner-image2-768x422.png 768w, https://fedoramagazine.org/wp-content/uploads/2025/07/banner-image2-1536x844.png 1536w, https://fedoramagazine.org/wp-content/uploads/2025/07/banner-image2-816x448.png 816w, https://fedoramagazine.org/wp-content/uploads/2025/07/banner-image2.png 1920w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></a></figure>
2263.  
2264.  
2265.  
2266. <p>While open source BIM is still evolving, these tools already offer meaningful work-flows for concept modelling, coordination, and documentation — all while staying aligned with open data standards.</p>
2267.  
2268.  
2269.  
2270. <h3 class="wp-block-heading">Graphic and Document Production</h3>
2271.  
2272.  
2273.  
2274. <p>Architectural work involves more than modelling — it also requires clear visuals and well-structured documents. On Fedora, tools like <strong>Inkscape</strong> and <strong>GIMP</strong> help you produce diagrams, edit renderings, or refine presentation materials with full control over layout and image quality.</p>
2275.  
2276.  
2277.  
2278. <figure class="wp-block-image size-large"><a href="https://fedoramagazine.org/wp-content/uploads/2025/07/gimp-3_egkzEoFYKU.jpg"><img loading="lazy" decoding="async" width="1024" height="538" src="https://fedoramagazine.org/wp-content/uploads/2025/07/gimp-3_egkzEoFYKU-1024x538.jpg" alt="GIMP" class="wp-image-42440" srcset="https://fedoramagazine.org/wp-content/uploads/2025/07/gimp-3_egkzEoFYKU-1024x538.jpg 1024w, https://fedoramagazine.org/wp-content/uploads/2025/07/gimp-3_egkzEoFYKU-300x158.jpg 300w, https://fedoramagazine.org/wp-content/uploads/2025/07/gimp-3_egkzEoFYKU-768x404.jpg 768w, https://fedoramagazine.org/wp-content/uploads/2025/07/gimp-3_egkzEoFYKU-1536x807.jpg 1536w, https://fedoramagazine.org/wp-content/uploads/2025/07/gimp-3_egkzEoFYKU-816x429.jpg 816w, https://fedoramagazine.org/wp-content/uploads/2025/07/gimp-3_egkzEoFYKU.jpg 1920w" sizes="auto, (max-width: 1024px) 100vw, 1024px" /></a></figure>
2279.  
2280.  
2281.  
2282. <p>For documentation, <strong>LibreOffice</strong> offers a reliable suite for writing specifications, reports, and schedules. If you prefer more control over formatting, <strong>LaTeX</strong> gives you a structured way to produce professional documents — especially when precision and consistency matter.</p>
2283.  
2284.  
2285.  
2286. <p>These tools help you communicate ideas clearly, whether for clients, collaborators, or construction teams.</p>
2287.  
2288.  
2289.  
2290. <h2 class="wp-block-heading">Fedora Tips for Architects</h2>
2291.  
2292.  
2293.  
2294. <h3 class="wp-block-heading">Flatpak vs DNF</h3>
2295.  
2296.  
2297.  
2298. <p>Many design tools are available through both Flatpak and DNF. Use Flatpak when you want easy access to the latest versions and isolated environments (e.g., graphics software), and DNF when you prefer tighter system integration and package control.</p>
2299.  
2300.  
2301.  
2302. <h3 class="wp-block-heading">Pen Tablet Setup</h3>
2303.  
2304.  
2305.  
2306. <p>Fedora detects most pen tablets automatically. You can configure pressure sensitivity, button mapping, and input area through GNOME Settings &gt; Devices &gt; Stylus, or use CLI tools like <em>xsetwacom</em> or <em>libinput</em> for advanced tweaks.</p>
2307.  
2308.  
2309.  
2310. <h3 class="wp-block-heading">Fonts and Typography</h3>
2311.  
2312.  
2313.  
2314. <p>Fedora provides a wide selection of high-quality free fonts through its repositories. You can install additional font packages using dnf, or manually place fonts in <em>~/.fonts/</em> for user-level use — useful when working on design boards or documents.</p>
2315.  
2316.  
2317.  
2318. <h3 class="wp-block-heading">Version Control with Git</h3>
2319.  
2320.  
2321.  
2322. <p>Even for design files, <strong>Git</strong> can help track changes and back up your work. Use it for versioning .blend, .svg, .fcstd, or even LaTeX files. For larger binaries, consider using Git LFS or structured folder snapshots.</p>
2323.  
2324.  
2325.  
2326. <h2 class="wp-block-heading">Conclusion</h2>
2327.  
2328.  
2329.  
2330. <p>Architecture is about more than form, it’s about intent, structure, and the systems that support them. The same applies to the tools we use. Choosing open source is not just about avoiding cost; it’s a decision to work with transparency, adaptability, and long-term agency.</p>
2331.  
2332.  
2333.  
2334. <p>Fedora offers a platform where design and freedom coexist, where architects can shape their tools as much as they shape space. It may not have every convenience out of the box, but it gives us something more enduring: control over our work-flow, and a community-driven path forward.</p>
2335.  
2336.  
2337.  
2338. <p>Designing openly is not always the easiest path, but it may be the most honest one.</p>
2339.  
2340.  
2341.  
2342. <p></p>
2343. ]]></content:encoded>
2345. <wfw:commentRss>https://fedoramagazine.org/fedora-for-architects-open-source-tools-for-architectural-design/feed/</wfw:commentRss>
2346. <slash:comments>16</slash:comments>
2349. <post-id xmlns="com-wordpress:feed-additions:1">42396</post-id><enclosure url="https://fedoramagazine.org/wp-content/uploads/2025/07/FedoraMagz-FedoraForArchitects-300x127.png" length="26296" type="image/jpg" /> </item>
2350. </channel>
2351. </rss>
2352.  

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

1. Download the "valid RSS" banner.

2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

3. Add this HTML to your page (change the image src attribute if necessary):

   <a href="http://www.feedvalidator.org/check.cgi?url=https%3A//fedoramagazine.org/feed/"><img src="valid-rss-rogers.png" alt="[Valid RSS]" title="Validate my RSS feed" /></a>

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=https%3A//fedoramagazine.org/feed/

Home · About · News · Docs · Terms