Introducing Cloudflare for Unified Risk Posture

Post Syndicated from James Chang original https://blog.cloudflare.com/unified-risk-posture


Managing risk posture — how your business assesses, prioritizes, and mitigates risks — has never been easy. But as attack surfaces continue to expand rapidly, doing that job has become increasingly complex and inefficient. (One global survey found that SOC team members spend, on average, one-third of their workday on incidents that pose no threat).  

But what if you could mitigate risk with less effort and less noise?

This post explores how Cloudflare can help customers do that, thanks to a new suite that converges capabilities across our Secure Access Services Edge (SASE) and web application and API (WAAP) security portfolios. We’ll explain:

  • Why this approach helps protect more of your attack surface, while also reducing SecOps effort
  • Three key use cases — including enforcing Zero Trust with our expanded CrowdStrike partnership
  • Other new projects we’re exploring based on these capabilities

Cloudflare for Unified Risk Posture

Today, we’re announcing Cloudflare for Unified Risk Posture, a new suite of cybersecurity risk management capabilities that can help enterprises with automated and dynamic risk posture enforcement across their expanding attack surface. Today, one unified platform enables organizations to:

  • Evaluate risk across people and applications: Cloudflare evaluates risk posed by people via user entity and behavior analytics (UEBA) models and risks to apps, APIs, and sites via malicious payload, zero-day threat, and bot detection models.
  • Exchange risk indicators with best-in-class partners: Cloudflare ingests risk scores from best-in-class endpoint protection (EPP) and identity provider (IDP) partners and shares telemetry back with security information and event management (SIEM) and extended detection and response (XDR) platforms for further analysis, all via one-time integrations with our unified API.
  • Enforce automated risk controls at scale: Based on these dynamic first- and third-party risk scores, Cloudflare enforces consistent risk controls for people and apps across any location around the world.

Figure 1: Unified Risk Posture Diagram

As mentioned above, this suite converges capabilities from our SASE and WAAP security portfolios onto our global network. Customers can now take advantage of built-in risk management functionality packaged as part of these existing portfolios.

This launch builds on our progressive efforts to extend first-party visibility and controls and third-party integrations that make it easier for organizations to adapt to evolving risks. For example, as part of the 2024 Security Week, we announced the general availability of behavior-based user risk scoring and the beta availability of an AI-enabled assistant to help you analyze risks facing your applications. And in a recent integration in the Fall of 2023, we announced that our cloud email security customers can ingest and display our threat detections within the CrowdStrike Falcon® Next-Gen SIEM dashboard.

To further manage your risk posture, you will be able to take advantage of new Cloudflare capabilities and integrations, including:

  • A new integration to share Cloudflare Zero Trust and email log data with the CrowdStrike Falcon Next-Gen SIEM (available now)
  • A new integration to share Cloudflare’s user risk score with Okta to enforce access policies (coming by the end of Q2 2024)
  • New first-party UEBA models, including user risk scores based on device posture checks (coming by the end of Q2 2024)

Unifying the evaluation, exchange, and enforcement stages of risk management onto Cloudflare’s platform helps security leaders mitigate risk with less effort. As a cybersecurity vendor defending both public-facing and internal infrastructure, Cloudflare is uniquely positioned to protect wide swathes of your expanding attack surface. Bringing together dynamic first-party risk scoring, flexible integrations, and automated enforcement helps drive two primary business outcomes:

  1. Reducing effort in SecOps with less manual policy building and greater agility in responding to incidents. This means fewer clicks to build policies, more automated workflows, and lower mean times to detect (MTTD) and mean times to respond (MTTR) to incidents.
  2. Reducing cyber risk with visibility and controls that span people and apps. This means fewer critical incidents and more threats blocked automatically.

Customers like Indeed, the #1 job site in the world, are already seeing these impacts by partnering with Cloudflare:

“Cloudflare is helping us mitigate risk more effectively with less effort and simplifies how we deliver Zero Trust across my organization.”
— Anthony Moisant, SVP, Chief Information Officer and Chief Security Officer at Indeed.

Problem: Too many risks across too much attack surface

Managing risk posture is an inherently broad challenge, covering internal dangers and external threats across attack vectors. Below is just a sampling of risk factors CISOs and their security teams track across three everyday dimensions including people, apps, and data:

  • People risks: Phishing, social engineering, malware, ransomware, remote access, insider threats, physical access compromise, third party / supply chain, mobile devices / BYOD
  • App risks: denial of service, zero-day exploits, SQL injection, cross-site scripting, remote code execution, credential stuffing, account takeover, shadow IT usage, API abuse
  • Data risks: data loss / exposure, data theft / breach, privacy violation, compliance violation, data tampering

Point solutions emerged to lock down some of these specific risks and attack vectors. But over time, organizations have accumulated many services with a limited ability to talk to one another and build a more holistic view of risk. The granular telemetry generated by each tool has led to information overload for security staff who are often stretched thin already. Security Information and Event Management (SIEM) and Extended Detection & Response (XDR) platforms play a critical role in aggregating risk data across environments and mitigating threats based on analysis, but these tools still demand time, resources, and expertise to operate effectively. All these challenges have gotten worse as attack surfaces have expanded rapidly, as businesses embrace hybrid work, build new digital apps, and more recently, experiment with AI.

How Cloudflare helps manage risk posture

To help restore control over this complexity, Cloudflare for Unified Risk Posture provides one platform to evaluate risk, exchange indicators, and enforce dynamic controls throughout IT environments and around the world, all while complementing the security tools your business already relies on.

Although the specific risks Cloudflare can mitigate are wide-ranging (including all those in the sample bullets above), the following three use cases represent the full range of our capabilities, which you can start taking advantage of today.

Use Case #1: Enforce Zero Trust with Cloudflare & CrowdStrike

This first use case spotlights the flexibility with which Cloudflare fits into your current security ecosystem to make it easier to adopt Zero Trust best practices.

Cloudflare integrates with and ingests security signals from best-in-class EPP and IDP partners to enforce identity and device posture checks for any access request to any destination. You can even onboard multiple providers at once to enforce different policies in different contexts. For example, by integrating with CrowdStrike Falcon®, joint customers can enforce policies based on the Falcon Zero Trust Assessment (ZTA) score, which delivers continuous real-time security posture assessments across all endpoints in an organization regardless of the location, network or user. Plus, customers can then push activity logs generated by Cloudflare, including all access requests, to whichever cloud storage or analytics providers they prefer.

Today, we are announcing an expanded partnership with CrowdStrike for a new integration that enables organizations to share logs with Falcon Next-Gen SIEM for deeper analysis and further investigation. Falcon Next-Gen SIEM unifies first- and third-party data, native threat intelligence, AI, and workflow automation to drive SOC transformation and enforce better threat protection. The integration of Cloudflare Zero Trust and email logs with Falcon Next-Gen SIEM allows joint customers to identify and investigate Zero Trust networking and email risks and analyze data with other log sources to uncover hidden threats.

“CrowdStrike Falcon Next-Gen SIEM delivers up to 150x faster search performance over legacy SIEMs and products positioned as SIEM alternatives. Our transformative telemetry, paired with Cloudflare’s robust Zero Trust capabilities provides an unprecedented partnership. Together, we are converging two of the most critical pieces of the risk management puzzle that organizations of every size must address in order to combat today’s growing threats.”
— Daniel Bernard, Chief Business Officer at CrowdStrike

Below is a sample workflow of how Cloudflare and CrowdStrike work together to enforce Zero Trust policies and mitigate emerging risks. Together, Cloudflare and CrowdStrike complement each other by exchanging activity and risk data and enforcing risk-based policies and remediation steps.

Figure 2: Enforce Zero Trust with Cloudflare & CrowdStrike

Phase 1: Automated investigation

Phase 2: Zero Trust enforcement

Phase 3: Remediation

Cloudflare and CrowdStrike help an organization detect that a user is compromised.

In this example, Cloudflare has recently blocked web browsing to risky websites and phishing emails, serving as the first line of defense. Those logs are then sent to CrowdStrike Falcon Next-Gen SIEM, which alerts your organization’s analyst about suspicious activity.

At the same time, CrowdStrike Falcon Insight XDR automatically scans that user’s device and detects that it is infected. As a result, the Falcon ZTA score reflecting the device’s health is lowered.

This org has set up device posture checks via Cloudflare’s Zero Trust Network Access (ZTNA), only allowing access when the Falcon ZTA risk score is above a specific threshold they have defined. 

Our ZTNA denies the user’s next request to access an application because the Falcon ZTA score falls below that threshold.

Because of this failed device posture check, Cloudflare increases the risk score for that user, which places them in a group with more restrictive controls. 

In parallel, CrowdStrike’s Next-GenSIEM has continued to analyze the specific user’s activity and broader risks throughout the organization’s environment. Using machine learning models, CrowdStrike surfaces top risks and proposes solutions for each risk to your analyst.

The analyst can then review and select remediation tactics — for example, quarantining the user’s device — to further reduce risk throughout the organization. 

Use Case #2: Protect apps, APIs, & websites

This next use case is focused on protecting apps, APIs, and websites from threat actors and bots. Many customers first adopt Cloudflare for this use case, but may not be aware of the risk evaluation algorithms underpinning their protection.

Figure 3: Protect apps, APIs & sites with ML-backed threat intelligence

Cloudflare’s Application Services detect and mitigate malicious payloads and bots using risk models backed by machine learning (ML) including:

These risk models are trained largely on telemetry from Cloudflare’s global network, which is used as a reverse proxy by nearly 20% of all websites and sees about 3 trillion DNS queries per day. This unique real-time visibility powers threat intelligence and even enables us to detect and mitigate zero-days before others.

Cloudflare also uses ML to discover new API endpoints and schemas without requiring any prerequisite customer input. This helps organizations uncover unauthenticated APIs and map their growing attack surface before applying protections.

Unlike other vendors, Cloudflare’s network architecture enables risk evaluation models and security controls on public-facing and internal infrastructure to be shared across all of our services. This means that organizations can apply protections against app vulnerability exploits, DDoS, and bots in front of internal apps like self-hosted Jira and Confluence servers, protecting them from emerging and even zero-day threats.

Organizations can review the potential misconfigurations, data leakage risks, and vulnerabilities that impact the risk posture for their apps, APIs, and websites within Cloudflare Security Center. We are investing in this centralized view of risk posture management by integrating alerts and insights across our security portfolio. In fact, we recently announced updates focused on highlighting where gaps exist in how your organization has deployed Cloudflare services.

Finally, we are also making it easier for organizations to investigate security events directly and recently announced beta availability of Log Explorer. In this beta, security teams can view all of their HTTP traffic in one place with search, analytics dashboards, and filters built-in. These capabilities can help customers monitor more risk factors within the Cloudflare platform versus exporting to third party tools.

Use Case #3: Protect sensitive data with UEBA

This third use case summarizes one common way many customers plan to leverage our user risk / UEBA scores to prevent leaks and mishandling of sensitive data:

Figure 4: Protect apps, APIs & sites with ML-backed threat intelligence

  • Phase 1: In this example, the security team has already configured data loss prevention (DLP) policies to detect and block traffic with sensitive data. These policies prevent one user’s multiple, repeated attempts to upload source code to a public GitHub repository.
  • Phase 2: Because this user has now violated a high number of DLP policies within a short time frame, Cloudflare scores that suspicious user as high risk, regardless of whether those uploads had malicious or benign intent. The security team can now further investigate that specific user, including reviewing all of his recent log activity.
  • Phase 3: For that specific high-risk user or for a group of high-risk users, administrators can then set ZTNA or even browser isolation rules to block or isolate access to applications that contain other sensitive data.

Altogether, this workflow highlights how Cloudflare’s risk posture controls adapt to suspicious behavior from evaluation through to enforcement.

How to get started with unified risk posture management

The above use cases reflect how our customers are unifying risk management with Cloudflare. Through these customer conversations, a few themes emerged for why they feel confident in our vision to help them manage risk across their expanding attack surface:

  • The simplicity of our unified platform: We bring together SASE and WAAP risk scoring and controls for people and apps. Plus, with a single API for all Cloudflare services, organizations can automate and customize workflows with infrastructure-as-code tools like Terraform with ease.
  • The flexibility of our integrations: We exchange risk signals with the EPP, IDP, XDR, and SIEM providers you already use, so you can do more with your tools and data. Plus, with one-time integrations that work across all our services, you can extend controls across your IT environments with agility.
  • The scale of our global network: Every security service is available for customers to run in every location across our network spanning 320+ locations and 13K+ interconnects. In this way, single-pass inspection and risk policy enforcement is always fast, consistent, and resilient, delivered close to your users and apps.

If you’re ready to see how Cloudflare can help you manage risk, request a consultation today. Or if you’re at RSA Conference 2024, come to any of our in-person events.

To continue learning more about how Cloudflare can help you evaluate risk, exchange risk indicators, and enforce risk controls, explore more resources on our website.

Using Fortran on Cloudflare Workers

Post Syndicated from John Graham-Cumming original https://blog.cloudflare.com/using-fortran-on-cloudflare-workers


In April 2020, we blogged about how to get COBOL running on Cloudflare Workers by compiling to WebAssembly. The ecosystem around WebAssembly has grown significantly since then, and it has become a solid foundation for all types of projects, be they client-side or server-side.

As WebAssembly support has grown, more and more languages are able to compile to WebAssembly for execution on servers and in browsers. As Cloudflare Workers uses the V8 engine and supports WebAssembly natively, we’re able to support languages that compile to WebAssembly on the platform.

Recently, work on LLVM has enabled Fortran to compile to WebAssembly. So, today, we’re writing about running Fortran code on Cloudflare Workers.

Before we dive into how to do this, here’s a little demonstration of number recognition in Fortran. Draw a number from 0 to 9 and Fortran code running somewhere on Cloudflare’s network will predict the number you drew.

Try yourself on handwritten-digit-classifier.fortran.demos.cloudflare.com.

This is taken from the wonderful Fortran on WebAssembly post but instead of running client-side, the Fortran code is running on Cloudflare Workers. Read on to find out how you can use Fortran on Cloudflare Workers and how that demonstration works.

Wait, Fortran? No one uses that!

Not so fast! Or rather, actually pretty darn fast if you’re doing a lot of numerical programming or have scientific data to work with. Fortran (originally FORmula TRANslator) is very well suited for scientific workloads because of its native functionality for things like arithmetic and handling large arrays and matrices.

If you look at the ranking of the fastest supercomputers in the world you’ll discover that the measurement of “fast” is based on these supercomputers running a piece of software called LINPACK that was originally written in Fortran. LINPACK is designed to help with problems solvable using linear algebra.

The LINPACK benchmarks use LINPACK to solve an n x n system of linear equations using matrix operations and, in doing so, determine how fast supercomputers are. The code is available in Fortran, C and Java.

A related Fortran package, BLAS, also does linear algebra and forms the basis of the number identifying code above. But other Fortran packages are still relevant. Back in 2017, NASA ran a competition to make FUN3D (used to perform calculations of airflow over simulated aircraft). FUN3D is written in Fortran.

So, although Fortran (or at the time FORTRAN) first came to life in 1957, it’s alive and well and being used widely for scientific applications (there’s even Fortran for CUDA). One particular application left Earth 20 years after Fortran was born: Voyager. The Voyager probes use a combination of assembly language and Fortran to keep chugging along.

But back in our solar system, and back on Region: Earth, you can now use Fortran on Cloudflare Workers. Here’s how.

How to get your Fortran code running on Cloudflare Workers

To make it easy to run your Fortran code on Cloudflare Workers, we created a tool called Fortiche (translates to smart in French). It uses Flang and Emscripten under the hood.

Flang is a frontend in LLVM and, if you read the Fortran on WebAssembly blog post, we currently have to patch LLVM to work around a few issues.

Emscripten is used to compile LLVM output and produce code that is compatible with Cloudflare Workers.

This is all packaged in the Fortiche Docker image. Let’s see a simple example.

add.f90:

SUBROUTINE add(a, b, res)
    INTEGER, INTENT(IN) :: a, b
    INTEGER, INTENT(OUT) :: res

    res = a + b
END

Here we defined a subroutine called add that takes a and b, sums them together and places the result in res.

Compile with Fortiche:

docker run -v $PWD:/input -v $PWD/output:/output xtuc/fortiche --export-func=add add.f90

Passing --export-func=add to Fortiche makes the Fortran add subroutine available to JavaScript.

The output folder contains the compiled WebAssembly module and JavaScript from Emscripten, and a JavaScript endpoint generated by Fortiche:

$ ls -lh ./output
total 84K
-rw-r--r-- 1 root root 392 avril 22 12:00 index.mjs
-rw-r--r-- 1 root root 27K avril 22 12:00 out.mjs
-rwxr-xr-x 1 root root 49K avril 22 12:00 out.wasm

And finally the Cloudflare Worker:

// Import what Fortiche generated
import {load} from "../output/index.mjs"

export default {
    async fetch(request: Request): Promise<Response> {
        // Load the Fortran program
        const program = await load();

        // Allocate space in memory for the arguments and result
        const aPtr = program.malloc(4);
        const bPtr = program.malloc(4);
        const outPtr = program.malloc(4);

        // Set argument values
        program.HEAP32[aPtr / 4] = 123;
        program.HEAP32[bPtr / 4] = 321;

        // Run the Fortran add subroutine
        program.add(aPtr, bPtr, outPtr);

        // Read the result
        const res = program.HEAP32[outPtr / 4];

        // Free everything
        program.free(aPtr);
        program.free(bPtr);
        program.free(outPtr);

        return Response.json({ res });
    },
};

Interestingly, the values we pass to Fortran are all pointers, therefore we have to allocate space for each argument and result (the Fortran integer type is four bytes wide), and pass the pointers to the `add` subroutine.

Running the Worker gives us the right answer:

$ curl https://fortran-add.cfdemos.workers.dev

{"res":444}

You can find the full example here.

Handwritten digit classifier

This example is taken from https://gws.phd/posts/fortran_wasm/#mnist. It relies on the BLAS library, which is available in Fortiche with the flag: --with-BLAS-3-12-0.

Note that the LAPACK library is also available in Fortiche with the flag: --with-LAPACK-3-12-0.

You can try on https://handwritten-digit-classifier.fortran.demos.cloudflare.com and find the source code here.

Let us know what you write using Fortran and Cloudflare Workers!

Secure Randomness in Go 1.22 (Go Blog)

Post Syndicated from corbet original https://lwn.net/Articles/972680/

The Go Blog has a detailed
article
on the new, more secure random-number generator implemented for
the 1.22 release.

For example, when Go 1.20 deprecated math/rand’s Read, we heard
from developers who discovered (thanks to tooling pointing out use
of deprecated functionality) they had been using it in places where
crypto/rand’s Read was definitely needed, like generating key
material. Using Go 1.20, that mistake is a serious security problem
that merits a detailed investigation to understand the
damage. Where were the keys used? How were the keys exposed? Were
other random outputs exposed that might allow an attacker to derive
the keys? And so on. Using Go 1.22, that mistake is just a mistake.

За шарлатанските лечения и лишеите върху прогнилата каца на здравеопазването

Post Syndicated from Боян Юруков original https://yurukov.net/blog/2024/sharlatanski-lechecniq/

Виждате често кутии и кампании да събират пари за това или онова лечение. Често става въпрос за онкологични заболявания. Също нерядко обещаното изцерение от обикновено чуждестранна болница е чиста форма на шарлатанство. Убедиха ме наскоро да не се задълбавам вече в темата, но вчера нещо ми припомни за това и ме вбеси.

До мен стигна мейл, който видимо е от част от лобистка кампания за промяна на покритите от държавата процедури. При всичките проблеми в здравеопазването ни и особено в проследяването и лечението на онкологични заболявания, има натиск да стане не само приемливо, но и да се заплащат неща като „биоток“, „детокс“ на конкретни органи, свръхдози с витамин С и ред други без никакви доказателства за най-малкото благоприятен ефект.

Не, че ще доста от обещаните лечения в Турция Израел и т.н., за които се плащат баснословни суми срещу зрънце надежда за родители и роднини имат същата медицинска стойност. Нека гледаме обаче в своя си двор.

Лошото е, че подобни фалшиви лечения вече са много вървежни у нас – също както барокамерите дето уж „лекували“ аутизъм, хомеопатията срещу наследствени заболявания и стволови клетки за какво ли не. За всяко от тези съм виждал кутии, концерти, кампании и дарения от общински съвети и винаги се аргументират с вариация на твърдения за реакции от ваксини през лекарска немарливост или немощ на съществуващите методи за лечение.

Тези преуспяват във вакуума на управлението на здравната система, в който посредници на лекарства строят болници и диктуват закони и регулаторна политика, а шефове на болници мачкат почернени майки и си строят секс апартаменти с пари за лечение. Измамниците, за които говоря, са просто лишеите, които неизменно се развива върху една прогнила каца. Предупреждавам за тях и методите им от години, сега са просто по-видими.

Та затова се сетих вчера. А защо ме бяха убедили да не задълбавам? Заради другата важна част от уравнението – ние дарителите, които ни е грижа и искаме да помогнем в останалите случаи, когато не само има нужда, но и има реално лечение и шанс.

Но да видим дали министерството ще захвърли в коша ония лобизъм толкова бързо, колкото аз връчената ми завчера визитка на ортопед-хомеопат.

Иначе, писал съм преди доста за фонда за лечение на деца, данните за онкологичните заболявания в България и една от доказаните мерки за превенция на един от най-пагубните му форми у нас.

The post За шарлатанските лечения и лишеите върху прогнилата каца на здравеопазването first appeared on Блогът на Юруков.

2023 PSF annual impact report

Post Syndicated from jzb original https://lwn.net/Articles/972596/

The Python Software
Foundation
(PSF) has announced
its annual
impact report
for 2023. The report includes updates from PSF staff
as well as summaries of the foundation’s activities, financials, and
infrastructure. The PSF celebrated the
20th anniversary of PyCon US, distributed more than $370,000 in grants, and
enjoyed impressive traffic on PyPI:

In 2023 PyPI saw a 45% growth in download counts and bandwidth alike,
serving 603,378,275 downloads for the 516,402 projects hosted there
requiring 747.4 Petabytes of data transfer, or 189.6 Gbps of bandwidth
24x7x365.

See the full report for a breakdown of grant disbursements and
trends, PSF expenses, and high-level plans for the rest of 2024.

Stenberg: I survived curl up 2024

Post Syndicated from daroc original https://lwn.net/Articles/972603/

Daniel Stenberg has

posted a report
about the recent curl up conference about
curl development. It was held over two days in
Stockholm. The report has short summaries of the talks with links to the
recordings.

curl up is never a big meeting/conference but we have in the past
sometimes been around twenty-five attendees. This year’s amount of
fifteen was the smallest so far, but in this small set of people we
have a set of long-term well-known curl contributors. It is not a
big list of attendees that creates a good curl up.

И пак за свободата на словото

Post Syndicated from Григор original http://www.gatchev.info/blog/?p=2633

Напоследък често попадам на претенции на една определена категория хора, че свободата на словото им се нарушавала. Обикновено от сорта на „мръсните левичари ми забраняват да говоря каквото мисля и ми отнемат свободата на словото“. И обикновено след като някой им е обърнал внимание, че изказват директен и безсрамен расизъм, нацизъм, сексисъм или друго от сорта.

Реално никой не пречи на такива хора да говорят каквото си искат. (Иначе нямаше да могат да напишат изказването, заради което хленчат.) Проблемът им е, че когато почнат да бълват примерно расизъм, околните ги гледат като расисти – вече не като свестни и читави хора. Съответно те се чувстват дискриминирани („защо другите ги гледат като свестни и читави, а мен не?“) и опищяват света.

Реално това, срещу което протестират, е че се налага да търпят последствията на расизма си, или каквато друга простащина демонстрират. Искат хем да са демонстративни боклуци, хем да бъдат третирани като достойни хора. И когато не го получават, се тръшкат като оскърбени принцеси. (Talk about snowflakes.)

(Не, тази категория хора не са рашистките пропагандисти. Те също често демонстрират расизъм, нацизъм и сексизъм – чудесни начини за разделяне на обществото и сеене на омраза са. Но сами по себе си не са достатъчни за провеждане на рашистка пропаганда, така че пропагандистите рядко ги защищават изолирано. Обикновено се тръшкат за свобода на словото, когато някой оспори лъжите им. Защото някой им пречи да лъжат по принцип, а не защото някой им пречи да са расисти или нацисти.)

Тази категория хора обикновено наричат себе си „десни“ или „консерватори“. И двете са опит за мимикрия – те са всъщност нещо друго.

Ние сме свикнали с разделението между либерали, които дърпат напред, и консерватори, които отстояват наличното. Всяка от тези групи има своята важна роля в прогреса. Като двигателят и спирачките на кола са – без двигател тя няма да тръгне, без спирачки ще ви пребие някъде, безопасното придвижване се постига с имането и разумната употреба и на двете.

Има обаче и трета група – реакционери. Те се борят да върнат нещата назад, към „светлото минало“. Към времената на расизма, нацизма, неграмотността, мизерията, феодализма… Те търсят лековерни, за да им пробутат някакво минало за „светло“ и „достойно“. Например за време, когато Нацията е била велика и недостижима (“Make America Great Again”, “Deutschland Uber Alles”, „България на Симеон Велики“ и подобни). Тъй като терминът „реакционери“ мигновено издава същността им, те се опитват да се пробутат за „консерватори“ или „десни“. Но стремежът им към отхвърлено от прогреса минало е сигурен индикатор – мигновено показва какво са всъщност.

Десните популисти обикновено са такива. Те са много по-разпространени днес от левите популисти и са по-злокачествени от тях. Левият популист обикновено обещава прекрасни неща – проблемът с него е, че няма да ги изпълни, и повечето хора вече знаят, че е измамник. Десният популист обикновено обещава ужасни неща в красива опаковка и проблемът е, че ще ги изпълни. И подкрепилите го тогава ще разберат за какво всъщност са се борили, но ще е вече късно.

Реакционерите са два типа – идиоти и психопати. Идиотите искрено вярват примерно че през Средновековието животът е бил прекрасен, селяните са работели по няколко дни в годината, благородниците са се грижели за доброто на всички, хората са живеели средно по над 100 години… Психопатите отлично знаят, че това е лъжа за идиоти и я повтарят именно затова. Миналото ги привлича с това, че е авторитарно и би им дало възможност да властват над по-свестните от тях. Нещо, за което нямат шансове при съвременна пазарна демокрация… Съответно идиотите са пехотинците-редници във войната на реакционерите да върнат миналото. Психопатите са техните офицери и генерали.

Опитите днес да се използват свободите на демокрацията, за да бъде връщано зловещо минало, са планирани от психопатите и извършвани под тяхна команда от идиотите реакционери. Част от тези опити е насаждането на расизъм, нацизъм, сексизъм и подобни идеологии на омразата, които се борим да оставим в миналото завинаги. Под маската на „свобода на словото“, и с претенциите, че който пречи на тези измами, е враг на свободата на словото.

Но свободата на словото не е абсолютна. Иначе телефонните измамници нямаше да са престъпници – те само говорят, другите сами им хвърлят парите си през балкона, нали? Щяха да са престъпници тези, които ги ловят и пращат в съда. Нито щеше да е престъпление уговарянето на деца от педофили – престъпление щеше да е да им се пречи. Вие кое подкрепяте – свободата на словото на тези категории или ограничаването ѝ?

(Преди няколко години в Ливърпул, ако не ме лъже паметта, имаше епидемия от заушка. Няколко десетки загинаха, няколкостотин останаха с трайни умствени увреждания или безплодие. Оказа се, че трийсетина години по-рано там е имало много успешна кампания на антиваксъри… Комитет на пострадалите даде антиваксърите под съд. Те заявиха в съда: „Ние само сме предоставили информацията. Свободата на словото е свещено и неотменно право. Решението са го взели родителите ви, съдете тях…“ Как мислите, да лъжат родителите да не си ваксинират децата тяхно свещено и неотменно право ли е? Може ли да им бъде търсена отговорност за последствията или не?)

Така е и с „десните“, които пищят как „крайно левите“, „световната либералфашистка конспирация“, „уокизмът“ и т.н. им отнемат свободата на словото. Не, не им я отнемат. Просто ги третират като каквито са се показали. Това е, което те не могат да понесат и пищят срещу него.

Затова е важно на такива това да се обяснява публично и в прав текст. И че свобода на словото и безотговорност за лъжи и проповядване на омраза са различни неща. Първото го имат – нека не лъжат, че го нямат. Второто ще го проимат когато го проимат телефонните измамници и педофилите.

[$] Modernizing accessibility for desktop Linux

Post Syndicated from jzb original https://lwn.net/Articles/971541/

In some aspects, such as in gaming, the Linux desktop has made
enormous strides in the past few years. In others, such as
accessibility, things have stagnated. At Open Source Summit North America (OSSNA), Matt Campbell spoke
about the need for, and an approach to, modernizing accessibility for
desktop Linux. This included a discussion of Newton, a fledgling
project that may greatly improve accessibility on the Linux desktop.

The collective thoughts of the interwebz