<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Troubleshooting RPM setup with Code Sign Protect in Network Security Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/network-security-discussions/troubleshooting-rpm-setup-with-code-sign-protect/m-p/1416444#M423</link>
    <description>&lt;P&gt;Hi Warriors! Kevin here from Venafi coming at you tackling the latest recent issue. I look for the most common issues and answer them in the Venafi Warrior Community so you can get help even faster.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Today I am sharing knowledge from the customer support team on some helpful ways to troubleshoot your Code Sign Protect signing operations when using rpm. RPM Package Manager is bundled with some versions of Linux distributions of AmzLinux, CentOS 7, and others.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;Summary:&lt;/P&gt;&lt;P&gt;Venafi Code Signing operations can be used for signing with rpm. However, some additional configuration may be necessary in order to be sure rpm works as expected.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;More Info:&lt;/P&gt;&lt;P&gt;Older versions of rpm always prompt for a password even if there is no password configured for the gpg key being used. If you have not configured a password, you can simply hit enter to proceed without entering any information for the password.&lt;/P&gt;&lt;P&gt;This is because rpmsign.c directly calls the getpass() function, and there is no way to bypass this. This behavior is corrected in newer versions of rpm.&lt;/P&gt;&lt;P&gt;By default, macros for gpg are hard coded to /usr/bin/gpg2, and they will need to be adjusted. Create file ~/.rpmmacros with contents as follows:&lt;/P&gt;&lt;P&gt;%_signature            gpg&lt;/P&gt;&lt;P&gt;%_gpg_name            myemail@example.org&lt;/P&gt;&lt;P&gt;%__gpg                /home/myexampleuser/lean-static-gpg/gnupg/bin/gpg&lt;/P&gt;&lt;P&gt;%__gpg_sign_cmd        %\{__gpg} gpg --batch --no-verbose --force-v3-sigs --no-armor --no-secmem-warning -u "%\{_gpg_name}" -sbo %\{__signature_filename} %\{__plaintext_filename}&lt;/P&gt;&lt;P&gt;     3. With this in place, you can sign as expected:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;rpmsign --addsign mypackage.rpm&lt;/P&gt;&lt;P&gt;Again, if using an older version of rpm like those bundled in AmzLinux2 or CentOS 7, rpm will prompt for a pass phrase whether or not one is in place. You can simply hit enter and proceed as normal.&lt;/P&gt;</description>
    <pubDate>Mon, 21 Mar 2022 20:07:35 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2022-03-21T20:07:35Z</dc:date>
    <item>
      <title>Troubleshooting RPM setup with Code Sign Protect</title>
      <link>https://live.paloaltonetworks.com/t5/network-security-discussions/troubleshooting-rpm-setup-with-code-sign-protect/m-p/1416444#M423</link>
      <description>&lt;P&gt;Hi Warriors! Kevin here from Venafi coming at you tackling the latest recent issue. I look for the most common issues and answer them in the Venafi Warrior Community so you can get help even faster.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Today I am sharing knowledge from the customer support team on some helpful ways to troubleshoot your Code Sign Protect signing operations when using rpm. RPM Package Manager is bundled with some versions of Linux distributions of AmzLinux, CentOS 7, and others.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;Summary:&lt;/P&gt;&lt;P&gt;Venafi Code Signing operations can be used for signing with rpm. However, some additional configuration may be necessary in order to be sure rpm works as expected.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;More Info:&lt;/P&gt;&lt;P&gt;Older versions of rpm always prompt for a password even if there is no password configured for the gpg key being used. If you have not configured a password, you can simply hit enter to proceed without entering any information for the password.&lt;/P&gt;&lt;P&gt;This is because rpmsign.c directly calls the getpass() function, and there is no way to bypass this. This behavior is corrected in newer versions of rpm.&lt;/P&gt;&lt;P&gt;By default, macros for gpg are hard coded to /usr/bin/gpg2, and they will need to be adjusted. Create file ~/.rpmmacros with contents as follows:&lt;/P&gt;&lt;P&gt;%_signature            gpg&lt;/P&gt;&lt;P&gt;%_gpg_name            myemail@example.org&lt;/P&gt;&lt;P&gt;%__gpg                /home/myexampleuser/lean-static-gpg/gnupg/bin/gpg&lt;/P&gt;&lt;P&gt;%__gpg_sign_cmd        %\{__gpg} gpg --batch --no-verbose --force-v3-sigs --no-armor --no-secmem-warning -u "%\{_gpg_name}" -sbo %\{__signature_filename} %\{__plaintext_filename}&lt;/P&gt;&lt;P&gt;     3. With this in place, you can sign as expected:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;rpmsign --addsign mypackage.rpm&lt;/P&gt;&lt;P&gt;Again, if using an older version of rpm like those bundled in AmzLinux2 or CentOS 7, rpm will prompt for a pass phrase whether or not one is in place. You can simply hit enter and proceed as normal.&lt;/P&gt;</description>
      <pubDate>Mon, 21 Mar 2022 20:07:35 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/network-security-discussions/troubleshooting-rpm-setup-with-code-sign-protect/m-p/1416444#M423</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2022-03-21T20:07:35Z</dc:date>
    </item>
  </channel>
</rss>

