Ce sujet a été résolu
Linux is currently failing at desktop security.
The reality is uncomfortable:
1. The "Sandbox" is nonexistent.
On macOS or ChromeOS, apps have to ask permission to read files. On standard Desktop Linux? A malicious calculator app or a compromised PDF viewer has immediate, total access to your entire home directory. It can grab your SSH keys, browser cookies, and documents without asking.
2. "sudo" is security theater.
If an attacker compromises your user account, they don't need root to own you. They can simply alias sudo in your shell configuration to intercept your password, or use X11 to log your keystrokes. The boundary between "User" and "Root" is porous.
3. The Kernel is behind.
While Windows has spent years implementing aggressive exploit mitigations (CFG, VBS, CET), the Linux kernel remains a massive, monolithic block of memory-unsafe C code with a huge attack surface and significantly fewer modern defenses.
4. Server vs. Desktop.
"But the internet runs on Linux!" Yes, on stripped-down, single-purpose servers managed by pros. That is a completely different threat model than a general-purpose desktop running a GUI, media stacks, fonts, and random user-installed apps.
PLS pour les Jean-Linux
The reality is uncomfortable:
1. The "Sandbox" is nonexistent.
On macOS or ChromeOS, apps have to ask permission to read files. On standard Desktop Linux? A malicious calculator app or a compromised PDF viewer has immediate, total access to your entire home directory. It can grab your SSH keys, browser cookies, and documents without asking.
2. "sudo" is security theater.
If an attacker compromises your user account, they don't need root to own you. They can simply alias sudo in your shell configuration to intercept your password, or use X11 to log your keystrokes. The boundary between "User" and "Root" is porous.
3. The Kernel is behind.
While Windows has spent years implementing aggressive exploit mitigations (CFG, VBS, CET), the Linux kernel remains a massive, monolithic block of memory-unsafe C code with a huge attack surface and significantly fewer modern defenses.
4. Server vs. Desktop.
"But the internet runs on Linux!" Yes, on stripped-down, single-purpose servers managed by pros. That is a completely different threat model than a general-purpose desktop running a GUI, media stacks, fonts, and random user-installed apps.
PLS pour les Jean-Linux
https://x.com/iAnonymous3000/status/1996400615191200047
il y a 17 heures
Linux is currently failing at desktop security.
The reality is uncomfortable:
1. The "Sandbox" is nonexistent.
On macOS or ChromeOS, apps have to ask permission to read files. On standard Desktop Linux? A malicious calculator app or a compromised PDF viewer has immediate, total access to your entire home directory. It can grab your SSH keys, browser cookies, and documents without asking.
2. "sudo" is security theater.
If an attacker compromises your user account, they don't need root to own you. They can simply alias sudo in your shell configuration to intercept your password, or use X11 to log your keystrokes. The boundary between "User" and "Root" is porous.
3. The Kernel is behind.
While Windows has spent years implementing aggressive exploit mitigations (CFG, VBS, CET), the Linux kernel remains a massive, monolithic block of memory-unsafe C code with a huge attack surface and significantly fewer modern defenses.
4. Server vs. Desktop.
"But the internet runs on Linux!" Yes, on stripped-down, single-purpose servers managed by pros. That is a completely different threat model than a general-purpose desktop running a GUI, media stacks, fonts, and random user-installed apps.
PLS pour les Jean-Linux
The reality is uncomfortable:
1. The "Sandbox" is nonexistent.
On macOS or ChromeOS, apps have to ask permission to read files. On standard Desktop Linux? A malicious calculator app or a compromised PDF viewer has immediate, total access to your entire home directory. It can grab your SSH keys, browser cookies, and documents without asking.
2. "sudo" is security theater.
If an attacker compromises your user account, they don't need root to own you. They can simply alias sudo in your shell configuration to intercept your password, or use X11 to log your keystrokes. The boundary between "User" and "Root" is porous.
3. The Kernel is behind.
While Windows has spent years implementing aggressive exploit mitigations (CFG, VBS, CET), the Linux kernel remains a massive, monolithic block of memory-unsafe C code with a huge attack surface and significantly fewer modern defenses.
4. Server vs. Desktop.
"But the internet runs on Linux!" Yes, on stripped-down, single-purpose servers managed by pros. That is a completely different threat model than a general-purpose desktop running a GUI, media stacks, fonts, and random user-installed apps.
PLS pour les Jean-Linux
https://x.com/iAnonymous3000/status/1996400615191200047
Je pensais que tu étais un Jean Linux
il y a 17 heures
L'op qui va perdre 80% des foromeurs d'entrée de jeu parce qu'il a pas traduit le texte
il y a 17 heures
Linux is currently failing at desktop security.
The reality is uncomfortable:
1. The "Sandbox" is nonexistent.
On macOS or ChromeOS, apps have to ask permission to read files. On standard Desktop Linux? A malicious calculator app or a compromised PDF viewer has immediate, total access to your entire home directory. It can grab your SSH keys, browser cookies, and documents without asking.
2. "sudo" is security theater.
If an attacker compromises your user account, they don't need root to own you. They can simply alias sudo in your shell configuration to intercept your password, or use X11 to log your keystrokes. The boundary between "User" and "Root" is porous.
3. The Kernel is behind.
While Windows has spent years implementing aggressive exploit mitigations (CFG, VBS, CET), the Linux kernel remains a massive, monolithic block of memory-unsafe C code with a huge attack surface and significantly fewer modern defenses.
4. Server vs. Desktop.
"But the internet runs on Linux!" Yes, on stripped-down, single-purpose servers managed by pros. That is a completely different threat model than a general-purpose desktop running a GUI, media stacks, fonts, and random user-installed apps.
PLS pour les Jean-Linux
The reality is uncomfortable:
1. The "Sandbox" is nonexistent.
On macOS or ChromeOS, apps have to ask permission to read files. On standard Desktop Linux? A malicious calculator app or a compromised PDF viewer has immediate, total access to your entire home directory. It can grab your SSH keys, browser cookies, and documents without asking.
2. "sudo" is security theater.
If an attacker compromises your user account, they don't need root to own you. They can simply alias sudo in your shell configuration to intercept your password, or use X11 to log your keystrokes. The boundary between "User" and "Root" is porous.
3. The Kernel is behind.
While Windows has spent years implementing aggressive exploit mitigations (CFG, VBS, CET), the Linux kernel remains a massive, monolithic block of memory-unsafe C code with a huge attack surface and significantly fewer modern defenses.
4. Server vs. Desktop.
"But the internet runs on Linux!" Yes, on stripped-down, single-purpose servers managed by pros. That is a completely different threat model than a general-purpose desktop running a GUI, media stacks, fonts, and random user-installed apps.
PLS pour les Jean-Linux
https://x.com/iAnonymous3000/status/1996400615191200047
J'allais faire un long pavé de debunk puis j'ai vu que le mec s'appelait Sooraj, ça suffit amplement à disqualifier son avis
il y a 16 heures
Je pensais que tu étais un Jean Linux
J'ai jamais été un grand fan de Linux en vrai même si j'espere qu'il va bien se developper, je suis retourné sur Windows
il y a 15 heures
J'allais faire un long pavé de debunk puis j'ai vu que le mec s'appelait Sooraj, ça suffit amplement à disqualifier son avis
il y a 15 heures
Linux is currently failing at desktop security.
The reality is uncomfortable:
1. The "Sandbox" is nonexistent.
On macOS or ChromeOS, apps have to ask permission to read files. On standard Desktop Linux? A malicious calculator app or a compromised PDF viewer has immediate, total access to your entire home directory. It can grab your SSH keys, browser cookies, and documents without asking.
2. "sudo" is security theater.
If an attacker compromises your user account, they don't need root to own you. They can simply alias sudo in your shell configuration to intercept your password, or use X11 to log your keystrokes. The boundary between "User" and "Root" is porous.
3. The Kernel is behind.
While Windows has spent years implementing aggressive exploit mitigations (CFG, VBS, CET), the Linux kernel remains a massive, monolithic block of memory-unsafe C code with a huge attack surface and significantly fewer modern defenses.
4. Server vs. Desktop.
"But the internet runs on Linux!" Yes, on stripped-down, single-purpose servers managed by pros. That is a completely different threat model than a general-purpose desktop running a GUI, media stacks, fonts, and random user-installed apps.
PLS pour les Jean-Linux
The reality is uncomfortable:
1. The "Sandbox" is nonexistent.
On macOS or ChromeOS, apps have to ask permission to read files. On standard Desktop Linux? A malicious calculator app or a compromised PDF viewer has immediate, total access to your entire home directory. It can grab your SSH keys, browser cookies, and documents without asking.
2. "sudo" is security theater.
If an attacker compromises your user account, they don't need root to own you. They can simply alias sudo in your shell configuration to intercept your password, or use X11 to log your keystrokes. The boundary between "User" and "Root" is porous.
3. The Kernel is behind.
While Windows has spent years implementing aggressive exploit mitigations (CFG, VBS, CET), the Linux kernel remains a massive, monolithic block of memory-unsafe C code with a huge attack surface and significantly fewer modern defenses.
4. Server vs. Desktop.
"But the internet runs on Linux!" Yes, on stripped-down, single-purpose servers managed by pros. That is a completely different threat model than a general-purpose desktop running a GUI, media stacks, fonts, and random user-installed apps.
PLS pour les Jean-Linux
https://x.com/iAnonymous3000/status/1996400615191200047
Peut-être que si on utilisait que des applications de confiance au lieu de multiplier leur nombre à l'infini, on n'aurait pas besoin de sandboxing et autres techniques de combat. En voila une surface d'attaque dont ne ne parle jamais. Un ordinateur ne doit pas être une zone de guerre.
Ce modèle d'apps à tire-larigot est fondamentalement un trou de sécurité.
Ce modèle d'apps à tire-larigot est fondamentalement un trou de sécurité.
Certifié tous gaz.
il y a 15 heures
LeBotDuPCC
14h
L'expert en sécurité qui n'a jamais entendu parler de gestion de droits.
No Nut : 5ème régiment, matricule R5-05
il y a 14 heures
JVCucks
17h
zéro virus contrairement à windaube
Parce que les hackeurs savent que les utilisateurs de linux sont à 90% des informaticiens puant, donc aucun intérêt de perde du temps pour eux
il y a 14 heures
Linux is currently failing at desktop security.
The reality is uncomfortable:
1. The "Sandbox" is nonexistent.
On macOS or ChromeOS, apps have to ask permission to read files. On standard Desktop Linux? A malicious calculator app or a compromised PDF viewer has immediate, total access to your entire home directory. It can grab your SSH keys, browser cookies, and documents without asking.
2. "sudo" is security theater.
If an attacker compromises your user account, they don't need root to own you. They can simply alias sudo in your shell configuration to intercept your password, or use X11 to log your keystrokes. The boundary between "User" and "Root" is porous.
3. The Kernel is behind.
While Windows has spent years implementing aggressive exploit mitigations (CFG, VBS, CET), the Linux kernel remains a massive, monolithic block of memory-unsafe C code with a huge attack surface and significantly fewer modern defenses.
4. Server vs. Desktop.
"But the internet runs on Linux!" Yes, on stripped-down, single-purpose servers managed by pros. That is a completely different threat model than a general-purpose desktop running a GUI, media stacks, fonts, and random user-installed apps.
PLS pour les Jean-Linux
The reality is uncomfortable:
1. The "Sandbox" is nonexistent.
On macOS or ChromeOS, apps have to ask permission to read files. On standard Desktop Linux? A malicious calculator app or a compromised PDF viewer has immediate, total access to your entire home directory. It can grab your SSH keys, browser cookies, and documents without asking.
2. "sudo" is security theater.
If an attacker compromises your user account, they don't need root to own you. They can simply alias sudo in your shell configuration to intercept your password, or use X11 to log your keystrokes. The boundary between "User" and "Root" is porous.
3. The Kernel is behind.
While Windows has spent years implementing aggressive exploit mitigations (CFG, VBS, CET), the Linux kernel remains a massive, monolithic block of memory-unsafe C code with a huge attack surface and significantly fewer modern defenses.
4. Server vs. Desktop.
"But the internet runs on Linux!" Yes, on stripped-down, single-purpose servers managed by pros. That is a completely different threat model than a general-purpose desktop running a GUI, media stacks, fonts, and random user-installed apps.
PLS pour les Jean-Linux
https://x.com/iAnonymous3000/status/1996400615191200047
1. C'est le problème de X11. Wayland règle ça et Flathub ainsi que Snap.
2. Oui. M'enfin c'est comme le mode admin de Windows.
Et je rajouterai que Windows, de par sa grande présence sur les PCs, est largement plus la cible des attaques.
2. Oui. M'enfin c'est comme le mode admin de Windows.
Et je rajouterai que Windows, de par sa grande présence sur les PCs, est largement plus la cible des attaques.
Nous sommes un.
il y a 14 heures
Linux is currently failing at desktop security.
The reality is uncomfortable:
1. The "Sandbox" is nonexistent.
On macOS or ChromeOS, apps have to ask permission to read files. On standard Desktop Linux? A malicious calculator app or a compromised PDF viewer has immediate, total access to your entire home directory. It can grab your SSH keys, browser cookies, and documents without asking.
2. "sudo" is security theater.
If an attacker compromises your user account, they don't need root to own you. They can simply alias sudo in your shell configuration to intercept your password, or use X11 to log your keystrokes. The boundary between "User" and "Root" is porous.
3. The Kernel is behind.
While Windows has spent years implementing aggressive exploit mitigations (CFG, VBS, CET), the Linux kernel remains a massive, monolithic block of memory-unsafe C code with a huge attack surface and significantly fewer modern defenses.
4. Server vs. Desktop.
"But the internet runs on Linux!" Yes, on stripped-down, single-purpose servers managed by pros. That is a completely different threat model than a general-purpose desktop running a GUI, media stacks, fonts, and random user-installed apps.
PLS pour les Jean-Linux
The reality is uncomfortable:
1. The "Sandbox" is nonexistent.
On macOS or ChromeOS, apps have to ask permission to read files. On standard Desktop Linux? A malicious calculator app or a compromised PDF viewer has immediate, total access to your entire home directory. It can grab your SSH keys, browser cookies, and documents without asking.
2. "sudo" is security theater.
If an attacker compromises your user account, they don't need root to own you. They can simply alias sudo in your shell configuration to intercept your password, or use X11 to log your keystrokes. The boundary between "User" and "Root" is porous.
3. The Kernel is behind.
While Windows has spent years implementing aggressive exploit mitigations (CFG, VBS, CET), the Linux kernel remains a massive, monolithic block of memory-unsafe C code with a huge attack surface and significantly fewer modern defenses.
4. Server vs. Desktop.
"But the internet runs on Linux!" Yes, on stripped-down, single-purpose servers managed by pros. That is a completely different threat model than a general-purpose desktop running a GUI, media stacks, fonts, and random user-installed apps.
PLS pour les Jean-Linux
https://x.com/iAnonymous3000/status/1996400615191200047
Oui mais moins populaires donc moins d'emmerde
Kénophobie ou Leukophobie
il y a 14 heures
Zephyr
17h
L'op qui va perdre 80% des foromeurs d'entrée de jeu parce qu'il a pas traduit le texte
Abusez pas c'est de l'anglais bidon là...
il y a 13 heures
Saar we love Windows and Israel saar
Nous sommes la jeunesse, nous sommes la vie, Rex doit vaincre c'est pourquoi Rex vaincra
il y a 13 heures
Linux is currently failing at desktop security.
The reality is uncomfortable:
1. The "Sandbox" is nonexistent.
On macOS or ChromeOS, apps have to ask permission to read files. On standard Desktop Linux? A malicious calculator app or a compromised PDF viewer has immediate, total access to your entire home directory. It can grab your SSH keys, browser cookies, and documents without asking.
2. "sudo" is security theater.
If an attacker compromises your user account, they don't need root to own you. They can simply alias sudo in your shell configuration to intercept your password, or use X11 to log your keystrokes. The boundary between "User" and "Root" is porous.
3. The Kernel is behind.
While Windows has spent years implementing aggressive exploit mitigations (CFG, VBS, CET), the Linux kernel remains a massive, monolithic block of memory-unsafe C code with a huge attack surface and significantly fewer modern defenses.
4. Server vs. Desktop.
"But the internet runs on Linux!" Yes, on stripped-down, single-purpose servers managed by pros. That is a completely different threat model than a general-purpose desktop running a GUI, media stacks, fonts, and random user-installed apps.
PLS pour les Jean-Linux
The reality is uncomfortable:
1. The "Sandbox" is nonexistent.
On macOS or ChromeOS, apps have to ask permission to read files. On standard Desktop Linux? A malicious calculator app or a compromised PDF viewer has immediate, total access to your entire home directory. It can grab your SSH keys, browser cookies, and documents without asking.
2. "sudo" is security theater.
If an attacker compromises your user account, they don't need root to own you. They can simply alias sudo in your shell configuration to intercept your password, or use X11 to log your keystrokes. The boundary between "User" and "Root" is porous.
3. The Kernel is behind.
While Windows has spent years implementing aggressive exploit mitigations (CFG, VBS, CET), the Linux kernel remains a massive, monolithic block of memory-unsafe C code with a huge attack surface and significantly fewer modern defenses.
4. Server vs. Desktop.
"But the internet runs on Linux!" Yes, on stripped-down, single-purpose servers managed by pros. That is a completely different threat model than a general-purpose desktop running a GUI, media stacks, fonts, and random user-installed apps.
PLS pour les Jean-Linux
https://x.com/iAnonymous3000/status/1996400615191200047
Depuis la backdoor xz utils, j'ai arrêté Linux. Impossible de savoir si tes packages sont compromis vu que tout est dev par des inconnus...
"Oui mais tu peux aller lire le code source"
J'ai que ça à foutre d'analyser les modifications du code à chaque maj d'un package
"Oui mais tu peux aller lire le code source"
J'ai que ça à foutre d'analyser les modifications du code à chaque maj d'un package
il y a 13 heures
Depuis la backdoor xz utils, j'ai arrêté Linux. Impossible de savoir si tes packages sont compromis vu que tout est dev par des inconnus...
"Oui mais tu peux aller lire le code source"
J'ai que ça à foutre d'analyser les modifications du code à chaque maj d'un package
"Oui mais tu peux aller lire le code source"
J'ai que ça à foutre d'analyser les modifications du code à chaque maj d'un package
La backdoor xz c'est un cas aboslument exceptionnel. On parle d'un truc créé avec les moyens d'un gouvernement pour déjouer l'attention de dizaines d'années d'audits et de fuzzings en tout genre
Quant aux inconnus, on parle pas de randoms qui contribuent mais (toujours avec les moyens d'un gouvernement) de plusieurs comptes qui ont mis des années à bâtir une confiance avec les contributeurs pour gratter des permissions
Quant aux inconnus, on parle pas de randoms qui contribuent mais (toujours avec les moyens d'un gouvernement) de plusieurs comptes qui ont mis des années à bâtir une confiance avec les contributeurs pour gratter des permissions
il y a 13 heures




























