The Navajo witch purge refers to a significant event in Navajo history that occurred in the mid-1800s. This event was characterized by the Navajo people taking strong measures to rid their community of witches or "skinwalkers," who were believed to possess dark powers and bring harm to others. In Navajo culture, a witch is considered an individual who has the ability to shape-shift into various animal forms and manipulate supernatural forces for nefarious purposes. These witches, known as "skinwalkers," were highly feared and thought to be responsible for many misfortunes and illnesses within the community. During the Navajo witch purge, tribal leaders and medicine men came together to identify and eliminate those suspected of practicing witchcraft. This was done through extensive investigations, consultations with tribal spiritual leaders, and the performance of cleansing ceremonies.
So going from no CSP, to adding Flask's default, to removing Flask's default leaves you exactly where you were in the beginning! You have not worsened your security posture. So in that sense yes it's "safe", in that you haven't weakened your security position. You just haven't improved it, and Flask Talisman adds security options. Presumably you're using Flask Talisman's for its other security features otherwise why install it if you're just gonna turn it all off?) that's still a security improvement. But yes it would be better if you could use CSP too for the best protection it can offer (depending on the exact CSP you set).
However, plenty of skills don t care about this, like tool proficiency checks thieves tools especially , physical challenges, or even mental skills like investigation and perception where you know you re going to need to make the check. Even if a character is already proficient in the weapon they want to use, it s impossible to know when or if your DM will award a magic weapon and you can use it.
This was done through extensive investigations, consultations with tribal spiritual leaders, and the performance of cleansing ceremonies. When a suspected witch was identified, the community would gather in a hogan (traditional Navajo dwelling) for a ceremony known as a "sing." These sings were intended to bring healing and protection to the community, but in the case of a witch purge, they were used to expose and neutralize the witch.
Is there a way to remove content_security_policy to none with Talisman?
I was asked below if this was "safe", and have more to say on this than can add in a comment, so thought I'd edit my answer to address that.
Content Security Policy (CSP) is a very good additional security benefit - particularly to reduce the impact of Cross Site Scripting vulnerabilities on a site.
However it can be complicated to set up properly, and if not set properly it will stop stuff loading on your site (that's the entire intent of it!).
By default you get no CSP - it is something you need to explicitly add to your server to benefit from it.
However, adding a library like Flask Talisman changes that and gives you a default CSP - and quite a strict one at that be default (basically only load content from your site and don't allow Google Fonts for example, and no inline styles/scripts).
So going from no CSP, to adding Flask's default, to removing Flask's default leaves you exactly where you were in the beginning! You have not worsened your security posture. So in that sense yes it's "safe", in that you haven't weakened your security position. You just haven't improved it, and Flask Talisman adds security options. Presumably you're using Flask Talisman's for its other security features otherwise why install it if you're just gonna turn it all off?) that's still a security improvement. But yes it would be better if you could use CSP too for the best protection it can offer (depending on the exact CSP you set).
Of course if you had a good CSP configured in Flask and it was working find, and then you added some changes and it doesn't work, and you disable the whole CSP rather than alter it to cope with your changes then you ARE reducing your security. But I was assuming from the question that they haven't configured a CSP, and the explicit question in the title was asking how to turn it off.
Should Flask Talisman default a (very strict) CSP? That's a good question. Personally I think yes. It's a security library with the explicit intent to set security headers and CSP is a security header. So to me it should have good defaults, that can then be configured if you aren't ready for that protection yet. An alternative would be to have either no CSP (to make it entirely optional) or a weaker CSP (e.g. to allow upgrade-insecure-requests which is a good starter CSP). But I think it's better to have it on by default so people can learn about CSP and then consider setting it properly, or explicitly turning it off if they don't want to do that yet.
During the sing, chants, prayers, and the burning of specific herbs and resins were performed to ward off the dark powers of the witch. Sometimes, a medicine man or spiritual leader would be called upon to confront the accused witch directly in a process known as the "evil way ceremony." The evil way ceremony involved the medicine man performing specific rituals and prayers that were believed to strip the accused witch of their dark powers. This was often a highly intense and emotionally charged process, with the accused witch being confronted with evidence and accusations collected during the investigation. After the evil way ceremony, the accused witch would either be deemed innocent and allowed to rejoin the community or, if found guilty, subjected to additional rituals intended to prevent them from further harming others. These rituals usually involved restraining the witch's abilities and sealing off their powers. The Navajo witch purge was a deeply ingrained cultural response to the perceived threat posed by witches within the community. It represented a collective effort to safeguard the well-being and harmony of the Navajo people by eliminating those believed to be practicing harmful and malevolent witchcraft. Today, the belief in witches and skinwalkers remains a part of Navajo culture, although the witch purge itself is not as prevalent as it once was..
Reviews for "Traditional Navajo Rituals: Insights into the Witch Purge"
1. Jenna - 1 star
"Navajo Witch Purge was a complete disappointment. The storyline had potential but fell flat due to poor execution. The characters lacked depth and the dialogue was forced and unconvincing. The special effects were also incredibly subpar, making it difficult to immerse myself in the supposed horror of the film. Overall, it felt like a cheap attempt to cash in on the horror genre without putting in the effort to create a genuinely scary experience. I would not recommend wasting your time on this film."
2. Alex - 2 stars
"I had high hopes for Navajo Witch Purge, but it failed to deliver on multiple levels. The pacing of the movie was all over the place, with moments of slow and dull build-up followed by rushed and confusing action scenes. The cinematography also left much to be desired, with blurry and poorly framed shots that made it difficult to follow the events on screen. Additionally, the portrayal of Native American culture felt shallow and stereotypical, bordering on offensive. Overall, it was a disappointing and poorly executed attempt at horror."
3. Ryan - 2.5 stars
"I found Navajo Witch Purge to be mediocre at best. While the concept seemed intriguing, the execution was lacking. The film relied too heavily on jump scares, sacrificing genuine suspense and storytelling. The acting performances were average, with some moments feeling overacted and forced. The plot also had several plot holes that were never addressed, leaving the audience feeling unsatisfied and confused. Overall, Navajo Witch Purge was a forgettable horror film that failed to leave a lasting impression."