Le Pouls Du Monde

Stéphane KleinQuand je ne peux pas utiliser `scp -r root@myserver:/foobar/ ./`, voici une méthode shell pour upload / download avec ssh, tar et sudo :<a href="https://notes.sklein.xyz/2025-04-02_1648/" rel="nofollow noopener" translate="no" target="_blank">https://notes.sklein.xyz/2025-04-02_1648/</a><a href="https://social.coop/tags/ssh" class="mention hashtag" rel="nofollow noopener" target="_blank">#ssh</a> <a href="https://social.coop/tags/unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#unix</a> <a href="https://social.coop/tags/tips" class="mention hashtag" rel="nofollow noopener" target="_blank">#tips</a> <a href="https://social.coop/tags/scp" class="mention hashtag" rel="nofollow noopener" target="_blank">#scp</a>

BillyAny idea why xon/xoff flow control would suddenly become enabled? I am working on a remote Ubuntu host, and suddenly ctrl-s is borderline malicious. I use emacs, and I don't even think about ctrl-s before I do it, so the xon/xoff flow control is very disruptive. The machine uptime is 18 days, and this has happened in the last hour. I haven't messed with any network config. I guess a system administrator could have updated packages. Could that have enabled xon/xoff flow control?<a href="https://mountains.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://mountains.social/tags/flowcontrol" class="mention hashtag" rel="nofollow noopener" target="_blank">#flowcontrol</a> <a href="https://mountains.social/tags/xon" class="mention hashtag" rel="nofollow noopener" target="_blank">#xon</a> <a href="https://mountains.social/tags/xoff" class="mention hashtag" rel="nofollow noopener" target="_blank">#xoff</a> <a href="https://mountains.social/tags/emacs" class="mention hashtag" rel="nofollow noopener" target="_blank">#emacs</a> <a href="https://mountains.social/tags/uptime" class="mention hashtag" rel="nofollow noopener" target="_blank">#uptime</a> <a href="https://mountains.social/tags/ssh" class="mention hashtag" rel="nofollow noopener" target="_blank">#ssh</a>

stibIf I have a <a href="https://aus.social/tags/codeberg" class="mention hashtag" rel="nofollow noopener" target="_blank">#codeberg</a> account set up, with a verified <a href="https://aus.social/tags/ssh" class="mention hashtag" rel="nofollow noopener" target="_blank">#ssh</a> key on my account and the corresponding public and private keys in `~/.ssh/`, is there a way that I can make it so that it doesn't ask me for my keyphrase every time I push? I'm sure VSCode could do this, but since I've switched to <a href="https://aus.social/tags/Helix" class="mention hashtag" rel="nofollow noopener" target="_blank">#Helix</a>, which doesn't have git built-in I've been manually doing the git stuff. My knowledge of <a href="https://aus.social/tags/cryptography" class="mention hashtag" rel="nofollow noopener" target="_blank">#cryptography</a> and <a href="https://aus.social/tags/git" class="mention hashtag" rel="nofollow noopener" target="_blank">#git</a> are well and truly at the 'barely enough to get myself into trouble' level. <a href="https://aus.social/tags/AskFedi" class="mention hashtag" rel="nofollow noopener" target="_blank">#AskFedi</a>

Jérémy LecourIntéressante technique pour l’authentification <a href="https://mastodon.evolix.org/tags/SSH" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSH</a> basée sur des clés récupérées dynamiquement : <a href="https://jpmens.net/2025/03/25/authorizedkeyscommand-in-sshd/" rel="nofollow noopener" translate="no" target="_blank">https://jpmens.net/2025/03/25/authorizedkeyscommand-in-sshd/</a> <a href="https://mastodon.evolix.org/tags/sysadmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#sysadmin</a>

AzureCerulean### <a href="https://4bear.com/tags/Cloudflare" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cloudflare</a> open sources <a href="https://4bear.com/tags/OPKSSH" class="mention hashtag" rel="nofollow noopener" target="_blank">#OPKSSH</a> to bring Single Sign-On <a href="https://4bear.com/tags/SSO" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSO</a> to <a href="https://4bear.com/tags/SSH" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSH</a>This week, it was officially open-sourced under the umbrella of the <a href="https://4bear.com/tags/OpenPubkey" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenPubkey</a> project, itself became a <a href="https://4bear.com/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> Foundation open-source initiative in 2023, OPKSSH remained closed-source until now. Making it easy to <a href="https://4bear.com/tags/authenticate" class="mention hashtag" rel="nofollow noopener" target="_blank">#authenticate</a> to <a href="https://4bear.com/tags/servers" class="mention hashtag" rel="nofollow noopener" target="_blank">#servers</a> over SSH using <a href="https://4bear.com/tags/OpenID" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenID</a> Connect (<a href="https://4bear.com/tags/OIDC" class="mention hashtag" rel="nofollow noopener" target="_blank">#OIDC</a>), allowing developers to ditch manually configured SSH keys in favor of identity provider-based access.<a href="https://www.helpnetsecurity.com/2025/03/28/opkssh-sso-ssh/" rel="nofollow noopener" translate="no" target="_blank">https://www.helpnetsecurity.com/2025/03/28/opkssh-sso-ssh/</a>

MichaelIt will never not bother me that the "port" parameter for SSH is lower-case -p while for SCP it's upper-case -PThis is the kind of annoying crap I expect from Microsoft, not Unix<a href="https://mastodon.world/tags/unix" class="mention hashtag" rel="nofollow noopener" target="_blank">#unix</a> <a href="https://mastodon.world/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://mastodon.world/tags/ssh" class="mention hashtag" rel="nofollow noopener" target="_blank">#ssh</a> <a href="https://mastodon.world/tags/scp" class="mention hashtag" rel="nofollow noopener" target="_blank">#scp</a> <a href="https://mastodon.world/tags/arrrgh" class="mention hashtag" rel="nofollow noopener" target="_blank">#arrrgh</a>

JP MensA few words on SSH public keys read from AuthorizedKeysFile(s) and obtained programmatically from OpenSSH's AuthorizedKeysCommand program.<a href="https://jpmens.net/2025/03/25/authorizedkeyscommand-in-sshd/" rel="nofollow noopener" translate="no" target="_blank">https://jpmens.net/2025/03/25/authorizedkeyscommand-in-sshd/</a><a href="https://mastodon.social/tags/ssh" class="mention hashtag" rel="nofollow noopener" target="_blank">#ssh</a> <a href="https://mastodon.social/tags/openssh" class="mention hashtag" rel="nofollow noopener" target="_blank">#openssh</a>

Martin<a href="https://mstdn.social/users/rysiek" class="u-url mention" rel="nofollow noopener" target="_blank">@rysiek@mstdn.social</a> I have long random passwords generated by <a href="https://social.mdosch.de?t=pass" class="mention hashtag" rel="nofollow noopener" target="_blank">#pass</a>. Those are <a href="https://social.mdosch.de?t=pgp" class="mention hashtag" rel="nofollow noopener" target="_blank">#pgp</a> encrypted and synced via <a href="https://social.mdosch.de?t=ssh" class="mention hashtag" rel="nofollow noopener" target="_blank">#ssh</a> and version controlled by <a href="https://social.mdosch.de?t=git" class="mention hashtag" rel="nofollow noopener" target="_blank">#git</a>. I never switched to passkeys. For <a href="https://social.mdosch.de?t=xmpp" class="mention hashtag" rel="nofollow noopener" target="_blank">#xmpp</a> I use <a href="https://social.mdosch.de?t=fast" class="mention hashtag" rel="nofollow noopener" target="_blank">#fast</a> which is sort of the same as passkey. <a href="https://relay.infosec.exchange/actor" class="u-url mention" rel="nofollow noopener" target="_blank">@relay@relay.infosec.exchange</a>

Recent searches

Search options

Administered by:

Server stats:

#ssh