![\"A](\"https:\/\/sickgaming.net\/blog\/wp-content\/uploads\/2026\/02\/mrhbaan-syria-fedora-now-available-in-syria.png\")
<\/p>\n<\/p>\n
Mrhbaan, Fedora community! This article explains why this is happening now. It also covers the work behind the scenes to make this change happen.<\/p>\n <\/span> <\/p>\n You might wonder: what happened? Why is this happening now? I cannot answer everything in this post. However, the story begins in December 2024 with the fall of the Assad regime in Syria. A new government took control of the country. This began a new era of foreign policy in Syrian international relations.<\/p>\n Fast-forward to 18 December 2025. The United States signed the National Defense Authorization Act for Fiscal Year 2026<\/a> into law. This law repealed the 2019 Caesar Act sanctions<\/a>. This action removed Syria from the list of OFAC embargoed countries<\/a>. The U.S. Department of the Treasury maintains this list.<\/p>\n This may seem like a small change. Yet, it is significant for Syrians. Some U.S. Commerce Department regulations remain in place. However, the U.S. Department of the Treasury’s policy change now allows open source software availability in Syria. The Fedora Project updated its stance to welcome Syrians back into the Fedora community. This matches actions taken by other major platforms for open source software, such as Microsoft\u2019s GitHub<\/a>.<\/p>\n Opening the firewall to Syria took seconds. However, months of conversations and hidden work occurred behind the scenes to make this happen. The story begins with a ticket. Zaid Ballour (@devzaid<\/a>) opened Ticket #541<\/a> to the Fedora Council on 1 September 2025. This escalated the issue to the Fedora Council. It prompted a closer look at the changing political situation in Syria.<\/p>\n Jef Spaleta and I dug deeper into the issue. We wanted to understand the overall context. The United States repealed the 2019 Caesar Act sanctions in December 2025. This indicated that the Fedora Export Policy Control<\/a> might be outdated.<\/p>\n During this time, Jef and I spoke with legal experts at Red Hat and IBM. We reviewed the situation in Syria. This review process took time. We had to ensure compliance with all United States federal laws and sanctions. The situation for Fedora differs from other open source communities. Much of our development happens within infrastructure that we control. Additionally, Linux serves as digital infrastructure. This context differs from a random open source library on GitHub.<\/p>\n However, the path forward became clear after the repeal of the 2019 Caesar Act. After several months, we received approval. Fedora is accessible to Syrians once again.<\/p>\n Some folks may have noticed the Fedora Infrastructure ticket<\/a> last week. It requested the removal of the firewall block. We also submitted a Fedora Legal Docs Merge Request<\/a> to change the Fedora Export Control Policy<\/a>.<\/p>\n![\"\ud83d\udc4b\"](\"https:\/\/sickgaming.net\/blog\/wp-content\/uploads\/2026\/02\/mrhbaan-syria-fedora-now-available-in-syria-1.png\")
I am happy to share that as of 10 February 2026, Fedora is now available in Syria.<\/strong> Last week, the Fedora Infrastructure Team lifted the IP range block<\/a> on IP addresses in Syria. This action restores download access to Fedora Linux deliverables, such as ISOs. It also restores access from Syria to Fedora Linux RPM repositories, the Fedora Account System, and Fedora build systems. Users can now access the various applications and services that make up the Fedora Project. This change follows a recent update to the Fedora Export Control Policy<\/a>. Today, anyone connecting to the public Internet from Syria should once again be able to access Fedora.<\/p>\nWhy Syria, why now?<\/h2>\n
Syria & Fedora, behind the scenes<\/h2>\n
Opening the door to Syria<\/h3>\n