infra/tickets

Fork 0

Unblock Syrian IP address ranges from Fedora Infrastructure apps & services #13135

New issue

Closed

opened 2026-02-10 16:52:12 +00:00 by jflory7 · 4 comments

jflory7 commented

2026-02-10 16:52:12 +00:00

Summary

Unblock 🇸🇾 Syrian IP address ranges from all Fedora Infrastructure apps and services, given the recent change of status for Syrian sanctions and US export control regulations

Background

For the last several months, me and @jspaleta were investigating whether we could allow the Syrian people to access Fedora Infrastructure services, applications, and our various assets we produce as a Linux operating system community. Fortunately, we received great news that we can once again allow Fedora friends in Syria 🇸🇾 to access our infrastructure, applications, and services hosted inside the United States.

I am planning a public announcement on the Fedora Magazine to go along with this change. But I would like for the access to be lifted before publishing the Fedora Magazine post. So, once it goes out, all Syrians inside Syria will be able to connect immediately to Fedora apps and services, and hopefully any DNS or cache issues can be flushed out long before people start actually trying to connect.

Here is the verbatim email I received from Red Hat/IBM Legal:

Hi Justin,

Syria was removed from the list of OFAC embargoed countries (US Dept of Treasury). That means there are no issues with you using Fedora (an upstream open source/publicly available project) technology in Syria. However, Red Hat products such as RHEL cannot be exported to Syria still, due to US Commerce Dept regulations that are still in place. In other words, Fedora is a "project" not a product -- so you're OK there.

Let us know if you have any other questions.

Thank you,

Red Hat Export Compliance Team
IBM Risk, Compliance, and Integrity

Details

I am not sure about the technical work that actually needs to be done to enable this. However, the IP ranges associated with the Syrian Arab Republic are not that difficult to find online.

Somehow, we need to allow incoming traffic from these IP ranges across all of our infrastructure.

Outcome

Anyone connecting to the public Internet from Syria will be able to access Fedora Project websites, applications, and services, and also download Fedora Linux ISOs, packages, and access our repositories

# Summary Unblock 🇸🇾 Syrian IP address ranges from all Fedora Infrastructure apps and services, given the recent change of status for Syrian sanctions and US export control regulations # Background For the last several months, me and @jspaleta were investigating whether we could allow the Syrian people to access Fedora Infrastructure services, applications, and our various assets we produce as a Linux operating system community. Fortunately, we received great news that we can once again allow Fedora friends in Syria 🇸🇾 to access our infrastructure, applications, and services hosted inside the United States. I am planning a public announcement on the Fedora Magazine to go along with this change. But I would like for the access to be lifted _before_ publishing the Fedora Magazine post. So, once it goes out, all Syrians inside Syria will be able to connect immediately to Fedora apps and services, and hopefully any DNS or cache issues can be flushed out long before people start actually trying to connect. Here is the verbatim email I received from Red Hat/IBM Legal: > Hi Justin, > > Syria was removed from the list of OFAC embargoed countries (US Dept of Treasury). That means there are no issues with you using Fedora (an upstream open source/publicly available project) technology in Syria. However, Red Hat products such as RHEL cannot be exported to Syria still, due to US Commerce Dept regulations that are still in place. In other words, Fedora is a "project" not a product -- so you're OK there. > > Let us know if you have any other questions. > > Thank you, > > Red Hat Export Compliance Team > IBM Risk, Compliance, and Integrity # Details I am not sure about the technical work that actually needs to be done to enable this. However, the [IP ranges associated with the Syrian Arab Republic](https://ipregistry.co/AS29256#ranges) are not that difficult to find online. Somehow, we need to allow incoming traffic from these IP ranges across all of our infrastructure. # Outcome Anyone connecting to the public Internet from Syria will be able to access Fedora Project websites, applications, and services, and also download Fedora Linux ISOs, packages, and access our repositories

👍 4

kevin added the

labels

2026-02-10 19:30:33 +00:00

kevin added this to the Sprint ( 2026-02-09 to 2026-02-22 ) project

2026-02-10 19:30:40 +00:00

kevin self-assigned this

2026-02-10 19:30:43 +00:00

kevin commented

2026-02-10 19:33:22 +00:00

Owner

This just requires a small change to our block script and deploying it.

I am doing so now...

This just requires a small change to our block script and deploying it. I am doing so now...

🎉 2

bilal-zero commented

2026-02-10 20:24:13 +00:00

One note that might not be totally related: Fedora Atomic will have some features such as toolbx broken as that depends on quay.io which is a RedHat product. Alternative registries should work fine.

kevin commented

2026-02-10 20:44:12 +00:00

Owner

Good point. registry.fedoraproject.org should work now too though (and it should have a full copy of all the quay.io content).

Anyhow, this is deployed. It may take a few hours before everything is set, but it should be all done.

Good point. registry.fedoraproject.org should work now too though (and it should have a full copy of all the quay.io content). Anyhow, this is deployed. It may take a few hours before everything is set, but it should be all done.

🚀 2

kevin closed this issue

2026-02-10 20:44:13 +00:00

jflory7 commented

2026-02-10 20:46:57 +00:00

Author

Amazing, that was so fast! Thanks @kevin! 🚀

We will give it a week or so to propagate, but I guess this means I need to get going on the Fedora Magazine announcement, fast! 😀

BTW, I made a Pull Request to the Fedora Export Control Policy doc on GitLab. Until this gets merged, it is better if we keep a bit quiet on this until it is merged, plus the Fedora Magazine announcement goes live.

Amazing, that was so fast! Thanks @kevin! 🚀 We will give it a week or so to propagate, but I guess this means I need to get going on the Fedora Magazine announcement, fast! 😀 BTW, [I made a Pull Request](https://gitlab.com/fedora/legal/fedora-legal-docs/-/merge_requests/348) to the Fedora Export Control Policy doc on GitLab. Until this gets merged, it is better if we keep a bit quiet on this until it is merged, plus the Fedora Magazine announcement goes live.

❤️ 1