dChan - Q Origins Project Archive

Anonymous ID: f4807c June 4, 2026, 4:39 p.m. No.24679331 🗄️.is 🔗kun >>9351

Who wants to bet nothing happens and trump is full of shit again?

==DOD Officially Drops 180 Faiths From Military's Recognized Religion List

Defense Secretary Hegseth previously announced the change due to an "impractical" system.==

Department of Defense, for the first time in almost 10 years, has dramatically reduced its number of recognized religious faiths and belief systems by approximately 180.

The reforms mark the first time the list has been officially revised since a memo was issued March 27, 2017, decreasing the total number of faiths from roughly 211 to its new number of 31. The changes were iterated in a May 20, 2026, memorandum issued by the Under Secretary of War and signed by Anthony Tata, under secretary of defense for personnel and readiness of the United States, and obtained by Military.com.

This latest revision to the faith codes comes at the direction of Defense Secretary Pete Hegseth, according to the Tata-signed memo, done to “streamline the DoW collection of religious preferences collection for service members to enhance the delivery of targeted religious support from the Chaplaincy.” It calls for the previously instituted faith and belief codes to be revised within a 60-day period from the issuance of the memorandum.

“The new list will provide chaplains with clear, readily available information that will better enable them to anticipate the religious support needs of service members and to provide religious support activities that align with service members’ personal faith and practices,” Tata wrote.

He added that members will not be limited to the list of “religious affiliation codes” when selecting information for their dog tags. The revised list, according to documents obtained by Military.com, include Agnostics, Buddhists, Hindus, Islam (Muslims), Judaism, Sikh, and a wide range of Christian-based groups like Baptists, Catholics, Lutherans and Methodists.

This restructuring of faith codes, which help identity service members as well as the military in planning for appropriated religious coverage to include them, has now excluded minority faith/worldview groups including Atheists, Asatru, Deists, Druids, Eckankar, Heathens, Humanists, Magick, New Age churches, Pagan, Rosicrucianism, Shaman, Spiritualists, Troth, Unitarian Universalists and various Wiccans.

AP26147613403197

President Donald Trump speaks during a Cabinet meeting at the White House, Wednesday, May 27, 2026, in Washington, as Secretary of Defense Pete Hegseth, looks on. (AP Photo/Jacquelyn Martin)

It represents a stark change from the memo administered in 2017, during President Donald Trump’s first term. The Armed Forces Chaplains Board at the time endorsed a faith and belief code expansion “to standardize and better identify religious preferences recognized by the military services.”

That change at the time was said to better expand religious planning for multiple reasons, including better tracking for more accurate demographic data, better planning for religious support for the force, and providing a better assessment of the capabilities and requirements of each military service’s chaplain’s corps.

"The previous system had ballooned to well over 200 faith codes. … It was impractical and unusable, and many codes were never used at all," Hegseth said in March, adding that 82% of members who identify as religious use only six of the codes.

The secretary added that chaplains "are first and foremost called and ordained by God."

'Not the American Way'

A former U.S. Army chaplain who now serves as an endorser told Military.com the revised list is “horrible.”

https://www.military.com/dod-officially-drops-180-faiths-from-militarys-recognized-religion-list

NHS warns staff to 'prepare for Ebola outbreak in the UK' as eye-bleeding disease kills hundreds in Africa: 'Stock up on PPE and isolate patients ASAP'

NHS staff have been told to prepare for potential Ebola cases reaching the UK amid a fast-growing outbreak of the deadly virus in Africa.

In updated guidance, the UK Health Security Agency (UKHSA) has urged hospitals, GPs and frontline services to ensure they are ready to rapidly identify and isolate suspected patients, warning that while the risk to Britain remains low, imported cases are possible.

Healthcare providers have been instructed to check they have adequate supplies of personal protective equipment (PPE) and ensure staff are trained in its use, alongside clear protocols for managing suspected cases.

Clinicians are being reminded to consider Ebola in any patient who is acutely unwell with a fever and has travelled from affected regions within the past 21 days, reflecting the virus’s incubation period.

Under the guidance, suspected cases must be treated urgently, with patients isolated immediately in a single room and assessed by staff using appropriate protective measures.

Strict infection control procedures are required, and cases must be escalated rapidly to specialist public health teams, as Ebola is a notifiable disease in the UK.

The warning comes as an outbreak of the rare Bundibugyo strain of Ebola continues to spread in the Democratic Republic of the Congo (DRC) and neighbouring Uganda, after being declared a Public Health Emergency of International Concern by the World Health Organisation in May.

The latest figures suggest there have been hundreds of suspected cases and dozens of confirmed deaths, with numbers continuing to rise as testing and surveillance improve.

https://www.dailymail.com/health/article-15873619/NHS-staff-prepare-Ebola-outbreak-UK-Africa.html

New HTTP/2 Bomb DoS Attack Hits Nginx, Apache, IIS, Envoy, and Pingora

A new HTTP/2 Bomb DoS attack can exhaust memory on major web servers, causing denial-of-service in seconds.

A newly disclosed denial-of-service attack called HTTP/2 Bomb affects several major web servers and HTTP/2 implementations, including Nginx, Apache HTTP Server, Microsoft IIS, Envoy, and Cloudflare Pingora.

Calif researchers published this issue, describing it as a remote attack targeting default HTTP/2 configurations. In contrast to traditional denial-of-service attacks, HTTP/2 Bomb uses standard protocol behavior to force servers to allocate and retain large amounts of memory.

The attack uses two techniques. First, it exploits HPACK, HTTP/2’s header compression, by sending small indexed header references that expand into much larger server-side allocations. Second, it leverages HTTP/2 flow control to stall responses, preventing the server from releasing allocated memory.

This enables a client with limited bandwidth to consume significant RAM on a vulnerable server. According to the researchers, test results show Envoy 1.37.2 reached 32 GB of memory in 10 seconds, Apache httpd 2.4.67 in 18 seconds, Nginx 1.29.7 in 45 seconds, and Microsoft IIS on Windows Server 2025 reached 64 GB in 45 seconds.

Researchers also note the issue is not just decoded header size. Many defenses limit total decoded header size, but this attack exploits numerous small header fields, where memory usage results from per-header bookkeeping and server-side processing rather than payload size.

Cookie handling additionally contributes to the issue in some implementations. HTTP/2 permits splitting Cookie headers into separate fields, and in affected cases, these were not properly counted against request field limits. This allowed attackers to create many header objects while staying under expected protection thresholds.

The Apache httpd issue is tracked as CVE-2026-49975. A fix is available in mod_http2 2.0.41, where cookie headers are counted against LimitRequestFields. The fix is also present in httpd trunk, though it was not yet part of a 2.4.x release at the time of the disclosure.

Nginx resolved the issue in version 1.29.8 by introducing the max_headers directive, defaulting to 1000. Administrators unable to upgrade should temporarily disable HTTP/2 using http2 off;.

For Apache httpd deployments unable to upgrade to the fixed mod_http2 release, the recommended mitigation is to disable HTTP/2 by setting Protocols http/1.1. Lowering LimitRequestFieldSize may also reduce the impact for each stream, but this is only a partial mitigation since the attack can be multiplied across streams and connections.

For Microsoft IIS, Envoy, and Cloudflare Pingora, no confirmed patch was available at the time of disclosure. Calif later reported that Envoy released patches on June 3, though validation remained ongoing. Where no fix is available, administrators should disable HTTP/2 or use a component that enforces a strict header-count limit per request.

Administrators of public-facing HTTP/2 services should assess whether their stack is affected, apply available updates ASAP, and ensure that request header count limits are enforced. If immediate action is not possible, disabling HTTP/2 is the safest temporary mitigation.

https://linuxiac.com/new-http-2-bomb-dos-attack-hits-nginx-apache-iis-envoy-and-pingora/

>>24679369

Shirly is a mossad puppet

Mossad Sent Arms Seized From Hamas And Hezbollah To Kurdish Militias In Iran

The Israeli Mossad spy agency armed Kurdish militias in Iraq with weapons and ammunition seized from Hamas and Hezbollah as part of a plot to topple the Iranian government, journalist Amit Segal revealed in a report to Israel’s Yisrael Hayom on June 5.

The United States’ Central Intelligence Agency, CIA, was also actively involved in the plot , but it was later canceled by President Donald Trump due to pressure from Turkish President Recep Tayyip Erdogan.

The Kurdish militias received financial support and vehicles, and were equipped with small arms, anti-tank missiles, grenades, and mortar shells seized from Hamas and Hezbollah during the wars in Gaza and Lebanon. The plot was aimed at bringing down the Iranian government.

Segal’s report described the plan as a “bold operation” centered on a large-scale Kurdish incursion from Iraq into Iran. The plan included liberating Kurdish regions, advancing eastward, and sparking additional uprisings across the country.

Israel even began striking Islamic Revolutionary Guard Corps bases near the border to prepare the ground for the operation.

Nevertheless, the plot was halted at the last moment when Trump received an angry phone call from Erdogan, who strongly opposes any Kurdish empowerment in the region. In the wake of the call, the plan was called off.

“It’s ironic that weapons that Iran funded were almost used against it, and maybe still will be,” Segal wrote.

Last March, the Turkish newspaper Daily Sabah, which is affiliated with the Turkish government, reported that Ankara had succeeded in thwarting an Israeli plot to recruit Kurdish militants as a ground force in the war against Iran.

The Islamic Republic has warned against such a move, and has been launching strikes against Kurdish militants in Iraq on a regular basis ever since.

While the latest report suggests that the U.S. didn’t go on with the plot because of Turkey’s objection, the truth is that the plan put together by Mossad and CIA was never actually going to work.

Iranian Kurdish militia groups are deeply fractured with differing ideologies, and competing agendas. Adding to this the fact that while Iran, despite facing pressure from American and Israeli strikes at the time, its regular and reserve ground forces, numbered in the millions, were completely free to quickly attack and crush any uprising. A few thousand Kurdish militants would have had little, if no hope of succeeding.

https://southfront.press/mossad-sent-arms-seized-from-hamas-and-hezbollah-to-kurdish-militias-in-iran/