How to Diagnose and Fix SSH 'Permission Denied (publickey)' Errors

·2 views

The SSH error 'Permission denied (publickey)' signals that every key the client offered was rejected by the server during authentication negotiation, not a simple password mistake. Developers can diagnose the issue using 'ssh -vvv' on the client side and server logs via 'journalctl -u ssh' to identify which keys were offered and why they were refused. The four main causes are connecting as the wrong user, the public key missing from the target account's authorized_keys file, overly open file permissions causing the client to silently skip the key, and legacy ssh-rsa keys being rejected by OpenSSH 8.8 and later versions. OpenSSH 8.8, released in October 2021, disabled SHA-1-based ssh-rsa signatures by default, meaning older RSA keys from CI systems or devices like Raspberry Pis may silently fail. Regenerating keys using the ed25519 algorithm and using ssh-copy-id to install them correctly prevents most recurring authentication failures.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

How SaaS Teams Can Build CSV Exports That Are Actually Useful to Customers

A practical guide published on DEV Community by developer Uriel Bitto outlines best practices for designing CSV exports in SaaS products. The guide emphasizes scoping exports to a specific user job, using clear column headers, and including stable record IDs so files remain useful outside the app. It recommends using established CSV libraries rather than manual string-joining, and testing output in the tools customers actually use, such as spreadsheets. Security concerns like CSV injection are also highlighted, with advice to apply access controls and sanitize untrusted values based on the intended destination. The core benchmark proposed is whether a customer can open the file, understand its contents, and complete their task without needing the app open beside them.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer builds TikTok downloader, shares lessons on streaming and expiring URLs

A developer recently built a web service called FromTik that allows users to download public TikTok videos, slideshows, and audio files. Rather than saving full video files to disk before delivery, the service streams media in chunks directly from TikTok's CDN to the user, reducing disk usage and speeding up downloads. The developer avoided unnecessary re-encoding with FFmpeg, reserving it only for tasks like extracting MP3 audio or converting slideshows into video. A key technical insight was that TikTok CDN URLs are short-lived and signed, making long-term caching of extracted links unreliable. The article outlines how treating media metadata as request-specific rather than permanently stored leads to a more dependable architecture.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

OpenBot enforces audit logging before any bot action executes, not after

OpenBot, an open-source agent framework described as a template rather than a finished product, routes every bot action through a single gateway that evaluates policy and writes an audit record before the action is carried out. The system uses CEL-based rules to inspect tool names, file paths, shell commands, and other parameters, and is designed to fail closed — a missing or broken policy blocks rather than permits. Sensitive data such as secrets are partially obscured in logs, recording only that a request was made and the length of the value, not its contents. Human takeovers during bot sessions — such as handling login walls or two-factor prompts — are also logged, and bot actions are refused rather than queued while a person is in control. The project is currently in alpha, has no hosted version, and is explicitly intended as a starting point for teams to adapt with their own configuration.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

AI Model Jev Completes 60-Second Highway Drive Without a Single Crash

A developer used TypeSafe AI's decision-focused model Jev to control a simulated vehicle on a three-lane highway populated with 30 surrounding vehicles. After early attempts resulted in immediate crashes or the car stopping completely, the system was refined to ask Jev multiple simultaneous questions about lane changes, speed adjustments, and collision risk. The final run covered 1,203.72 metres in 60 seconds at an average speed of 72.3 km/h, with no collisions or full stops recorded. Jev, described by TypeSafe AI as a 'System One' model, returns typed decisions and probability values rather than conversational text, making it suited for real-time agent control. The experiment demonstrated that the model could apply roughly 2.73 driving decisions per second with a median response latency of around 311 milliseconds.

0 comments Read more at DEV Community