Gamedev Mastodon

tjhowseTIL of a deliberate source of Heisenbugs in the default sshd config:MaxStartups 5:50:10This means: Allow up to 5 simultaneous "starting" SSH connections. Between 5 and 10 starting connections, drop them randomly 50% of the time. Above 10: Do not allow any new SSH connections to start.Took me a long time to diagnose why a particular combination of concurrent SSH processes would fail occasionally when connecting to this embedded machine.<a href="https://www.simplified.guide/ssh/limit-simultaneous-connections" rel="nofollow noopener noreferrer" target="_blank">https://www.simplified.guide/ssh/limit-simultaneous-connections</a><a href="https://howse.social/tags/sshd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sshd</a> <a href="https://howse.social/tags/ansible" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ansible</a> <a href="https://howse.social/tags/swdev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#swdev</a>

Peter N. M. HansteenSo this happened:Jan 30 03:07:16 skapet sshd-session[94311]: Failed password for invalid user "> from 165.231.182.56 port 15613 ssh2I wonder if we are seeing a variant of "gropefor database down, feeding raw html to the ssh gropebot" scenario again such as in <a href="https://nxdomain.no/~peter/so_somebody_is_throwing_html_at_your_sshd.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://nxdomain.no/~peter/so_somebody_is_throwing_html_at_your_sshd.html</a> <a href="https://mastodon.social/tags/sshgropers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sshgropers</a> <a href="https://mastodon.social/tags/sshd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sshd</a> <a href="https://mastodon.social/tags/passwordguessing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#passwordguessing</a> <a href="https://mastodon.social/tags/passwordgroping" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#passwordgroping</a> <a href="https://mastodon.social/tags/passwords" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#passwords</a> <a href="https://mastodon.social/tags/cybercrime" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cybercrime</a>

:rss: Qiita - 人気の記事XZ Utils backdoor (CVE-2024-3094) 解説 <a href="https://qiita.com/naokiwa/items/203f558f5dd2a999b862?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://qiita.com/naokiwa/items/203f558f5dd2a999b862?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items</a><a href="https://rss-mstdn.studiofreesia.com/tags/qiita" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#qiita</a> <a href="https://rss-mstdn.studiofreesia.com/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://rss-mstdn.studiofreesia.com/tags/xz" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#xz</a> <a href="https://rss-mstdn.studiofreesia.com/tags/sshd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sshd</a> <a href="https://rss-mstdn.studiofreesia.com/tags/autotools" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#autotools</a> <a href="https://rss-mstdn.studiofreesia.com/tags/lzma" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#lzma</a>

WesMasonToday I did a writeup on a ssh client I love and adore. It's a cross platform (big 3) graphical client and I enjoy it as a replacement for WSL on windows and still give me a familiar view on Linux too.But today's writeup was a bug report on the replaced ssh engine they put in the past week. Ssh keys are still broken for me and I discovered a few other things too along my investigation. It was a somewhat length dive for a github issue, but I hope it is well received, especially if it helps fix more issues. <a href="https://lifergeek.social/tags/ssh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ssh</a> <a href="https://lifergeek.social/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://lifergeek.social/tags/sshd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sshd</a> <a href="https://lifergeek.social/tags/github" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#github</a> <a href="https://lifergeek.social/tags/opensource" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#opensource</a>

Ariel (🐿 arc)Bizarre OpenSSH/PAM/Nix-Home-Manager issues today. Looks like the daemon or PAM is refusing to acknowledge the symlink in `~/.nix-profile/bin/zsh` and so blocking SSH login.It's also throwing bad password errors but I tried pasting the string in both `sudo passwd $USER` and the SSH password prompt.`StrictModes=no` didn't have any positive affect.User is working just fine otherwise, `/etc/shells` contains the location which matches `getent passwd`, symlink in `~/.nix-profile/bin/zsh` to the store is valid...<a href="https://eigenmagic.net/tags/OpenSSH" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSSH</a> <a href="https://eigenmagic.net/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a> <a href="https://eigenmagic.net/tags/Nix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Nix</a> <a href="https://eigenmagic.net/tags/NixOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NixOS</a> <a href="https://eigenmagic.net/tags/SSH" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSH</a> <a href="https://eigenmagic.net/tags/sshd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sshd</a> <a href="https://eigenmagic.net/tags/HomeManager" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HomeManager</a>

jfmblinux :jeditux:Ah ouais !!! 🤔 80.67.164.12 2001.910.1400.115.12 <a href="https://toot.aquilenet.fr/@yunohost" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@yunohost</a> ça me surprend de voir ça 🤔<a href="https://mastodon.jfmblinux.fr/tags/fail2ban" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fail2ban</a> <a href="https://mastodon.jfmblinux.fr/tags/Postfix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Postfix</a> <a href="https://mastodon.jfmblinux.fr/tags/sshd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sshd</a> <a href="https://mastodon.jfmblinux.fr/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a> <a href="https://mastodon.jfmblinux.fr/tags/SSH" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSH</a> <a href="https://mastodon.jfmblinux.fr/tags/Hacker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Hacker</a>

dexternemrodAnd again it was an "include" in the sshd_config that caused some trouble. Still impressive how fast the bad login attempts accumulate on a fresh ip. <a href="https://troet.cafe/tags/ssh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ssh</a> <a href="https://troet.cafe/tags/sshd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sshd</a>

Peter N. M. Hansteensshd(8) splitting continues <a href="https://www.undeadly.org/cgi?action=article;sid=20241014070554" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.undeadly.org/cgi?action=article;sid=20241014070554</a> <a href="https://mastodon.social/tags/openbsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openbsd</a> <a href="https://mastodon.social/tags/openssh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openssh</a> <a href="https://mastodon.social/tags/ssh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ssh</a> <a href="https://mastodon.social/tags/sshd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sshd</a> <a href="https://mastodon.social/tags/sshd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sshd</a>-auth <a href="https://mastodon.social/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a> <a href="https://mastodon.social/tags/authentication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#authentication</a>

Jonathan KamensAnother vestige of <a href="https://federate.social/tags/Ubuntu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ubuntu</a> from desktops that I recently switched to <a href="https://federate.social/tags/Debian" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Debian</a>, gone… A while ago Ubuntu decided <a href="https://federate.social/tags/sshd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sshd</a> should run as a <a href="https://federate.social/tags/systemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#systemd</a> socket instead of a service. I didn't like the change but didn't want to diverge from "standard" so I switched. But sometimes you have to ssh into a machine 2 or 3 times before it works, and when you upgrade systemd remotely the sshd socket can break and lock you out of the machine. I just switched back to using Debian standard ssh.service. 🎉 <a href="https://federate.social/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a>

Julius Kaiser"In a recent commit, Damien Miller (djm@) introduced the new sshd(8) configurations options, PerSourcePenalties and PerSourcePenaltyExemptList, to provide a built in facility in sshd(8) itself to penalize undesirable behavior, and to shield specific clients from penalty, respectively. "<a href="https://undeadly.org/cgi?action=article;sid=20240607042157" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://undeadly.org/cgi?action=article;sid=20240607042157</a><a href="https://mastodon.online/tags/ssh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ssh</a> <a href="https://mastodon.online/tags/sshd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sshd</a> <a href="https://mastodon.online/tags/sysadmin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sysadmin</a> <a href="https://mastodon.online/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a> <a href="https://mastodon.online/tags/openbsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openbsd</a> <a href="https://mastodon.online/tags/selfhosted" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosted</a> <a href="https://mastodon.online/tags/selfhosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selfhosting</a>

Liera :trans_furr_white: :drgn_flag_rainbow:Don't forget to update your server if you're running a SSH server! Article below gives what versions are affected by this vulnerability :blobfoxcomfycomputer: <a href="https://www.qualys.com/regresshion-cve-2024-6387/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.qualys.com/regresshion-cve-2024-6387/</a><a href="https://tech.lgbt/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a> <a href="https://tech.lgbt/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://tech.lgbt/tags/ssh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ssh</a> <a href="https://tech.lgbt/tags/sshd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sshd</a> <a href="https://tech.lgbt/tags/server" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#server</a>

steve mookie kongUpdate your ssh server.<a href="https://nvd.nist.gov/vuln/detail/CVE-2024-6387" rel="nofollow noopener noreferrer" target="_blank">https://nvd.nist.gov/vuln/detail/CVE-2024-6387</a><a href="https://mookiesplace.com/tags/infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#infosec</a> <a href="https://mookiesplace.com/tags/ssh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ssh</a> <a href="https://mookiesplace.com/tags/sshd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sshd</a>

Greg SlepakJust noticed that <a class="u-url mention" href="https://fosstodon.org/@fedora" rel="nofollow noopener noreferrer" target="_blank">@fedora</a> doesn't have the fix for the latest serious <a class="hashtag" href="https://crib.social/tag/ssh" rel="nofollow noopener noreferrer" target="_blank">#ssh</a> exploit yet. Anyone know when the fix will make it in? <a href="https://news.ycombinator.com/item?id=40843778" rel="nofollow noopener noreferrer" target="_blank">https://news.ycombinator.com/item?id=40843778</a> <a class="hashtag" href="https://crib.social/tag/regresshion" rel="nofollow noopener noreferrer" target="_blank">#regresshion</a> <a class="hashtag" href="https://crib.social/tag/linux" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a class="hashtag" href="https://crib.social/tag/fedora" rel="nofollow noopener noreferrer" target="_blank">#fedora</a> <a class="hashtag" href="https://crib.social/tag/sshd" rel="nofollow noopener noreferrer" target="_blank">#sshd</a> <a class="hashtag" href="https://crib.social/tag/openssh" rel="nofollow noopener noreferrer" target="_blank">#openssh</a> /cc <a class="u-url mention" href="https://mastodon.social/@decathorpe" rel="nofollow noopener noreferrer" target="_blank">@decathorpe</a>

Jan Lehnardt :couchdb:PSA: if you run a macOS Server (or just have “remote login” enabled in the Sharing pref pane) and want to protect against CVE-2024-6387, do update sshd_config as documented and you’re done. No need to restart sshd (and drop your connections / screen sharing port forwards) because on macOS launchd forks a new sshd process for each incoming connection. ✌️<a href="https://narrativ.es/tags/sshd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sshd</a> <a href="https://narrativ.es/tags/macOSAdmin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#macOSAdmin</a> <a href="https://narrativ.es/tags/macOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#macOS</a>

Anarchozionist/DatenproletUpdatet eure <a href="https://chaos.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Linux</a>-Systeme!<a href="https://blog.qualys.com/vulnerabilities-threat-research/2024/07/01/regresshion-remote-unauthenticated-code-execution-vulnerability-in-openssh-server" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://blog.qualys.com/vulnerabilities-threat-research/2024/07/01/regresshion-remote-unauthenticated-code-execution-vulnerability-in-openssh-server</a><a href="https://chaos.social/tags/openssh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openssh</a> <a href="https://chaos.social/tags/ssh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ssh</a> <a href="https://chaos.social/tags/sshd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sshd</a>

John Leonard'Critical' vulnerability in OpenSSH uncovered, affects almost all Linux systems14 million internet-facing servers are vulnerable, says Qualys<a href="https://www.computing.co.uk/news/4329906/critical-vulnerability-openssh-uncovered-affects-linux-systems" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.computing.co.uk/news/4329906/critical-vulnerability-openssh-uncovered-affects-linux-systems</a><a href="https://mastodon.social/tags/openssh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openssh</a> <a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a> <a href="https://mastodon.social/tags/sshd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sshd</a> <a href="https://mastodon.social/tags/qualys" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#qualys</a> <a href="https://mastodon.social/tags/vulnerability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#vulnerability</a> <a href="https://mastodon.social/tags/infosec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#infosec</a> <a href="https://mastodon.social/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cybersecurity</a>

Lutra SecurityDo you use OpenSSH?This is a retorical question, of course you use OpenSSH. The TODO for today is: Update sshd!⚠️CVE-2024-6387 - regreSSHion: RCE in OpenSSH's server, on glibc-based Linux systems<a href="https://www.qualys.com/2024/07/01/cve-2024-6387/regresshion.txt" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.qualys.com/2024/07/01/cve-2024-6387/regresshion.txt</a><a href="https://infosec.exchange/tags/sshd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sshd</a> <a href="https://infosec.exchange/tags/regreSSHion" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#regreSSHion</a> <a href="https://infosec.exchange/tags/CVE20246387" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CVE20246387</a>

Peter N. M. HansteenOpenSSH 9.8 released <a href="https://www.undeadly.org/cgi?action=article;sid=20240701102851" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.undeadly.org/cgi?action=article;sid=20240701102851</a> <a href="https://mastodon.social/tags/openbsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openbsd</a> <a href="https://mastodon.social/tags/openssh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openssh</a> <a href="https://mastodon.social/tags/ssh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ssh</a> <a href="https://mastodon.social/tags/sshd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sshd</a> <a href="https://mastodon.social/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a> <a href="https://mastodon.social/tags/crypto" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#crypto</a> <a href="https://mastodon.social/tags/encryption" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#encryption</a>

R. L. Dane :debian: :openbsd:<a href="https://fosstodon.org/tags/TIL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TIL</a> I learned that <a href="https://fosstodon.org/tags/Termux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Termux</a> (<a href="https://fosstodon.org/tags/Android" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Android</a> terminal/shell) has its own <a href="https://fosstodon.org/tags/sshd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#sshd</a>, and it's freaking perfrect.

DansLeRuSH ᴱᶰUseful against attempts to exploit <a href="https://floss.social/tags/SSHD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SSHD</a> :« <a href="https://floss.social/tags/OpenSSH" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenSSH</a> introduces options to penalize undesirable behavior […] In a recent commit, Damien Miller (<a href="https://cybervillains.com/@djm" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@djm</a>) introduced the new SSHD configurations options, "PerSourcePenalties" and "PerSourcePenaltyExemptList", to provide a built in facility in SSHD itself to penalize undesirable behavior, and to shield specific clients from penalty, respectively »› <a href="https://undeadly.org/cgi?action=article;sid=20240607042157" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://undeadly.org/cgi?action=article;sid=20240607042157</a> <a href="https://floss.social/tags/InfoSec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#InfoSec</a> <a href="https://floss.social/tags/Security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Security</a> <a href="https://floss.social/tags/Exploit" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Exploit</a>

Recent searches

Search options

Administered by:

Server stats:

#sshd