<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Networking on Cesar Gimenes</title><link>https://crg.eti.br/en/tags/networking/</link><description>Recent content in Networking on Cesar Gimenes</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>crg@crg.eti.br (Cesar Gimenes)</managingEditor><webMaster>crg@crg.eti.br (Cesar Gimenes)</webMaster><lastBuildDate>Sun, 09 Sep 2018 08:19:09 -0300</lastBuildDate><atom:link href="https://crg.eti.br/en/tags/networking/index.xml" rel="self" type="application/rss+xml"/><item><title>ssh - Using access keys</title><link>https://crg.eti.br/en/post/ssh-usando-chave/</link><pubDate>Sun, 09 Sep 2018 08:19:09 -0300</pubDate><author>crg@crg.eti.br (Cesar Gimenes)</author><guid>https://crg.eti.br/en/post/ssh-usando-chave/</guid><description>&lt;p>Watch the video for this article &lt;a href="https://www.youtube.com/watch?v=f-4R_PNEFT4">here&lt;/a>.&lt;/p>
&lt;p>Accessing servers over SSH with a public/private key pair is safer and more convenient — safer above all — and it also makes automating tasks much easier.&lt;/p>
&lt;h2 id="creating-the-keys">Creating the keys&lt;/h2>
&lt;p>First, generate the keys with the following command:&lt;/p>
&lt;div class="highlight">&lt;pre tabindex="0" style="color:#e6edf3;background-color:#0d1117;-moz-tab-size:4;-o-tab-size:4;tab-size:4;">&lt;code class="language-bash" data-lang="bash">&lt;span style="display:flex;">&lt;span>mkdir ~/.ssh
&lt;/span>&lt;/span>&lt;span style="display:flex;">&lt;span>ssh-keygen
&lt;/span>&lt;/span>&lt;/code>&lt;/pre>&lt;/div>&lt;p>You only need to do this once on the client machine, and a key pair will be generated. You can choose the file name, which defaults to &lt;code>id_rsa&lt;/code> for the private key and &lt;code>id_rsa.pub&lt;/code> for the public key.&lt;/p></description></item><item><title>Using a VPN on macOS</title><link>https://crg.eti.br/en/post/proton-vpm/</link><pubDate>Sat, 25 Aug 2018 20:05:18 -0300</pubDate><author>crg@crg.eti.br (Cesar Gimenes)</author><guid>https://crg.eti.br/en/post/proton-vpm/</guid><description>&lt;p>Like any tool, a &lt;a href="https://en.wikipedia.org/wiki/Virtual_private_network">VPN&lt;/a> is only effective if you know exactly which problem you want to solve with it. Some people want to keep their internet traffic anonymous, others want to protect their data, and so on. My own use is very specific: some internet providers are blocking important ports I need to reach certain services. For example, a well-known provider here in São Paulo is blocking TCP port 22, the one we use for SSH. Note that this is not the provider blocking incoming connections, which was already common, but outgoing ones — meaning that using any service that depends on SSH, like &lt;a href="https://github.com/crgimenes">GitHub&lt;/a>, or reaching a machine hosted on Google Cloud Platform&amp;rsquo;s Compute Engine becomes impossible.&lt;/p></description></item></channel></rss>