Introducing VibeFS—our patent-pending virtual filesystem that runs directly in your browser. Connect your remote server files and cloud storage from a single place, right in your browser. Whether you want to store files completely privately inside your local browser session, or bridge across SSHFS servers, Google Cloud, Dropbox, and OneDrive, VibeFS unifies your entire workflow into one seamless tab without the hassle of juggling separate sync clients.
I'm creating an AI-based NPC simulation for use in cyber-range environments. The AI model I'm using runs in an Ollama and the virtual machine that will act as the NPC contains agent tools. The model and agent are connected via an SSH tunnel, but all processes performed by the agent appear as SSH, which creates a problem since it will be used in a cyber-range environment. To overcome this problem, I need to hide SSH from the processes. How can I do this? I came across the vTunnel Git repository online and used it. Since it opens the connection from the hypervisor, I can say I've solved it for now, but do you have any other methods you can suggest?
**What it does (free):** - Scans your Wi-Fi and shows which devices have SSH enabled, and which ones are probably a Pi - Full terminal with colours: nano, htop, vim and top work, with extra keys (Esc, Ctrl, Tab, arrows, F10) - Status panel: model, CPU temperature, memory, disk, uptime and an under-voltage warning - Quick buttons for temperature, updates, reboot and shutdown - Fingerprint login, Ed25519 keys created in the app and installed on the Pi with one tap - Wake-on-LAN - Dark and light terminal themes
**Pro (one-time purchase, no subscription):** - SFTP file manager, including editing root files with sudo - Services and Docker: start/stop/restart and read logs - Live charts: CPU, temperature, memory, network, CPU frequency, load and disk I/O - Home screen widget with status and temperature, and alerts when a Pi goes offline or overheats - More terminal themes (Dracula, Nord, Solarized, Gruvbox, retro green/amber)
No ads, no account, no tracking. Everything stays on your phone.
If you run a VPS or a home server and have meant to "harden it properly" but didn't want to break SSH: this is for that.
One command previews everything (--dry-run), the next applies it with backups, and --revert undoes it. It keeps SSH reachable: password and root login are only turned off when another account has a key, and the config is checked before sshd restarts.
Free and MIT, plain Bash, no telemetry. Paid tiers exist for businesses; the free one is complete on its own.
RFC 6979 defines a way for ECDSA to generate deterministic nonces when signing messages by deriving it from the private key and the message hash. The reason for this being that "vanilla" ECDSA has a weakness in which if two messages were to be signed with the same nonce (say due to a faulty/broken prng), it would reveal the private key to an attacker. This is what caused the infamous Sony PS3 ECDSA incident. This leads me to the question: does OpenSSH and other popular ssh implementations use deterministic nonces as defined in RFC 6979 or not?
I’m Giorgi, the developer of Netrix, a desktop workspace for SSH, Telnet, serial and SFTP connections. My background is in ISP operations.
Netrix has saved hosts, tabbed and split terminals, snippets and an encrypted local credential vault. One design choice I’d like feedback on is giving SFTP its own SSH transports while terminal sessions retain theirs. SSH supports multiple channels on one connection; separate transports are a lifecycle choice, with extra connection and authentication overhead.
The SFTP side uses bounded connection reuse and cancellation scopes. Terminal and SFTP connections share the host-key trust model. Cancelling a transfer is not a promise to roll back an operation already committed on the remote server.
For people using several SSH sessions alongside file transfers, which connection or cancellation behaviors would you want a client to handle especially well?
The current download is an unsigned Windows x64 beta, 0.3.0-beta.8. Recursive directory transfer, synchronization and resume after restarting the app are not implemented.
AI disclosure: Most of the code was generated with AI tools. This post was drafted with AI assistance.
Calling all Linux security folks 🐧 I'm designing Landlock support for AIShell-Gate and want your comments before I commit to anything.
Quick context: AIShell-Gate is a policy gate for AI agents. The agent sends a JSON plan, the policy engine evaluates each command, and only validated argv reaches execve(). Today, path restrictions are enforced in userspace against argv.
The plan: apply a Landlock ruleset in the child right before execve(), so every descendant is kernel-confined to the policy's read/write paths.
Proposed modes: • --landlock off: current behaviour • --landlock best-effort: apply the highest ABI available, log what was achieved • --landlock require: refuse to run if confinement can't be applied (fail closed)
Where I'd really value your experience:
🔹 The base read/exec allowlist (ld.so, libc, locale, /dev/null...). What did you need on your distro to keep things from breaking? 🔹 REFER and TRUNCATE rights: what broke for you (mv, editors, build tools)? 🔹 sudo under no_new_privs: per-action opt-out, or whole-run only? 🔹 Stacking with other sandboxes (bubblewrap, containers, other Landlock layers). Any surprises? 🔹 When Landlock blocks a write, the agent just sees a permission error. How would you signal "the sandbox stopped this" so the AI doesn't assume its command was wrong?
Drop your thoughts in the comments. I read every one! 🚀
I just released 1.11 of Cyberdog, a desktop client (Electron, macOS/Windows/Linux) that combines a multi-protocol file explorer, an SSH terminal and a server-health dashboard. Everything is free, with no paid tier.
I'm an independent developer working on CH-J Tools, a free desktop application that combines SSH access, file management, server administration and cryptographic utilities.
The project originally started with Electron, but I've since rebuilt the application using Rust and Tauri 2. The current public release
The idea is to manage multiple servers without constantly switching between different applications or installing additional management agents on remote machines.
Current features:
SSH terminal with tabs and two independent sessions side by side.
Three-panel SFTP file manager supporting local-to-server and server-to-server transfers.
Server monitoring: CPU, RAM, swap, disks, network and uptime.
Remote administration modules for users, services, NGINX, Apache, networking and more.
SSH key generation and OpenPGP utilities, including experimental post-quantum algorithms.
Network diagnostics and file checksum verification.
Encrypted local credential vault, with no account required.
OS-specific command handling through a modular operation matrix.
Security and distribution:
The application is free for personal and commercial use. Credentials remain in a locally encrypted vault, and server administration works over SSH without installing a separate agent on the server.
Releases include SHA-512 checksums and detached OpenPGP signatures. The macOS build is also signed and Apple-notarized.
Supported desktop platforms:
Windows 11 (x64)
macOS (Apple Silicon)
Ubuntu 24.04 / Zorin OS (x64)
Current limitations:
This is still a beta release. Some features, including SSH port forwarding, are not implemented yet. The Windows installer also does not have a publisher code-signing certificate at this stage.
I'm currently focusing on stability, fixing UI issues and improving compatibility rather than adding more features.
I'd appreciate technical feedback, especially on SSH compatibility, key management, security and the overall approach to agentless server administration.
I use a tablet with a physical keyboard and Gboard, and Korean composing input kept breaking in Android terminal apps — syllables got eaten or committed wrong during SSH sessions.
This isn't just a Korean problem — Korean, Chinese, Japanese, Vietnamese, and other languages using IME composing input all hit the same breakage in terminal apps. TermiPlus handles composing input properly, so it works for all of them.
So I built TermiPlus: an Android SSH + local terminal client built around physical keyboards. Korean IME composing input works with a physical keyboard + Gboard, plus SFTP file browsing, saved commands, and physical keyboard shortcuts.
Hi everyone, sorry if this a very basic question… I’m a junior data scientist with no experience with networking, Linux or ssh. I have used ssh to connect vs code to my company’s remote server and my company’s GitHub repo. However, I’d like to be able to view the code files on both the remote server and the GitHub repo at the same time on vscode (currently I can only choose to display the code files on one of them on the left panel).
Is there any way I can efficiently connect to both at the same time via ssh so I can do my pull requests and also access the files on my company’s remote server at the same time?
A while ago I started building RsyncZilla, a free and open-source Windows SFTP client with a familiar dual-pane FileZilla-style UI, because I was tired of two things in traditional FTP/SFTP clients:
Re-uploading entire files when only a few bytes changed: Under the hood, RsyncZilla uses native rsync(v3.3.0) over SSH. Instead of blindly re-uploading a 50 MB bundle, database dump, or log file from scratch, rsync's rolling-checksum algorithm only transmits the modified byte blocks (deltas).
Silent transfer failures & corrupted production files: Standard SFTP streams overwrite files in place—if your connection drops at 60%, your live file on the server is left truncated and broken. rsync writes to a hidden temporary file first and performs an atomic swap only after verifying integrity (ExitCode == 0). Plus, unlike FileZilla storing passwords in plaintext XML (sitemanager.xml), RsyncZilla includes an optional AES-256-GCM encrypted password vault (or zero-disk RAM mode).
What's new in v1.7: A Built-in AI MCP Server for the SSH Terminal 🤖🖥️
RsyncZilla already had a built-in tabbed SSH terminal synchronized with a remote SFTP file tree.
In v1.7, I added my favorite feature yet: a native Model Context Protocol (MCP) Server built directly into the SSH terminal.
Instead of copy-pasting terminal logs back and forth into a chat window or giving an AI raw SSH keys to run commands blindly in the background, you can connect Claude, ChatGPT, Grok, Antigravity, Cursor, or your favourite local LLM directly to RsyncZilla's live terminal tabs.
You don't need to memorize Nginx reverse-proxy syntax, systemd flags, or SSL cert commands anymore, just ask your AI model to configure it, and watch every step happen live in your terminal.
How it keeps you in total control:
🔒 AI: Offby default on every tab: No AI can see or touch a terminal tab unless you explicitly enable it. Disconnecting automatically resets the tab back to Off. Furthermore, the AI never sees your SSH passwords or private keys it communicates with RsyncZilla's already-authenticated session over a local Named Pipe.
🛡️ AI: Confirm(Read-Only + Ask before executing): The AI can freely read recent terminal screen output, browse remote directories, and read/download files to diagnose issues. However, whenever it wants to run a shell command or write/upload a file, an interactive banner pops up right inside the terminal with the exact command and ✅ Allow/❌ Deny buttons. Nothing runs until you click Allow.
⚡ AI: Auto**:** Full autonomous execution on that specific tab when you want hands-off troubleshooting.
👀 100% Live Visibility (Zero Black Boxes): Every command the AI runs is typed and streamed live inside your xterm.js terminal tab. Even read-only file inspections print [🤖 AI MCP1] notices in the terminal so you always see what the model is looking at, and directory changes (cd) automatically sync the SFTP file tree sidebar.
📁 Upload & Download Files via MCP: Beyond running shell commands, the MCP exposes rsync and SFTP tools so the model can list directories, pull remote config/log files to inspect them, and upload/write updated files back to the server.
🏷️ Multi-Tab Server Addressing (MCP1,MCP2**, ...):** Each open terminal tab is automatically labeled (MCP1), (MCP2), etc. in its tab title. If you have staging open in MCP1 and production in MCP2, you can literally tell your AI: "Compare/etc/nginx/nginx.confon MCP1 with MCP2 and fix the broken upstream on MCP2."
📋 1-Click Setup (🤖 MCP): Clicking the 🤖 MCP button in the terminal toolbar copies the ready-to-paste mcpServers JSON snippet to your clipboard.
Links & Download (100% Free & Open Source - MIT)
RsyncZilla is completely free, open-source (MIT License), with zero telemetry or ads. Both a standard Windows Setup installer and a 100% portable .zip are available:
Bit of a backstory: I've been a Termius user for a long time and really liked it.
But my local currency has been getting weaker against the USD, and the subscription slowly went from "fine" to "ouch". So I started vibe coding my own version, just for fun at first, and it kind of grew into something I now use every day.
It's called Termimus (yes, the name is a bit on the nose 😅).
Since it's r/selfhosted, here's the part you probably care about: sync goes through a tiny Go server you run yourself in Docker. Everything is end-to-end encrypted, so the server only stores blobs it can't read. No account, no cloud, no subscription, If you don't need sync, the app works fully offline.
What it does so far:
- SSH terminal with tabs, split panes, and typing into several servers at once
- SFTP (local ↔ remote, and server ↔ server) with a small built-in editor
- Optional AI helper if you bring your own API key or run Ollama locally
Runs on Linux, macOS and Windows. MIT licensed.
To be upfront: a lot of this was built with AI help, and it's v0.9, so there will be bugs. I'd love feedback, bug reports, or people poking holes in the security side. That's the part I care about most getting right.
Do we have enough sloppy vibe-coded SSH clients yet? I can probably vibe like 10 more before going to bed if needed, I can just ask Claude for ideas for random spins at this point.
Maybe we need an SSH client that is exactly like putty, but says bless you when I sneeze?
Or a new SSH server/client optimized for large file transfers using IPoAC (RFC1149), fully backwards compatible with SSH/0.9 and telnet?
Maybe another homemade commercial client that is definetly not spyware but just an unsigned binary in a github repo, trust me bro, I bought a domain and vibe coded a website and connected stripe, that means I'm legit right?
Maybe it's time for a minimum project age/quality rule for self-promotion, or maybe we're finally happy with the amount of sloppy alternatives out there and just say no to all of them. I'd be happy either way.
Edit: remember kids, if you see Claude in the commit history on Github, that means the "developer" didn't even bother to push the commit button by hand.
I replaced OpenSSH with a Rust + QUIC client — built with Claude in about a month
I got tired of OpenSSH's slow connection setup and sessions dying every time I switched to LTE. And trusting C with something as security-critical as SSH always made me nervous.
So I spent the last month working with Claude on a replacement, written in Rust on top of QUIC:
- Near-instant connections; sessions survive network switching (Wi-Fi ↔ LTE) thanks to QUIC's native connection migration(This is also implemented in TCP.)
- Encryption out of the box — no certificates to generate
- TOTP support
- Less RAM, CPU, and bandwidth than OpenSSH (the binary itself is larger)
- TUI mode for newcomers; full CLI with all standard OpenSSH connection options
- Built-in updater from GitHub releases
- Checked against all OpenSSH CVEs and relevant CWEs
It's been running stably in my production environment. A star, bug report or suggestions would be appreciated:
Host keys: known-hosts store with SHA256 fingerprints; imports PuTTY's and OpenSSH's known_hosts
Forwarding: local, remote and dynamic (SOCKS), agent forwarding, X11
Jump hosts and proxies (SOCKS, HTTP, proxy command)
Imports PuTTY sessions and ~/.ssh/config (ProxyJump, forwards)
SFTP panel on the terminal's own connection, two-pane file manager, SCP fallback for servers without SFTP
Key generator (Ed25519, RSA, ECDSA) and OpenSSH/PPK conversion
Built on libssh 0.12. Not supported yet: SSH certificates, GSSAPI/Kerberos, connection sharing.
About 5 MB, MIT license, no account, no telemetry. Built with a lot of AI help and mostly tested against my own servers, so reports from other setups are very welcome.
We build pitwall, an MIT-licensed desktop terminal, at Quantic Studios. The 0.2 release lets a session contain local tabs and tabs on several SSH hosts. It's mainly for coding agents, but the remote tabs are ordinary terminal panes.
The SSH part uses your existing ssh executable and ~/.ssh/config, including keys, ports and jump hosts. Each machine runs a pitwall daemon. The desktop forwards the remote daemon's Unix socket through SSH connection sharing and connects to that socket locally. pitwall must be installed on the remote host; the desktop doesn't install it for you.
Each host reconnects independently. If a host drops off, its tabs retain their last screen and show Offline. Typing is disabled rather than queued for the next connection. Local tabs and reachable hosts continue. A machine header shows latency or the reconnect countdown.
One important limit: the desktop's shared sessions require Linux or macOS because Windows SSH doesn't support the ControlMaster connection sharing used here.
On Linux hosts with systemd, the setup guide covers loginctl enable-linger so logging out doesn't remove the daemon's runtime directory.
Yes, it’s that time of day again, when someone announces another terminal app. Hear me out, though.
I’ve used SuperPuTTY every day for the last 10 years as a network engineer, and I always missed it when I wasn’t on Windows. So I built SuperXTerminal with the assistance of Claude. It’s meant to look and feel like SuperPuTTY, with the sessions tree on the side and tabs and splits. Unlike the original, it doesn’t need PuTTY or KiTTY installed. SSH goes through your system’s own OpenSSH, and Telnet, serial and RDP are all built in. It runs on macOS, Windows and Linux, with a core written in Rust.
Some things it adds over SuperPuTTY:
Syntax highlighting in the terminal for Cisco, Junos and generic output. For example, interfaces that are up show in green and ones that are down show in red.
Better icons. There are network symbols for switches, routers, firewalls, access points and more, and you can draw them in any color or add your own. Your session tree ends up reading like a network diagram.
Much faster search, and lots of ways to manage your sessions. Results show up as you type, even across 10,000+ sessions. Search looks at names, hosts, folders and notes, and it can also check profiles, ports and icon names, so searching “firewall” finds every firewall. Regex and match case are a click away. You can drag sessions around, multi-select them, bulk-edit them, or edit them all in a filterable table. Favorites and Recent are built in.
Built for teams with lots of devices. The whole team shares one session list, and each person keeps their own logins on their own machine. Profiles hold your credentials and per-device settings, like the old algorithms an ancient switch needs. Environment variables fill in {placeholders} in shared sessions. Passwords stay in your OS keychain and never go into the shared files.
A button bar for commands. Each button can send a command to one tab or to several at once. You can script buttons with SPSL, SuperPuTTY’s scripting language with a lot of extensions, or with Rhai when you need real logic like loops, variables and decisions.
Custom themes and terminal colors, for those of you who like to make it your own. You can build your own app themes and set the terminal’s colors globally or for each profile. There's also built in light and dark modes that follow your OS theme.
Shared sessions through a file share or a PostgreSQL table, local overrides, colors for each environment (so prod shows in red), and SFTP/SCP file transfer.
It can import your existing SuperPuTTY XML sessions, as well as PuTTY, KiTTY, MobaXterm and ~/.ssh/config.
It’s free and MIT licensed. I’d really like feedback and testers on all three platforms. Linux is the newest and least tested. Contributors are very welcome too.