<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ssh on Onur Celep</title><link>https://onurcelep.github.io/tags/ssh/</link><description>Recent content in Ssh on Onur Celep</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 29 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://onurcelep.github.io/tags/ssh/index.xml" rel="self" type="application/rss+xml"/><item><title>SSH certificate access to a device lab, end to end</title><link>https://onurcelep.github.io/posts/ssh-certificate-access-to-a-device-lab/</link><pubDate>Mon, 29 Jun 2026 00:00:00 +0000</pubDate><guid>https://onurcelep.github.io/posts/ssh-certificate-access-to-a-device-lab/</guid><description>&lt;p&gt;I run a fleet of embedded Linux test benches. Each bench is a small gateway
(a Raspberry Pi) with a board under test wired to it. People and CI jobs need
to SSH into those gateways and boards to flash images, drive tests, and poke
at failures. The question that looks trivial and is not: &lt;strong&gt;who is allowed to
SSH where, and how do you keep that true over time?&lt;/strong&gt;&lt;/p&gt;</description></item></channel></rss>