SShortSingh.
Back to feed

How to Set Up SSH Key Authentication for Passwordless Remote Server Access

0
·16 views

An operations engineer explains how to replace password logins with SSH key authentication, which the author says takes about five minutes using only the command line. The guide recommends generating an Ed25519 key pair with ssh-keygen, with a passphrase to encrypt the private key, and falling back to a 4096-bit RSA key for legacy systems. Public keys can be installed on a server with ssh-copy-id or by appending them to authorized_keys manually. The article also covers testing the new login, disabling password authentication in sshd_config, and troubleshooting common errors like permission problems and agent 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)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Developers Weigh New AI Code Editors as Coding Agents Reshape Workflows

The article surveys roughly ten standalone AI code editors and many AI coding tools, including Cursor, now owned by SpaceX, Google Antigravity, Amazon Kiro, Trae, and Zed. It notes that Coinbase's AI acceleration lead told engineers in January 2026 to stop using their IDEs and rely on coding agents for all work. Anthropic data reportedly shows Claude Code sessions roughly doubling in length over three months. The piece argues companies may begin treating AI token usage as a managed resource, with budgets and dashboards, under a concept it calls "Claudeonomics." It concludes that developers who deliver the most output per token will stand out most.

0
ProgrammingDEV Community ·

Fastest AI inference API varies by region, 30-day latency study finds

A 30-day latency study of AI inference APIs found that no single provider is fastest everywhere, as results shift with the client's location. Fireworks AI had the quickest network response from US Central and Tokyo, while OpenRouter led from São Paulo. For time to first token, Groq's gpt-oss-120b model was fastest, with median times of 0.8 to 1.5 seconds across the three regions, and Google's Gemini Flash-Lite model was slower with higher tail latency. The researchers noted that SambaNova's network response differed 15-fold between Tokyo and São Paulo, and that closest proximity did not guarantee the fastest first token. Token-generation throughput and first-token times for Cerebras and SambaNova were not measured, and German probe results were excluded due to a throttling issue.

0
ProgrammingDEV Community ·

AI Agents Can Act Beyond a User's Rights Through Confused Deputy Flaws

An example in the article shows a support assistant summarizing a ticket for a user at Acme, where an embedded line told it to close another tenant's tickets. The assistant had permission to do so because it ran under one broad service account, so the injected write looked fully authorized. The authors argue the root cause is authority that does not follow the request, not a faulty model. Their proposed fix is a check outside the model that permits a tool call only if the user, the agent, and the tenant all allow it. The series covers the policy, tests, and multi-agent production concerns, with examples written in Cedar.

0
ProgrammingDEV Community ·

OpenAI sets 2026-2027 API shutdown dates for GPT-4o, GPT-4.1, GPT-5, o3 and Whisper

OpenAI has published a schedule of API deprecations running from late 2026 into 2027. GPT-4o, GPT-4o mini, GPT-4.1 and GPT-4.1 mini are set to leave the API on 14 January 2027, with gpt-6-luna recommended as the replacement. GPT-5, o3 and related models shut down on 11 December 2026, while Whisper and GPT-4o transcription models follow on 26 February 2027. The GPT-4 series received only about 92 days' notice, well short of the six months OpenAI generally promises, and one recommended replacement is itself retired just 37 days after it takes over.