home.social

#openssh — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #openssh, aggregated by home.social.

  1. I created a presentation and a Docker-based hands-on lab in which you can learn how SSH works, how it can be attacked and how to protect it: sshlabs.compass-security.train #security #infosec #network #ssh #openssh #pentest

  2. I created a presentation and a Docker-based hands-on lab in which you can learn how SSH works, how it can be attacked and how to protect it: sshlabs.compass-security.train #security #infosec #network #ssh #openssh #pentest

  3. I created a presentation and a Docker-based hands-on lab in which you can learn how SSH works, how it can be attacked and how to protect it: sshlabs.compass-security.train #security #infosec #network #ssh #openssh #pentest

  4. I created a presentation and a Docker-based hands-on lab in which you can learn how SSH works, how it can be attacked and how to protect it: sshlabs.compass-security.train #security #infosec #network #ssh #openssh #pentest

  5. I created a presentation and a Docker-based hands-on lab in which you can learn how SSH works, how it can be attacked and how to protect it: sshlabs.compass-security.train #security #infosec #network #ssh #openssh #pentest

  6. SSH как корпоративный L3-туннель: когда классические VPN-протоколы больше не работают

    В последние годы для команд, которые работают с зарубежной инфраструктурой из России, обычный корпоративный VPN перестал быть чем-то, что можно один раз настроить и забыть. OpenVPN, WireGuard, IPsec, различные TLS- и QUIC-обёртки могут работать стабильно месяцами, а потом внезапно начать деградировать: где-то соединение не устанавливается, где-то режется UDP, где-то DPI начинает узнавать сигнатуры, где-то провайдер меняет правила фильтрации. Для компании это превращается не в техническую мелочь, а в операционный риск. Инженеры не могут попасть на серверы. DevOps не может проверить прод. Администратор не может забрать бэкап. Пентестер не может подключиться к стенду заказчика. При этом инфраструктура может находиться в Европе, США, Азии или у любого другого зарубежного провайдера, а сотрудники — физически находиться в РФ. В какой-то момент мы пришли к простой мысли: если из корпоративной сети ещё можно установить исходящее SSH-соединение, то можно попробовать использовать сам OpenSSH не только как инструмент администрирования, но и как транспорт для L3-туннеля. В OpenSSH для этого давно существует режим ssh -w, который поднимает туннель через tun-устройство. Идея статьи не в том, чтобы объявить ssh -w «лучшим VPN на все времена». Это не замена WireGuard для нормальной постоянной инфраструктуры и не серебряная пуля против любых сетевых ограничений. Но это очень полезный аварийный и корпоративный вариант: работает поверх обычного SSH, не требует отдельного VPN-демона на сервере, может быть поднят на дешёвом VPS, использует привычную модель ключей OpenSSH и позволяет строить полноценную маршрутизацию на L3.

    habr.com/ru/articles/1036160/

    #ssh #vpn #ssh_tunnel #SSH_VPN #openssh #wintun

  7. 37 Debian LTS advisories were released in February fixing 145 CVEs across various packages. These include security fixes for bind9, firefox-esr, imagemagick, libpng, mbedtls, openssh, packagekit, perl, postgresql-13, python3.9, systemd and many more.

    Debian LTS contributors also prepared updates for more recent releases, Debian 12 (#bookworm), Debian 13 (#trixie) and Debian unstable.

    Read the full report: freexian.com/blog/debian-lts-r

    This work is funded by Freexian's Debian LTS offering. Become a sponsor of Debian LTS (freexian.com/lts/debian/?utm_s) and enjoy the benefits (freexian.com/lts/debian/detail).

    #debian #debianlts #freexian #imagemagick #libpng #openssh #packagekit #perl #systemd

  8. 37 Debian LTS advisories were released in February fixing 145 CVEs across various packages. These include security fixes for bind9, firefox-esr, imagemagick, libpng, mbedtls, openssh, packagekit, perl, postgresql-13, python3.9, systemd and many more.

    Debian LTS contributors also prepared updates for more recent releases, Debian 12 (#bookworm), Debian 13 (#trixie) and Debian unstable.

    Read the full report: freexian.com/blog/debian-lts-r

    This work is funded by Freexian's Debian LTS offering. Become a sponsor of Debian LTS (freexian.com/lts/debian/?utm_s) and enjoy the benefits (freexian.com/lts/debian/detail).

    #debian #debianlts #freexian #imagemagick #libpng #openssh #packagekit #perl #systemd

  9. 37 Debian LTS advisories were released in February fixing 145 CVEs across various packages. These include security fixes for bind9, firefox-esr, imagemagick, libpng, mbedtls, openssh, packagekit, perl, postgresql-13, python3.9, systemd and many more.

    Debian LTS contributors also prepared updates for more recent releases, Debian 12 (), Debian 13 () and Debian unstable.

    Read the full report: freexian.com/blog/debian-lts-r

    This work is funded by Freexian's Debian LTS offering. Become a sponsor of Debian LTS (freexian.com/lts/debian/?utm_s) and enjoy the benefits (freexian.com/lts/debian/detail).

  10. 37 Debian LTS advisories were released in February fixing 145 CVEs across various packages. These include security fixes for bind9, firefox-esr, imagemagick, libpng, mbedtls, openssh, packagekit, perl, postgresql-13, python3.9, systemd and many more.

    Debian LTS contributors also prepared updates for more recent releases, Debian 12 (#bookworm), Debian 13 (#trixie) and Debian unstable.

    Read the full report: freexian.com/blog/debian-lts-r

    This work is funded by Freexian's Debian LTS offering. Become a sponsor of Debian LTS (freexian.com/lts/debian/?utm_s) and enjoy the benefits (freexian.com/lts/debian/detail).

    #debian #debianlts #freexian #imagemagick #libpng #openssh #packagekit #perl #systemd

  11. 37 Debian LTS advisories were released in February fixing 145 CVEs across various packages. These include security fixes for bind9, firefox-esr, imagemagick, libpng, mbedtls, openssh, packagekit, perl, postgresql-13, python3.9, systemd and many more.

    Debian LTS contributors also prepared updates for more recent releases, Debian 12 (#bookworm), Debian 13 (#trixie) and Debian unstable.

    Read the full report: freexian.com/blog/debian-lts-r

    This work is funded by Freexian's Debian LTS offering. Become a sponsor of Debian LTS (freexian.com/lts/debian/?utm_s) and enjoy the benefits (freexian.com/lts/debian/detail).

    #debian #debianlts #freexian #imagemagick #libpng #openssh #packagekit #perl #systemd

  12. OK, normally I have my shit wired together, but this bastard is getting to me.

    The requirement is for 'phishing-resistant' second factor. That rules out all of the six-digit code apps - it is too easy apparently to get someone to read out their codes to an attacker.

    Again, IDK, but apparently 'phishing-resistant' is the next Big Thing. My personal feeling? We are chasing our shadows. Unless I am the last alive Iranian nuclear bloke, my login is as secure as I can be bothered to make it, and I am bound to be disappointed by a weakness at some point in the near or far future. Phishing isn't on the agenda.

    Life.

    I carry a seemingly-fine cryptographic store about with me most days and ludicrously call it my 'phone'. It can sign stuff, wrangle certificates, store passwords, read faces and fingerprints and QRcodes and NFC tags. Heaps of useful 'security' stuff. I wouldn't call the software environment _secure_ at all, but ... IDK, people seem happy enough with it. Anything for an easy life. Row with the flow.

    So I search for:
    "google passkey login with ssh"
    My god, whatalottasloppa comes back. A gattling gun of half-arsery, cant and junk advice.
    Then "MS hello for business login ssh". Christ almighty. Much worse. Worse again.
    Then "Apple ID login to ssh". At least that seems to be a simple: "no". A relief really.

    Someone in the know please: can I set up my sshd to use my phone-based passkey as a; primary, secondary or even the complete, login?

    #TOTP #HOTP #passkey #sshd #key #certificates #PSK #login #ssh #linux #pam #openssh

  13. OK, normally I have my shit wired together, but this bastard is getting to me.

    The requirement is for 'phishing-resistant' second factor. That rules out all of the six-digit code apps - it is too easy apparently to get someone to read out their codes to an attacker.

    Again, IDK, but apparently 'phishing-resistant' is the next Big Thing. My personal feeling? We are chasing our shadows. Unless I am the last alive Iranian nuclear bloke, my login is as secure as I can be bothered to make it, and I am bound to be disappointed by a weakness at some point in the near or far future. Phishing isn't on the agenda.

    Life.

    I carry a seemingly-fine cryptographic store about with me most days and ludicrously call it my 'phone'. It can sign stuff, wrangle certificates, store passwords, read faces and fingerprints and QRcodes and NFC tags. Heaps of useful 'security' stuff. I wouldn't call the software environment _secure_ at all, but ... IDK, people seem happy enough with it. Anything for an easy life. Row with the flow.

    So I search for:
    "google passkey login with ssh"
    My god, whatalottasloppa comes back. A gattling gun of half-arsery, cant and junk advice.
    Then "MS hello for business login ssh". Christ almighty. Much worse. Worse again.
    Then "Apple ID login to ssh". At least that seems to be a simple: "no". A relief really.

    Someone in the know please: can I set up my sshd to use my phone-based passkey as a; primary, secondary or even the complete, login?

    #TOTP #HOTP #passkey #sshd #key #certificates #PSK #login #ssh #linux #pam #openssh

  14. OK, normally I have my shit wired together, but this bastard is getting to me.

    The requirement is for 'phishing-resistant' second factor. That rules out all of the six-digit code apps - it is too easy apparently to get someone to read out their codes to an attacker.

    Again, IDK, but apparently 'phishing-resistant' is the next Big Thing. My personal feeling? We are chasing our shadows. Unless I am the last alive Iranian nuclear bloke, my login is as secure as I can be bothered to make it, and I am bound to be disappointed by a weakness at some point in the near or far future. Phishing isn't on the agenda.

    Life.

    I carry a seemingly-fine cryptographic store about with me most days and ludicrously call it my 'phone'. It can sign stuff, wrangle certificates, store passwords, read faces and fingerprints and QRcodes and NFC tags. Heaps of useful 'security' stuff. I wouldn't call the software environment _secure_ at all, but ... IDK, people seem happy enough with it. Anything for an easy life. Row with the flow.

    So I search for:
    "google passkey login with ssh"
    My god, whatalottasloppa comes back. A gattling gun of half-arsery, cant and junk advice.
    Then "MS hello for business login ssh". Christ almighty. Much worse. Worse again.
    Then "Apple ID login to ssh". At least that seems to be a simple: "no". A relief really.

    Someone in the know please: can I set up my sshd to use my phone-based passkey as a; primary, secondary or even the complete, login?

    #TOTP #HOTP #passkey #sshd #key #certificates #PSK #login #ssh #linux #pam #openssh

  15. OK, normally I have my shit wired together, but this bastard is getting to me.

    The requirement is for 'phishing-resistant' second factor. That rules out all of the six-digit code apps - it is too easy apparently to get someone to read out their codes to an attacker.

    Again, IDK, but apparently 'phishing-resistant' is the next Big Thing. My personal feeling? We are chasing our shadows. Unless I am the last alive Iranian nuclear bloke, my login is as secure as I can be bothered to make it, and I am bound to be disappointed by a weakness at some point in the near or far future. Phishing isn't on the agenda.

    Life.

    I carry a seemingly-fine cryptographic store about with me most days and ludicrously call it my 'phone'. It can sign stuff, wrangle certificates, store passwords, read faces and fingerprints and QRcodes and NFC tags. Heaps of useful 'security' stuff. I wouldn't call the software environment _secure_ at all, but ... IDK, people seem happy enough with it. Anything for an easy life. Row with the flow.

    So I search for:
    "google passkey login with ssh"
    My god, whatalottasloppa comes back. A gattling gun of half-arsery, cant and junk advice.
    Then "MS hello for business login ssh". Christ almighty. Much worse. Worse again.
    Then "Apple ID login to ssh". At least that seems to be a simple: "no". A relief really.

    Someone in the know please: can I set up my sshd to use my phone-based passkey as a; primary, secondary or even the complete, login?

    #TOTP #HOTP #passkey #sshd #key #certificates #PSK #login #ssh #linux #pam #openssh

  16. OK, normally I have my shit wired together, but this bastard is getting to me.

    The requirement is for 'phishing-resistant' second factor. That rules out all of the six-digit code apps - it is too easy apparently to get someone to read out their codes to an attacker.

    Again, IDK, but apparently 'phishing-resistant' is the next Big Thing. My personal feeling? We are chasing our shadows. Unless I am the last alive Iranian nuclear bloke, my login is as secure as I can be bothered to make it, and I am bound to be disappointed by a weakness at some point in the near or far future. Phishing isn't on the agenda.

    Life.

    I carry a seemingly-fine cryptographic store about with me most days and ludicrously call it my 'phone'. It can sign stuff, wrangle certificates, store passwords, read faces and fingerprints and QRcodes and NFC tags. Heaps of useful 'security' stuff. I wouldn't call the software environment _secure_ at all, but ... IDK, people seem happy enough with it. Anything for an easy life. Row with the flow.

    So I search for:
    "google passkey login with ssh"
    My god, whatalottasloppa comes back. A gattling gun of half-arsery, cant and junk advice.
    Then "MS hello for business login ssh". Christ almighty. Much worse. Worse again.
    Then "Apple ID login to ssh". At least that seems to be a simple: "no". A relief really.

    Someone in the know please: can I set up my sshd to use my phone-based passkey as a; primary, secondary or even the complete, login?

    #TOTP #HOTP #passkey #sshd #key #certificates #PSK #login #ssh #linux #pam #openssh

  17. Today feels like a good day to point out that ssh host keys should be tied to your hardware.

    I've heard TPMs are good at this.

    #OpenSSH #Linux #security

  18. collaborators worked on detecting undeclared file conflicts, mini-sprint improving contributors.debian.org, security-tracker performance, fixing dput-ng data loss bug, MiniDebConf Campinas and many more contributions to in April 2026.

    Read all the details at freexian.com/blog/debian-contr

    We thank the organizations subscribing to our Long Term Support contracts (freexian.com/lts/?utm_source=m) and consulting services (freexian.com/services/?utm_sou) for making this possible.

    -ng

  19. #Freexian collaborators worked on detecting undeclared file conflicts, mini-sprint improving contributors.debian.org, security-tracker performance, fixing dput-ng data loss bug, MiniDebConf Campinas and many more contributions to #Debian in April 2026.

    Read all the details at freexian.com/blog/debian-contr

    We thank the organizations subscribing to our Long Term Support contracts (freexian.com/lts/?utm_source=m) and consulting services (freexian.com/services/?utm_sou) for making this possible.

    #dput-ng #linux #openssh

  20. #Freexian collaborators worked on detecting undeclared file conflicts, mini-sprint improving contributors.debian.org, security-tracker performance, fixing dput-ng data loss bug, MiniDebConf Campinas and many more contributions to #Debian in April 2026.

    Read all the details at freexian.com/blog/debian-contr

    We thank the organizations subscribing to our Long Term Support contracts (freexian.com/lts/?utm_source=m) and consulting services (freexian.com/services/?utm_sou) for making this possible.

    #dput-ng #linux #openssh

  21. #Freexian collaborators worked on detecting undeclared file conflicts, mini-sprint improving contributors.debian.org, security-tracker performance, fixing dput-ng data loss bug, MiniDebConf Campinas and many more contributions to #Debian in April 2026.

    Read all the details at freexian.com/blog/debian-contr

    We thank the organizations subscribing to our Long Term Support contracts (freexian.com/lts/?utm_source=m) and consulting services (freexian.com/services/?utm_sou) for making this possible.

    #dput-ng #linux #openssh

  22. #Freexian collaborators worked on detecting undeclared file conflicts, mini-sprint improving contributors.debian.org, security-tracker performance, fixing dput-ng data loss bug, MiniDebConf Campinas and many more contributions to #Debian in April 2026.

    Read all the details at freexian.com/blog/debian-contr

    We thank the organizations subscribing to our Long Term Support contracts (freexian.com/lts/?utm_source=m) and consulting services (freexian.com/services/?utm_sou) for making this possible.

    #dput-ng #linux #openssh

  23. @FritzAdalis @RuntimeArguments @jammcq @YesJustWolf

    Thanks. I did look this up after I wrote the post. I should have looked it up before. But still, without knowing that history, it appeared the speaker was either confused about and or equating them or something. It wasn't obvious to me that the OpenBSD team *wrote* OpenSSH. That's the way I heard it, might have misinterpreted what was said.

  24. @RuntimeArguments @jammcq @YesJustWolf

    I've been a user since 1984, and spent my working life developing flavors of Unix and now . I listened to this episode over the past couple of days. I'm a long time user of One point of confusion and a few points that I learned.

    When talking about the origins of you talked about but didn't explain how it related to OpenSSH . Was OpenBSD involved in the creation of OpenSSH ? It could have used explanation.

    1/2

  25. openssh-server post-installation script error (exit status 10) and SSH not working #apt #dpkg #openssh

    askubuntu.com/q/1566463/612

  26. openssh-server post-installation script error (exit status 10) and SSH not working #apt #dpkg #openssh

    askubuntu.com/q/1566463/612

  27. openssh-server post-installation script error (exit status 10) and SSH not working #apt #dpkg #openssh

    askubuntu.com/q/1566463/612

  28. openssh-server post-installation script error (exit status 10) and SSH not working #apt #dpkg #openssh

    askubuntu.com/q/1566463/612

  29. openssh-server post-installation script error (exit status 10) and SSH not working #apt #dpkg #openssh

    askubuntu.com/q/1566463/612

  30. Did a new release of ssh-tpm-agent.

    github.com/Foxboron/ssh-tpm-ag

    `ssh-tpm-add` now supports `-c` for confirmation dialogs before key usage, along with a nice process chain. Thanks to @mic92

    #TPM #Security #OpenSSH #SSH

  31. Did a new release of ssh-tpm-agent.

    github.com/Foxboron/ssh-tpm-ag

    `ssh-tpm-add` now supports `-c` for confirmation dialogs before key usage, along with a nice process chain. Thanks to @mic92

    #TPM #Security #OpenSSH #SSH

  32. Did a new release of ssh-tpm-agent.

    github.com/Foxboron/ssh-tpm-ag

    `ssh-tpm-add` now supports `-c` for confirmation dialogs before key usage, along with a nice process chain. Thanks to @mic92

    #TPM #Security #OpenSSH #SSH

  33. Did a new release of ssh-tpm-agent.

    github.com/Foxboron/ssh-tpm-ag

    `ssh-tpm-add` now supports `-c` for confirmation dialogs before key usage, along with a nice process chain. Thanks to @mic92

    #TPM #Security #OpenSSH #SSH

  34. Did a new release of ssh-tpm-agent.

    github.com/Foxboron/ssh-tpm-ag

    `ssh-tpm-add` now supports `-c` for confirmation dialogs before key usage, along with a nice process chain. Thanks to @mic92

    #TPM #Security #OpenSSH #SSH

  35. 🕵🏻‍♂️ [InfoSec MASHUP] - This week's news cycle handed us the usual parade of breaches, arrests, and patch-your-stuff urgency — but if you squint at the #Malware section long enough, a more uncomfortable story emerges. #SAP-related npm packages backdoored with a credential stealer. A popular #PyPI package hijacked via a forged signed release pushed through a compromised GitHub Actions workflow. Seventy-three "sleeper" extensions quietly sitting in #OpenVSX, waiting. The common thread: attackers aren't breaking down the front door anymore. They're walking in through the tools developers use every day, often with a valid signature and a clean commit history.

    What makes this particularly fun — in the way a slow-motion disaster is fun — is that the blast radius isn't just the developer who ran pip install. It's every downstream user, every CI/CD pipeline, every AI coding agent that helpfully executed the preinstall hook without asking questions. The supply chain isn't a niche threat vector reserved for nation-state ops anymore. It's where commodity attackers are increasingly playing, because it scales beautifully and the detection gap remains embarrassingly wide.

    → Week #18/2026 also covers: Supply chain attackers found the path of least resistance, #OpenSSH patched a bug older than most junior devs, and #Europe is done pretending U.S. #cloud is a neutral choice.

    Full issue 👉 infosec-mashup.santolaria.net/

    If you find it useful, subscribe to get it in your inbox every weekend 📨 #infosecMASHUP #cybersecurity #infosec #threatintel #AI

  36. 🕵🏻‍♂️ [InfoSec MASHUP] - This week's news cycle handed us the usual parade of breaches, arrests, and patch-your-stuff urgency — but if you squint at the #Malware section long enough, a more uncomfortable story emerges. #SAP-related npm packages backdoored with a credential stealer. A popular #PyPI package hijacked via a forged signed release pushed through a compromised GitHub Actions workflow. Seventy-three "sleeper" extensions quietly sitting in #OpenVSX, waiting. The common thread: attackers aren't breaking down the front door anymore. They're walking in through the tools developers use every day, often with a valid signature and a clean commit history.

    What makes this particularly fun — in the way a slow-motion disaster is fun — is that the blast radius isn't just the developer who ran pip install. It's every downstream user, every CI/CD pipeline, every AI coding agent that helpfully executed the preinstall hook without asking questions. The supply chain isn't a niche threat vector reserved for nation-state ops anymore. It's where commodity attackers are increasingly playing, because it scales beautifully and the detection gap remains embarrassingly wide.

    → Week #18/2026 also covers: Supply chain attackers found the path of least resistance, #OpenSSH patched a bug older than most junior devs, and #Europe is done pretending U.S. #cloud is a neutral choice.

    Full issue 👉 infosec-mashup.santolaria.net/

    If you find it useful, subscribe to get it in your inbox every weekend 📨 #infosecMASHUP #cybersecurity #infosec #threatintel #AI

  37. 🕵🏻‍♂️ [InfoSec MASHUP] - This week's news cycle handed us the usual parade of breaches, arrests, and patch-your-stuff urgency — but if you squint at the #Malware section long enough, a more uncomfortable story emerges. #SAP-related npm packages backdoored with a credential stealer. A popular #PyPI package hijacked via a forged signed release pushed through a compromised GitHub Actions workflow. Seventy-three "sleeper" extensions quietly sitting in #OpenVSX, waiting. The common thread: attackers aren't breaking down the front door anymore. They're walking in through the tools developers use every day, often with a valid signature and a clean commit history.

    What makes this particularly fun — in the way a slow-motion disaster is fun — is that the blast radius isn't just the developer who ran pip install. It's every downstream user, every CI/CD pipeline, every AI coding agent that helpfully executed the preinstall hook without asking questions. The supply chain isn't a niche threat vector reserved for nation-state ops anymore. It's where commodity attackers are increasingly playing, because it scales beautifully and the detection gap remains embarrassingly wide.

    → Week #18/2026 also covers: Supply chain attackers found the path of least resistance, #OpenSSH patched a bug older than most junior devs, and #Europe is done pretending U.S. #cloud is a neutral choice.

    Full issue 👉 infosec-mashup.santolaria.net/

    If you find it useful, subscribe to get it in your inbox every weekend 📨 #infosecMASHUP #cybersecurity #infosec #threatintel #AI

  38. 🕵🏻‍♂️ [InfoSec MASHUP] - This week's news cycle handed us the usual parade of breaches, arrests, and patch-your-stuff urgency — but if you squint at the #Malware section long enough, a more uncomfortable story emerges. #SAP-related npm packages backdoored with a credential stealer. A popular #PyPI package hijacked via a forged signed release pushed through a compromised GitHub Actions workflow. Seventy-three "sleeper" extensions quietly sitting in #OpenVSX, waiting. The common thread: attackers aren't breaking down the front door anymore. They're walking in through the tools developers use every day, often with a valid signature and a clean commit history.

    What makes this particularly fun — in the way a slow-motion disaster is fun — is that the blast radius isn't just the developer who ran pip install. It's every downstream user, every CI/CD pipeline, every AI coding agent that helpfully executed the preinstall hook without asking questions. The supply chain isn't a niche threat vector reserved for nation-state ops anymore. It's where commodity attackers are increasingly playing, because it scales beautifully and the detection gap remains embarrassingly wide.

    → Week #18/2026 also covers: Supply chain attackers found the path of least resistance, #OpenSSH patched a bug older than most junior devs, and #Europe is done pretending U.S. #cloud is a neutral choice.

    Full issue 👉 infosec-mashup.santolaria.net/

    If you find it useful, subscribe to get it in your inbox every weekend 📨 #infosecMASHUP #cybersecurity #infosec #threatintel #AI

  39. 🕵🏻‍♂️ [InfoSec MASHUP] - This week's news cycle handed us the usual parade of breaches, arrests, and patch-your-stuff urgency — but if you squint at the #Malware section long enough, a more uncomfortable story emerges. #SAP-related npm packages backdoored with a credential stealer. A popular #PyPI package hijacked via a forged signed release pushed through a compromised GitHub Actions workflow. Seventy-three "sleeper" extensions quietly sitting in #OpenVSX, waiting. The common thread: attackers aren't breaking down the front door anymore. They're walking in through the tools developers use every day, often with a valid signature and a clean commit history.

    What makes this particularly fun — in the way a slow-motion disaster is fun — is that the blast radius isn't just the developer who ran pip install. It's every downstream user, every CI/CD pipeline, every AI coding agent that helpfully executed the preinstall hook without asking questions. The supply chain isn't a niche threat vector reserved for nation-state ops anymore. It's where commodity attackers are increasingly playing, because it scales beautifully and the detection gap remains embarrassingly wide.

    → Week #18/2026 also covers: Supply chain attackers found the path of least resistance, #OpenSSH patched a bug older than most junior devs, and #Europe is done pretending U.S. #cloud is a neutral choice.

    Full issue 👉 infosec-mashup.santolaria.net/

    If you find it useful, subscribe to get it in your inbox every weekend 📨 #infosecMASHUP #cybersecurity #infosec #threatintel #AI

  40. Masto besoin de conseil.
    Mon serveur #ssh me demande à chaque fois la passphrase de ma key. Doit y avoir un truc que je loupe. Un paramètre de ssh-config ou de sshd_config (je tourne avec #openssh

    le repouette me fait pousser la moustache !

    EDIT : résolue ! merci masto !