<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>EXPKEYSIG &#8211; SMsoft &#8211; informatica e dintorni</title>
	<atom:link href="https://blog.smsoft.it/tag/expkeysig/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.smsoft.it</link>
	<description>consigli settimanali su MacOS, GNU/Linux ed Open Source</description>
	<lastBuildDate>Thu, 16 Apr 2026 11:10:19 +0000</lastBuildDate>
	<language>it-IT</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=87376</generator>
	<item>
		<title>Debian: (EXPKEYSIG B7B3B788A8D3785C)</title>
		<link>https://blog.smsoft.it/2025/10/28/debian-expkeysig-b7b3b788a8d3785c/</link>
					<comments>https://blog.smsoft.it/2025/10/28/debian-expkeysig-b7b3b788a8d3785c/#respond</comments>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Tue, 28 Oct 2025 09:30:00 +0000</pubDate>
				<category><![CDATA[Linux]]></category>
		<category><![CDATA[Debian]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[EXPKEYSIG]]></category>
		<guid isPermaLink="false">https://blog.smsoft.it/?p=6745</guid>

					<description><![CDATA[La firma per il repository MySQL è scaduta il 22 ottobre 2025, potete verificarlo facilmente con: In questo modo, l&#8217;aggiornamento dei pacchetti MySQL sulla vostra Debian fallirà. Per cancellare la vecchia firma possiamo cancellare fisicamente il file /etc/apt/trusted.gpg.d/mysql2023.gpg oppure: o ancora, se importata precedentemente con gpg: Per risolvere dobbiamo importare la firma dal repository ubuntu ... <a title="Debian: (EXPKEYSIG B7B3B788A8D3785C)" class="read-more" href="https://blog.smsoft.it/2025/10/28/debian-expkeysig-b7b3b788a8d3785c/" aria-label="Per saperne di più su Debian: (EXPKEYSIG B7B3B788A8D3785C)">Leggi tutto</a>]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">La firma per il repository MySQL è scaduta  il 22 ottobre 2025, potete verificarlo facilmente con:</p>



<pre class="wp-block-code"><code>curl -fsSL https://repo.mysql.com/RPM-GPG-KEY-mysql-2023 -o /tmp/fresh.asc -H "Cache-Control: no-cache"
gpg --show-keys /tmp/fresh.asc</code></pre>



<pre class="wp-block-code"><code>pub rsa4096 2023-10-23 &#91;SC] &#91;scaduto: 2025-10-22]
BCA43417C3B485DD128EC6D4B7B3B788A8D3785C
uid MySQL Release Engineering mysql-build@oss.oracle.com 
sub rsa4096 2023-10-23 &#91;E] &#91;scaduto: 2025-10-22]</code></pre>



<p class="wp-block-paragraph">In questo modo, l&#8217;aggiornamento dei pacchetti MySQL sulla vostra Debian fallirà. </p>



<p class="wp-block-paragraph">Per cancellare la vecchia firma possiamo cancellare fisicamente il file <strong>/etc/apt/trusted.gpg.d/mysql2023.gpg </strong></p>



<pre class="wp-block-code"><code>rm /etc/apt/trusted.gpg.d/mysql2023.gpg</code></pre>



<p class="wp-block-paragraph">oppure:</p>



<pre class="wp-block-code"><code>apt-key del B7B3B788A8D3785C</code></pre>



<p class="wp-block-paragraph">o ancora, se importata precedentemente con gpg:</p>



<pre class="wp-block-code"><code>gpg --delete-keys B7B3B788A8D3785C</code></pre>



<p class="wp-block-paragraph">Per risolvere dobbiamo importare la firma dal repository ubuntu ed usarla:</p>



<pre class="wp-block-code"><code>curl -fsSL "https://keyserver.ubuntu.com/pks/lookup?op=get&amp;search=0xB7B3B788A8D3785C" -o /tmp/fresh.asc
gpg --show-keys /tmp/fresh.asc</code></pre>



<pre class="wp-block-code"><code>pub rsa4096 2023-10-23 &#91;SC] &#91;scadenza: 2027-10-23]
BCA43417C3B485DD128EC6D4B7B3B788A8D3785C
uid MySQL Release Engineering mysql-build@oss.oracle.com
sub rsa4096 2023-10-23 &#91;E] &#91;scadenza: 2027-10-23]</code></pre>



<pre class="wp-block-code"><code>gpg --import /tmp/fresh.asc</code></pre>



<p class="wp-block-paragraph"></p>



<p class="wp-block-paragraph"><strong>Nota:</strong> se non si ha accesso diretto a <strong>keyserver.ubuntu.com</strong> dalla macchina in questione, si può scaricare il certificato da un&#8217;altra macchina nel seguente modo:</p>



<pre class="wp-block-code"><code>gpg --keyserver keyserver.ubuntu.com --recv B7B3B788A8D3785C
gpg --export --armor B7B3B788A8D3785C &gt;fresh.asc</code></pre>



<p class="wp-block-paragraph">e poi si copia il file fresh.asc (in questo esempio lo metto in <strong>/tmp/fresh.asc</strong>) sui server dove bisogna importarlo e si completa la procedura con:</p>



<pre class="wp-block-code"><code>rm -fr /etc/apt/trusted.gpg.d/mysql2023.gpg
apt-key del B7B3B788A8D3785C
apt-key add /tmp/fresh.asc</code></pre>



<p class="wp-block-paragraph">enjoy!</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.smsoft.it/2025/10/28/debian-expkeysig-b7b3b788a8d3785c/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Debian 11 (bullseye) o Debian 12 (bookworm) APT: Firme GPG per PHP, MySQL, Docker e Node</title>
		<link>https://blog.smsoft.it/2023/03/28/debian-apt-firme-gpg-per-php-e-mysql/</link>
					<comments>https://blog.smsoft.it/2023/03/28/debian-apt-firme-gpg-per-php-e-mysql/#respond</comments>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Tue, 28 Mar 2023 08:30:00 +0000</pubDate>
				<category><![CDATA[Debian]]></category>
		<category><![CDATA[Html e PHP]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[docker]]></category>
		<category><![CDATA[EXPKEYSIG]]></category>
		<category><![CDATA[gpg]]></category>
		<category><![CDATA[key]]></category>
		<category><![CDATA[NO_PUBKEY]]></category>
		<category><![CDATA[php]]></category>
		<guid isPermaLink="false">https://blog.smsoft.it/?p=5863</guid>

					<description><![CDATA[Una cosa che mi chiedono spesso e come gestire le firme per i repository di PHP, MySQL, Docker se Node ulle nuove debian. La classica procedura di import della firma non funziona più, consiglio quindi di scaricare la firma come segue. per PHP Sury: per MySQL: per Docker: per Node: Nota: per vedere il contenuto ... <a title="Debian 11 (bullseye) o Debian 12 (bookworm) APT: Firme GPG per PHP, MySQL, Docker e Node" class="read-more" href="https://blog.smsoft.it/2023/03/28/debian-apt-firme-gpg-per-php-e-mysql/" aria-label="Per saperne di più su Debian 11 (bullseye) o Debian 12 (bookworm) APT: Firme GPG per PHP, MySQL, Docker e Node">Leggi tutto</a>]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">Una cosa che mi chiedono spesso e come gestire le firme per i repository di <strong>PHP</strong>, <strong>MySQL</strong>, <strong>Docker</strong> se <strong>Node</strong> ulle nuove debian. La classica procedura di import della firma non funziona più, consiglio quindi di scaricare la firma come segue.</p>



<p class="wp-block-paragraph"><strong>per PHP Sury:</strong></p>



<pre class="wp-block-code"><code>wget -qO- https://packages.sury.org/php/apt.gpg | gpg --dearmor &gt; /etc/apt/trusted.gpg.d/sury-php-x.x.gpg</code></pre>



<p class="wp-block-paragraph"><strong>per MySQL:</strong></p>



<pre class="wp-block-code"><code>wget -O- http://repo.mysql.com/RPM-GPG-KEY-mysql-2023 | gpg --dearmor &gt; /etc/apt/trusted.gpg.d/mysql.gpg</code></pre>



<p class="wp-block-paragraph"><strong>per Docker:</strong></p>



<pre class="wp-block-code"><code>curl -fsSL https://download.docker.com/linux/debian/gpg | gpg --dearmor -o /etc/apt/trusted.gpg.d/docker.gpg</code></pre>



<p class="wp-block-paragraph"><strong>per Node:</strong></p>



<pre class="wp-block-code"><code>curl -fsSL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | gpg --dearmor -o /etc/apt/trusted.gpg.d/nodesource.gpg</code></pre>



<p class="wp-block-paragraph"><strong>Nota</strong>: per vedere il contenuto di un file di firma (es /etc/apt/trusted.gpg.d/nodesource.gpg):</p>



<pre class="wp-block-code"><code>gpg --no-default-keyring --list-keys --keyring /etc/apt/trusted.gpg.d/nodesource.gpg</code></pre>



<p class="wp-block-paragraph"></p>



<p class="wp-block-paragraph"></p>



<p class="wp-block-paragraph">Installate le firme, si può procedere con l&#8217;<strong>aggiunta dei repository</strong> come segue:</p>



<pre class="wp-block-code"><code>echo "deb https://packages.sury.org/php/ $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/php.list</code></pre>



<p class="wp-block-paragraph">e</p>



<pre class="wp-block-code"><code>wget https://dev.mysql.com/get/mysql-apt-config_0.8.29-1_all.deb
dpkg -i mysql-apt-config_0.8.29-1_all.deb</code></pre>



<p class="wp-block-paragraph">e</p>



<pre class="wp-block-code"><code>echo "deb https://download.docker.com/linux/debian $(lsb_release -sc) stable" | tee /etc/apt/sources.list.d/docker.list</code></pre>



<p class="wp-block-paragraph">e</p>



<pre id="block-8f573445-654c-417a-a502-a342da0aaaf9" class="wp-block-code"><code>echo "deb https://deb.nodesource.com/node_20.x $(lsb_release -sc) main" | tee /etc/apt/sources.list.d/nodesource.list</code></pre>



<p class="wp-block-paragraph">enjoy!</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.smsoft.it/2023/03/28/debian-apt-firme-gpg-per-php-e-mysql/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>APT: Aggiornare la firma del repository gitlab</title>
		<link>https://blog.smsoft.it/2022/05/17/apt-aggiornare-la-firma-del-repository-gitlab/</link>
					<comments>https://blog.smsoft.it/2022/05/17/apt-aggiornare-la-firma-del-repository-gitlab/#respond</comments>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Tue, 17 May 2022 08:30:00 +0000</pubDate>
				<category><![CDATA[Debian]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[apt]]></category>
		<category><![CDATA[apt-key]]></category>
		<category><![CDATA[EXPKEYSIG]]></category>
		<guid isPermaLink="false">https://blog.smsoft.it/?p=5496</guid>

					<description><![CDATA[Se durante il classico apt update viene mostrato il seguente messaggio: Le seguenti firme non erano valide: EXPKEYSIG 3F01618A51312F3F GitLab B.V. (package repository signing key) packages@gitlab.com oppure in inglese: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3F01618A51312F3F E&#8217; possibile procedere all&#8217;aggiornamento come segue: curl --silent https://packages.gitlab.com/gpg.key &#124; apt-key ... <a title="APT: Aggiornare la firma del repository gitlab" class="read-more" href="https://blog.smsoft.it/2022/05/17/apt-aggiornare-la-firma-del-repository-gitlab/" aria-label="Per saperne di più su APT: Aggiornare la firma del repository gitlab">Leggi tutto</a>]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">Se durante il classico apt update viene mostrato il seguente messaggio:</p>



<pre class="wp-block-preformatted">Le seguenti firme non erano valide: EXPKEYSIG 3F01618A51312F3F GitLab B.V. (package repository signing key) <a href="mailto:packages@gitlab.com">packages@gitlab.com</a></pre>



<p class="wp-block-paragraph">oppure in inglese:</p>



<pre class="wp-block-preformatted">The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3F01618A51312F3F</pre>



<p class="wp-block-paragraph">E&#8217; possibile procedere all&#8217;aggiornamento come segue:</p>



<pre class="wp-block-preformatted">curl --silent https://packages.gitlab.com/gpg.key | apt-key add -</pre>



<p class="wp-block-paragraph">enjoy!</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.smsoft.it/2022/05/17/apt-aggiornare-la-firma-del-repository-gitlab/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>apt update ed EXPKEYSIG &#8211; NO_PUBKEY</title>
		<link>https://blog.smsoft.it/2021/03/30/apt-update-ed-expkeysig/</link>
					<comments>https://blog.smsoft.it/2021/03/30/apt-update-ed-expkeysig/#respond</comments>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Tue, 30 Mar 2021 08:30:00 +0000</pubDate>
				<category><![CDATA[Debian]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[apt]]></category>
		<category><![CDATA[expire]]></category>
		<category><![CDATA[expired]]></category>
		<category><![CDATA[EXPKEYSIG]]></category>
		<category><![CDATA[keys]]></category>
		<category><![CDATA[NO_PUBKEY]]></category>
		<guid isPermaLink="false">https://blog.smsoft.it/?p=4913</guid>

					<description><![CDATA[Se durante l&#8217;aggiornamento dei pacchetti con apt viene fori un errore tipo: Le seguenti firme non erano valide: EXPKEYSIG B188E2B695BD4743 DEB.SURY.ORG Automatic Signing Key deb@sury.org bisogna procedere all&#8217;aggiornamento della firma. La cosa più veloce è questa: apt-key del B188E2B695BD4743 wget -O /etc/apt/trusted.gpg.d/php.gpg https://packages.sury.org/php/apt.gpg in alternativa, il sistema classico: apt-key adv --keyserver keys.gnupg.net --recv-keys B188E2B695BD4743 Nota ... <a title="apt update ed EXPKEYSIG &#8211; NO_PUBKEY" class="read-more" href="https://blog.smsoft.it/2021/03/30/apt-update-ed-expkeysig/" aria-label="Per saperne di più su apt update ed EXPKEYSIG &#8211; NO_PUBKEY">Leggi tutto</a>]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">Se durante l&#8217;aggiornamento dei pacchetti con apt viene fori un errore tipo:</p>



<pre class="wp-block-preformatted">Le seguenti firme non erano valide: EXPKEYSIG B188E2B695BD4743 DEB.SURY.ORG Automatic Signing Key <a href="mailto:deb@sury.org">deb@sury.org</a></pre>



<p class="wp-block-paragraph">bisogna procedere all&#8217;aggiornamento della firma. La cosa più veloce è questa:</p>



<pre class="wp-block-preformatted">apt-key del B188E2B695BD4743
wget -O /etc/apt/trusted.gpg.d/php.gpg https://packages.sury.org/php/apt.gpg</pre>



<p class="wp-block-paragraph">in alternativa, il sistema classico:</p>



<pre class="wp-block-preformatted">apt-key adv --keyserver keys.gnupg.net --recv-keys B188E2B695BD4743</pre>



<p class="wp-block-paragraph"></p>



<p class="wp-block-paragraph"><strong>Nota per Debian 11 (bullseye)</strong></p>



<p class="wp-block-paragraph">Su bullseye non è possibile aggiungere chiavi con apt-key. In questo caso la procedura da seguire è la seguente:</p>



<pre class="wp-block-preformatted">curl -fsSL https://packages.sury.org/php/apt.gpg | gpg --dearmor -o /usr/share/keyrings/phpsury-archive-keyring.gpg</pre>



<p class="wp-block-paragraph">Poi modificare il file <strong>/etc/apt/sources.list.d/php.list</strong> e sostituire:</p>



<pre class="wp-block-preformatted">deb https://packages.sury.org/php/ bullseye main</pre>



<p class="wp-block-paragraph">con</p>



<pre class="wp-block-code"><code>deb &#91;signed-by=/usr/share/keyrings/phpsury-archive-keyring.gpg] https://packages.sury.org/php/ bullseye main</code></pre>



<p class="wp-block-paragraph"></p>



<p class="wp-block-paragraph">enjoy!</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.smsoft.it/2021/03/30/apt-update-ed-expkeysig/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>apt: NO_PUBKEY B188E2B695BD4743</title>
		<link>https://blog.smsoft.it/2019/09/17/apt-no_pubkey-b188e2b695bd4743/</link>
					<comments>https://blog.smsoft.it/2019/09/17/apt-no_pubkey-b188e2b695bd4743/#respond</comments>
		
		<dc:creator><![CDATA[admin]]></dc:creator>
		<pubDate>Tue, 17 Sep 2019 08:30:35 +0000</pubDate>
				<category><![CDATA[Debian]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[apt]]></category>
		<category><![CDATA[B188E2B695BD4743]]></category>
		<category><![CDATA[EXPKEYSIG]]></category>
		<category><![CDATA[NO_PUBKEY]]></category>
		<category><![CDATA[sury.org]]></category>
		<guid isPermaLink="false">https://blog.smsoft.it/?p=4446</guid>

					<description><![CDATA[Il repository sury.org utilizzato per l&#8217;installazione delle varie versioni PHP, a seguito di aggiornamenti della firma, può riportare il seguente errore durante l&#8217;update dei pacchetti: Le seguenti firme non sono state verificate perché la chiave pubblica non è disponibile: NO_PUBKEY B188E2B695BD4743 Per risolvere basta digitare: apt-key del B188E2B695BD4743 wget -O /etc/apt/trusted.gpg.d/php.gpg https://packages.sury.org/php/apt.gpg enjoy!]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">Il repository <strong>sury.org</strong> utilizzato per l&#8217;installazione delle varie versioni <strong>PHP</strong>, a seguito di aggiornamenti della firma, può riportare il seguente errore durante l&#8217;update dei pacchetti:</p>



<pre class="wp-block-preformatted">Le seguenti firme non sono state verificate perché la chiave pubblica non è disponibile: NO_PUBKEY B188E2B695BD4743</pre>



<p class="wp-block-paragraph">Per risolvere basta digitare:</p>



<pre class="wp-block-preformatted">apt-key del B188E2B695BD4743
wget -O /etc/apt/trusted.gpg.d/php.gpg https://packages.sury.org/php/apt.gpg</pre>



<p class="wp-block-paragraph">enjoy!</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.smsoft.it/2019/09/17/apt-no_pubkey-b188e2b695bd4743/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
