<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: How to Use GPG to Encrypt and Decrypt Files in Linux	</title>
	<atom:link href="https://www.tecmint.com/gpg-encrypt-decrypt-files/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.tecmint.com/gpg-encrypt-decrypt-files/</link>
	<description>Tecmint - Linux Howtos, Tutorials, Guides, News, Tips and Tricks.</description>
	<lastBuildDate>Tue, 27 Jan 2026 06:08:25 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Ravi Saive		</title>
		<link>https://www.tecmint.com/gpg-encrypt-decrypt-files/comment-page-1/#comment-2383998</link>

		<dc:creator><![CDATA[Ravi Saive]]></dc:creator>
		<pubDate>Tue, 27 Jan 2026 06:08:25 +0000</pubDate>
		<guid isPermaLink="false">https://www.tecmint.com/?p=50801#comment-2383998</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.tecmint.com/gpg-encrypt-decrypt-files/comment-page-1/#comment-2383405&quot;&gt;Udu&lt;/a&gt;.

@Udu,

Thanks for the suggestion, here is the command to check a key’s fingerprint:
&lt;pre&gt;
gpg --fingerprint someone@example.com
&lt;/pre&gt;
Or for a key file before importing:
&lt;pre&gt;
gpg --show-keys --fingerprint publickey.asc
&lt;/pre&gt;
Then the fingerprint should be confirmed through a secure channel (in person, phone, or another trusted method) before trusting or importing the key.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a target="_blank" href="https://www.tecmint.com/gpg-encrypt-decrypt-files/comment-page-1/#comment-2383405">Udu</a>.</p>
<p>@Udu,</p>
<p>Thanks for the suggestion, here is the command to check a key’s fingerprint:</p>
<pre>
gpg --fingerprint someone@example.com
</pre>
<p>Or for a key file before importing:</p>
<pre>
gpg --show-keys --fingerprint publickey.asc
</pre>
<p>Then the fingerprint should be confirmed through a secure channel (in person, phone, or another trusted method) before trusting or importing the key.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Udu		</title>
		<link>https://www.tecmint.com/gpg-encrypt-decrypt-files/comment-page-1/#comment-2383405</link>

		<dc:creator><![CDATA[Udu]]></dc:creator>
		<pubDate>Sat, 24 Jan 2026 15:04:45 +0000</pubDate>
		<guid isPermaLink="false">https://www.tecmint.com/?p=50801#comment-2383405</guid>

					<description><![CDATA[It would be helpful to also explain how to verify key fingerprints before importing someone’s public key, and to confirm the fingerprint through a secure channel to prevent man-in-the-middle attacks.]]></description>
			<content:encoded><![CDATA[<p>It would be helpful to also explain how to verify key fingerprints before importing someone’s public key, and to confirm the fingerprint through a secure channel to prevent man-in-the-middle attacks.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: mikey		</title>
		<link>https://www.tecmint.com/gpg-encrypt-decrypt-files/comment-page-1/#comment-2055873</link>

		<dc:creator><![CDATA[mikey]]></dc:creator>
		<pubDate>Fri, 08 Sep 2023 06:47:10 +0000</pubDate>
		<guid isPermaLink="false">https://www.tecmint.com/?p=50801#comment-2055873</guid>

					<description><![CDATA[Thanks for the writing up. 

It&#039;s probably better to name the two files (&lt;strong&gt;aaronsec.key&lt;/strong&gt; and &lt;strong&gt;tadminsec.key&lt;/strong&gt;) &lt;strong&gt;aaronpub.key&lt;/strong&gt; and &lt;strong&gt;tadminpub.key&lt;/strong&gt;, respectively, since they are in fact public keys. 

And there is no need for &quot;&lt;strong&gt;secure other means&lt;/strong&gt;&quot; to exchange public keys. In fact public keys should be as widely published as possible.]]></description>
			<content:encoded><![CDATA[<p>Thanks for the writing up. </p>
<p>It&#8217;s probably better to name the two files (<strong>aaronsec.key</strong> and <strong>tadminsec.key</strong>) <strong>aaronpub.key</strong> and <strong>tadminpub.key</strong>, respectively, since they are in fact public keys. </p>
<p>And there is no need for &#8220;<strong>secure other means</strong>&#8221; to exchange public keys. In fact public keys should be as widely published as possible.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
