<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Ssh - Tag - Dimas Maulana</title>
    <link>https://dimasmaulana.pages.dev/tags/ssh/</link>
    <description>Dimas Maulana Website</description>
    <generator>Hugo 0.150.0 &amp; FixIt v0.4.3-20260130042349-e23a50d7</generator>
    <language>en</language>
    <lastBuildDate>Thu, 14 Nov 2024 08:40:11 +0700</lastBuildDate>
    <atom:link href="https://dimasmaulana.pages.dev/tags/ssh/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Refreshing Your Virtual Machine List in VirtualBox on Windows via SSH CLI</title>
      <link>https://dimasmaulana.pages.dev/posts/devops/refreshing-your-virtual-machine-list-in-virtualbox-on-windows-via-ssh-cli/</link>
      <pubDate>Thu, 14 Nov 2024 08:40:11 +0700</pubDate>
      <guid>https://dimasmaulana.pages.dev/posts/devops/refreshing-your-virtual-machine-list-in-virtualbox-on-windows-via-ssh-cli/</guid>
      <category domain="https://dimasmaulana.pages.dev/categories/devops/">DevOps</category>
      <description>&lt;p&gt;Sometimes, when working with VirtualBox on Windows, you might encounter an issue where your virtual machine list doesn&amp;rsquo;t update correctly, even after making changes like unlocking an encrypted drive. This can be frustrating when you&amp;rsquo;re trying to manage your VMs.&lt;/p&gt;&#xA;&lt;p&gt;This article will guide you through a solution to refresh your VirtualBox VM list via the command line interface (CLI) accessed via SSH.&lt;/p&gt;&#xA;&lt;h3 class=&#34;heading-element&#34; id=&#34;the-problem&#34;&gt;&lt;span&gt;The Problem&lt;/span&gt;&#xA;  &lt;a href=&#34;#the-problem&#34; class=&#34;heading-mark&#34;&gt;&#xA;    &lt;svg class=&#34;octicon octicon-link&#34; viewBox=&#34;0 0 16 16&#34; version=&#34;1.1&#34; width=&#34;16&#34; height=&#34;16&#34; aria-hidden=&#34;true&#34;&gt;&lt;path d=&#34;m7.775 3.275 1.25-1.25a3.5 3.5 0 1 1 4.95 4.95l-2.5 2.5a3.5 3.5 0 0 1-4.95 0 .751.751 0 0 1 .018-1.042.751.751 0 0 1 1.042-.018 1.998 1.998 0 0 0 2.83 0l2.5-2.5a2.002 2.002 0 0 0-2.83-2.83l-1.25 1.25a.751.751 0 0 1-1.042-.018.751.751 0 0 1-.018-1.042Zm-4.69 9.64a1.998 1.998 0 0 0 2.83 0l1.25-1.25a.751.751 0 0 1 1.042.018.751.751 0 0 1 .018 1.042l-1.25 1.25a3.5 3.5 0 1 1-4.95-4.95l2.5-2.5a3.5 3.5 0 0 1 4.95 0 .751.751 0 0 1-.018 1.042.751.751 0 0 1-1.042.018 1.998 1.998 0 0 0-2.83 0l-2.5 2.5a1.998 1.998 0 0 0 0 2.83Z&#34;&gt;&lt;/path&gt;&lt;/svg&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h3&gt;&lt;p&gt;Let&amp;rsquo;s say you have a virtual machine stored on an encrypted drive. When Windows starts, the drive is locked. You can unlock the drive via SSH, but when you try to list your virtual machines using &lt;code&gt;vboxmanage&lt;/code&gt; within your SSH session, you might still get an &amp;ldquo;access denied&amp;rdquo; error.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Unlocking Luks Encrypted Disk via SSH on Ubuntu Server</title>
      <link>https://dimasmaulana.pages.dev/posts/devops/unlocking-luks-encrypted-disk-via-ssh-on-ubuntu-server/</link>
      <pubDate>Fri, 08 Nov 2024 11:29:59 +0700</pubDate>
      <guid>https://dimasmaulana.pages.dev/posts/devops/unlocking-luks-encrypted-disk-via-ssh-on-ubuntu-server/</guid>
      <category domain="https://dimasmaulana.pages.dev/categories/devops/">DevOps</category>
      <description>&lt;p&gt;This article provides a step-by-step procedure for unlocking and accessing a Luks encrypted disk using SSH on an Ubuntu server.&lt;/p&gt;&#xA;&lt;h2 class=&#34;heading-element&#34; id=&#34;install-dropbear&#34;&gt;&lt;span&gt;Install Dropbear&lt;/span&gt;&#xA;  &lt;a href=&#34;#install-dropbear&#34; class=&#34;heading-mark&#34;&gt;&#xA;    &lt;svg class=&#34;octicon octicon-link&#34; viewBox=&#34;0 0 16 16&#34; version=&#34;1.1&#34; width=&#34;16&#34; height=&#34;16&#34; aria-hidden=&#34;true&#34;&gt;&lt;path d=&#34;m7.775 3.275 1.25-1.25a3.5 3.5 0 1 1 4.95 4.95l-2.5 2.5a3.5 3.5 0 0 1-4.95 0 .751.751 0 0 1 .018-1.042.751.751 0 0 1 1.042-.018 1.998 1.998 0 0 0 2.83 0l2.5-2.5a2.002 2.002 0 0 0-2.83-2.83l-1.25 1.25a.751.751 0 0 1-1.042-.018.751.751 0 0 1-.018-1.042Zm-4.69 9.64a1.998 1.998 0 0 0 2.83 0l1.25-1.25a.751.751 0 0 1 1.042.018.751.751 0 0 1 .018 1.042l-1.25 1.25a3.5 3.5 0 1 1-4.95-4.95l2.5-2.5a3.5 3.5 0 0 1 4.95 0 .751.751 0 0 1-.018 1.042.751.751 0 0 1-1.042.018 1.998 1.998 0 0 0-2.83 0l-2.5 2.5a1.998 1.998 0 0 0 0 2.83Z&#34;&gt;&lt;/path&gt;&lt;/svg&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&lt;p&gt;To enable SSH access on your Ubuntu server, you&amp;rsquo;ll need to install Dropbear. Run the following commands:&lt;/p&gt;</description>
    </item>
    <item>
      <title>Resolving Missing OpenSSH Service Configuration After Uninstallation</title>
      <link>https://dimasmaulana.pages.dev/posts/devops/resolving-missing-openssh-service-configuration-after-uninstallation/</link>
      <pubDate>Fri, 08 Nov 2024 10:27:57 +0700</pubDate>
      <guid>https://dimasmaulana.pages.dev/posts/devops/resolving-missing-openssh-service-configuration-after-uninstallation/</guid>
      <category domain="https://dimasmaulana.pages.dev/categories/devops/">DevOps</category>
      <description>&lt;p&gt;This article explains how to address a potential issue with OpenSSH configuration after uninstalling and reinstalling the service.&lt;/p&gt;&#xA;&lt;h2 class=&#34;heading-element&#34; id=&#34;the-problem&#34;&gt;&lt;span&gt;The Problem&lt;/span&gt;&#xA;  &lt;a href=&#34;#the-problem&#34; class=&#34;heading-mark&#34;&gt;&#xA;    &lt;svg class=&#34;octicon octicon-link&#34; viewBox=&#34;0 0 16 16&#34; version=&#34;1.1&#34; width=&#34;16&#34; height=&#34;16&#34; aria-hidden=&#34;true&#34;&gt;&lt;path d=&#34;m7.775 3.275 1.25-1.25a3.5 3.5 0 1 1 4.95 4.95l-2.5 2.5a3.5 3.5 0 0 1-4.95 0 .751.751 0 0 1 .018-1.042.751.751 0 0 1 1.042-.018 1.998 1.998 0 0 0 2.83 0l2.5-2.5a2.002 2.002 0 0 0-2.83-2.83l-1.25 1.25a.751.751 0 0 1-1.042-.018.751.751 0 0 1-.018-1.042Zm-4.69 9.64a1.998 1.998 0 0 0 2.83 0l1.25-1.25a.751.751 0 0 1 1.042.018.751.751 0 0 1 .018 1.042l-1.25 1.25a3.5 3.5 0 1 1-4.95-4.95l2.5-2.5a3.5 3.5 0 0 1 4.95 0 .751.751 0 0 1-.018 1.042.751.751 0 0 1-1.042.018 1.998 1.998 0 0 0-2.83 0l-2.5 2.5a1.998 1.998 0 0 0 0 2.83Z&#34;&gt;&lt;/path&gt;&lt;/svg&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&lt;p&gt;When OpenSSH is uninstalled via the Installer, the configuration for the &lt;code&gt;sshd&lt;/code&gt; service might be removed. Even if you reinstall OpenSSH through the Feature option, the configuration may still be missing. This can prevent SSH from functioning properly.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Resolving SSH Key Loading Issues on Windows</title>
      <link>https://dimasmaulana.pages.dev/posts/devops/resolving-ssh-key-loading-issues-on-windows/</link>
      <pubDate>Thu, 07 Nov 2024 22:34:09 +0700</pubDate>
      <guid>https://dimasmaulana.pages.dev/posts/devops/resolving-ssh-key-loading-issues-on-windows/</guid>
      <category domain="https://dimasmaulana.pages.dev/categories/devops/">DevOps</category>
      <description>&lt;p&gt;While SSH is commonly associated with Linux and Unix systems, it can also be configured on Windows. This guide focuses on resolving SSH key loading issues specifically for Windows environments.&lt;/p&gt;&#xA;&lt;h2 class=&#34;heading-element&#34; id=&#34;understanding-the-challenge&#34;&gt;&lt;span&gt;Understanding the Challenge&lt;/span&gt;&#xA;  &lt;a href=&#34;#understanding-the-challenge&#34; class=&#34;heading-mark&#34;&gt;&#xA;    &lt;svg class=&#34;octicon octicon-link&#34; viewBox=&#34;0 0 16 16&#34; version=&#34;1.1&#34; width=&#34;16&#34; height=&#34;16&#34; aria-hidden=&#34;true&#34;&gt;&lt;path d=&#34;m7.775 3.275 1.25-1.25a3.5 3.5 0 1 1 4.95 4.95l-2.5 2.5a3.5 3.5 0 0 1-4.95 0 .751.751 0 0 1 .018-1.042.751.751 0 0 1 1.042-.018 1.998 1.998 0 0 0 2.83 0l2.5-2.5a2.002 2.002 0 0 0-2.83-2.83l-1.25 1.25a.751.751 0 0 1-1.042-.018.751.751 0 0 1-.018-1.042Zm-4.69 9.64a1.998 1.998 0 0 0 2.83 0l1.25-1.25a.751.751 0 0 1 1.042.018.751.751 0 0 1 .018 1.042l-1.25 1.25a3.5 3.5 0 1 1-4.95-4.95l2.5-2.5a3.5 3.5 0 0 1 4.95 0 .751.751 0 0 1-.018 1.042.751.751 0 0 1-1.042.018 1.998 1.998 0 0 0-2.83 0l-2.5 2.5a1.998 1.998 0 0 0 0 2.83Z&#34;&gt;&lt;/path&gt;&lt;/svg&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&lt;p&gt;Similar to Linux/Unix, the default SSH configuration on Windows might only load keys authorized by administrators, typically stored in a location like &lt;code&gt;%ProgramData%\ssh\administrators_authorized_keys&lt;/code&gt;. This restricts user access unless they are explicitly added to the administrator-authorized keys.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Rsync to Windows Open SSH</title>
      <link>https://dimasmaulana.pages.dev/posts/devops/rsync-to-windows-open-ssh/</link>
      <pubDate>Wed, 06 Nov 2024 16:40:20 +0700</pubDate>
      <guid>https://dimasmaulana.pages.dev/posts/devops/rsync-to-windows-open-ssh/</guid>
      <category domain="https://dimasmaulana.pages.dev/categories/devops/">DevOps</category>
      <description>&lt;p&gt;Attempting to perform an rsync operation from a Linux or macOS system to a Windows machine directly using the &lt;code&gt;rsync&lt;/code&gt; command will fail. This is because Windows does not have a built-in &lt;code&gt;rsync&lt;/code&gt; utility.&lt;/p&gt;&#xA;&lt;p&gt;A typical command like &lt;code&gt;rsync /source/ target-hostname:/mnt/e/target/&lt;/code&gt; will result in an error.&lt;/p&gt;&#xA;&lt;h2 class=&#34;heading-element&#34; id=&#34;solution&#34;&gt;&lt;span&gt;Solution&lt;/span&gt;&#xA;  &lt;a href=&#34;#solution&#34; class=&#34;heading-mark&#34;&gt;&#xA;    &lt;svg class=&#34;octicon octicon-link&#34; viewBox=&#34;0 0 16 16&#34; version=&#34;1.1&#34; width=&#34;16&#34; height=&#34;16&#34; aria-hidden=&#34;true&#34;&gt;&lt;path d=&#34;m7.775 3.275 1.25-1.25a3.5 3.5 0 1 1 4.95 4.95l-2.5 2.5a3.5 3.5 0 0 1-4.95 0 .751.751 0 0 1 .018-1.042.751.751 0 0 1 1.042-.018 1.998 1.998 0 0 0 2.83 0l2.5-2.5a2.002 2.002 0 0 0-2.83-2.83l-1.25 1.25a.751.751 0 0 1-1.042-.018.751.751 0 0 1-.018-1.042Zm-4.69 9.64a1.998 1.998 0 0 0 2.83 0l1.25-1.25a.751.751 0 0 1 1.042.018.751.751 0 0 1 .018 1.042l-1.25 1.25a3.5 3.5 0 1 1-4.95-4.95l2.5-2.5a3.5 3.5 0 0 1 4.95 0 .751.751 0 0 1-.018 1.042.751.751 0 0 1-1.042.018 1.998 1.998 0 0 0-2.83 0l-2.5 2.5a1.998 1.998 0 0 0 0 2.83Z&#34;&gt;&lt;/path&gt;&lt;/svg&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&lt;p&gt;Leverage the power of the Windows Subsystem for Linux (WSL) to enable rsync functionality on your Windows system.&lt;/p&gt;</description>
    </item>
    <item>
      <title>SSHD Windows 10 Not Accepting Public Key</title>
      <link>https://dimasmaulana.pages.dev/posts/devops/sshd-windows-10-not-accepting-public-key-/</link>
      <pubDate>Sun, 17 Mar 2019 16:10:44 +0700</pubDate>
      <guid>https://dimasmaulana.pages.dev/posts/devops/sshd-windows-10-not-accepting-public-key-/</guid>
      <category domain="https://dimasmaulana.pages.dev/categories/devops/">DevOps</category>
      <category domain="https://dimasmaulana.pages.dev/categories/troubleshooting/">Troubleshooting</category>
      <description>&lt;p&gt;If you&amp;rsquo;re experiencing issues with SSHD on Windows 10 not accepting your public key, there are a few steps you can take to troubleshoot the problem. Follow the steps below to resolve the issue.&lt;/p&gt;&#xA;&lt;h2 class=&#34;heading-element&#34; id=&#34;step-1-open-the-sshd-configuration-file&#34;&gt;&lt;span&gt;Step 1: Open the SSHD Configuration File&lt;/span&gt;&#xA;  &lt;a href=&#34;#step-1-open-the-sshd-configuration-file&#34; class=&#34;heading-mark&#34;&gt;&#xA;    &lt;svg class=&#34;octicon octicon-link&#34; viewBox=&#34;0 0 16 16&#34; version=&#34;1.1&#34; width=&#34;16&#34; height=&#34;16&#34; aria-hidden=&#34;true&#34;&gt;&lt;path d=&#34;m7.775 3.275 1.25-1.25a3.5 3.5 0 1 1 4.95 4.95l-2.5 2.5a3.5 3.5 0 0 1-4.95 0 .751.751 0 0 1 .018-1.042.751.751 0 0 1 1.042-.018 1.998 1.998 0 0 0 2.83 0l2.5-2.5a2.002 2.002 0 0 0-2.83-2.83l-1.25 1.25a.751.751 0 0 1-1.042-.018.751.751 0 0 1-.018-1.042Zm-4.69 9.64a1.998 1.998 0 0 0 2.83 0l1.25-1.25a.751.751 0 0 1 1.042.018.751.751 0 0 1 .018 1.042l-1.25 1.25a3.5 3.5 0 1 1-4.95-4.95l2.5-2.5a3.5 3.5 0 0 1 4.95 0 .751.751 0 0 1-.018 1.042.751.751 0 0 1-1.042.018 1.998 1.998 0 0 0-2.83 0l-2.5 2.5a1.998 1.998 0 0 0 0 2.83Z&#34;&gt;&lt;/path&gt;&lt;/svg&gt;&#xA;  &lt;/a&gt;&#xA;&lt;/h2&gt;&lt;p&gt;To begin, open the SSHD configuration file using a text editor. In this example, we&amp;rsquo;ll use the Bash shell and the &lt;code&gt;vim&lt;/code&gt; editor. Open a command prompt and navigate to the following directory:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
