<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Ssh on Technical Notes</title><link>http://luispa.com/en/tags/ssh/</link><description>Recent content in Ssh on Technical Notes</description><generator>Hugo -- 0.148.0</generator><language>en-US</language><lastBuildDate>Sat, 28 Sep 2024 00:00:00 +0000</lastBuildDate><atom:link href="http://luispa.com/en/tags/ssh/index.xml" rel="self" type="application/rss+xml"/><item><title>CRLF vs LF</title><link>http://luispa.com/en/posts/2024-09-28-crlf-vs-lf/</link><pubDate>Sat, 28 Sep 2024 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2024-09-28-crlf-vs-lf/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-crlf.svg" alt="CRLF Logo" width="150px" style="float:left; padding-right:25px" />
&lt;p>When working in software development, one of the most subtle yet crucial aspects you need to be aware of is the difference between line endings in text files between Windows (CRLF &lt;code>\r\n&lt;/code>) and Linux/MacOS (LF &lt;code>\n&lt;/code>).&lt;/p>
&lt;p>This small detail can cause big problems if not handled correctly, especially when working in mixed environments &amp;ndash; &lt;strong>version control conflicts&lt;/strong>, &lt;strong>script incompatibilities&lt;/strong>, &lt;strong>compilation or execution issues&lt;/strong>. I wrote this post to have a handy reference for dealing with this topic, including a few tricks.&lt;/p>
&lt;br clear="left"/></description></item><item><title>Git Multi-Account</title><link>http://luispa.com/en/posts/2024-09-21-git-multicuenta/</link><pubDate>Sat, 21 Sep 2024 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2024-09-21-git-multicuenta/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-git-multi.svg" alt="GIT multi-account Logo" width="150px" style="float:left; padding-right:25px" />
&lt;p>This post will walk you through the process of setting up and using multiple accounts with one or more Git providers (GitHub, GitLab, Gitea). I describe the two options I recommend: &lt;strong>HTTPS + Git Credential Manager&lt;/strong> and &lt;strong>SSH multi-account&lt;/strong>.&lt;/p>
&lt;p>The first, HTTPS + Git Credential Manager, is the one I use most, because it&amp;rsquo;s compatible with CLI and/or GUI tools like Visual Studio, VSCode, Git Desktop, Gitkraken, etc. The second option, SSH multi-account, I delegate to &amp;ldquo;headless&amp;rdquo; machines, servers I connect to remotely via CLI or VSCode remote that need to clone repositories and work on them.&lt;/p>
&lt;br clear="left"/></description></item><item><title>Socketed SSH</title><link>http://luispa.com/en/posts/2023-04-14-ssh-socket/</link><pubDate>Fri, 14 Apr 2023 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2023-04-14-ssh-socket/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-socketed-ssh.svg" alt="socketed ssh logo" width="150px" height="150px" style="float:left; padding-right:25px" />
&lt;p>&lt;a href="https://systemd.io">Systemd&lt;/a> is a system used in Linux to manage boot and system processes. Its &lt;strong>&amp;ldquo;units&amp;rdquo;&lt;/strong> are configuration files that describe the processes and services that &lt;code>systemd&lt;/code> manages.&lt;/p>
&lt;p>One of these units is &lt;code>systemd.socket&lt;/code>, which starts the corresponding daemon when a connection is established through a socket with the machine. A socket is a form of communication between processes over a network or within the system. By creating a unit of this type, we ask it to listen on a specific socket and start a specific service when a connection is received.&lt;/p>
&lt;br clear="left"/></description></item><item><title>Git Cheat Sheet</title><link>http://luispa.com/en/posts/2021-10-10-git-cheatsheet/</link><pubDate>Sun, 10 Oct 2021 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2021-10-10-git-cheatsheet/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-git-cheatsheet.svg" alt="GIT Cheatsheet Logo" width="150px" style="float:left; padding-right:25px" />
&lt;p>This post contains &lt;strong>my GIT cheat sheet&lt;/strong>, various reminders I use as a programmer — common commands or situations. It comes in handy for example when I accidentally delete a file and want to recover it, check a previous version of code, or ignore a modification in a specific file.&lt;/p>
&lt;br clear="left"/></description></item><item><title>SSH and X11 as root</title><link>http://luispa.com/en/posts/2017-02-11-x11-desde-root/</link><pubDate>Sat, 11 Feb 2017 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2017-02-11-x11-desde-root/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-ssh-xorg.svg" alt="ssh xorg logo" width="150px" height="150px" style="float:left; padding-right:25px" />
&lt;p>The goal is to &lt;strong>make X11 (X-Window) applications work &amp;ldquo;also&amp;rdquo; from root&lt;/strong>. Making them work from a regular user is straightforward, but &lt;strong>then switching to root with &lt;code>su/sudo&lt;/code> and having X11 work is not allowed in Linux&lt;/strong>. The X11 connection &lt;em>only&lt;/em> belongs to the user you logged in with via SSH.&lt;/p>
&lt;br clear="left"/></description></item><item><title>SSH on Linux</title><link>http://luispa.com/en/posts/2009-02-01-ssh/</link><pubDate>Sun, 01 Feb 2009 00:00:00 +0000</pubDate><guid>http://luispa.com/en/posts/2009-02-01-ssh/</guid><description>&lt;img src="http://luispa.com/img/posts/logo-ssh.svg" alt="ssh logo" width="150px" height="150px" style="float:left; padding-right:25px" />
&lt;p>The SSH service is the first thing you should configure on a Linux system. With OpenSSH you get a set of tools &amp;ndash; including ssh, sshd, scp, etc. &amp;ndash; that allow you to enable secure remote shell access to your machine. If you come from the &amp;ldquo;telnet&amp;rdquo; era, you should forget about it; its replacement today is SSH.&lt;/p>
&lt;br clear="left"/></description></item></channel></rss>