<?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 self-signed cert in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/self-signed-cert/m-p/2520237#M235555</link>
    <description>&lt;P&gt;I have a customer that is using an ASA 5515 and they are requesting the certificate for the webVPN to be changed to use 2048 bits for the Public Key. They didn't purchase or install a cert on this firewall so it is just using the default cert that was already installed and it used 1024 bits for the public key. Is there a way to change that to 2048 without having them purchase a new cert? Any help would be greatly appreciated. Thanks!&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 04:37:52 GMT</pubDate>
    <dc:creator>Benjamin Saito</dc:creator>
    <dc:date>2019-03-12T04:37:52Z</dc:date>
    <item>
      <title>self-signed cert</title>
      <link>https://community.cisco.com/t5/network-security/self-signed-cert/m-p/2520237#M235555</link>
      <description>&lt;P&gt;I have a customer that is using an ASA 5515 and they are requesting the certificate for the webVPN to be changed to use 2048 bits for the Public Key. They didn't purchase or install a cert on this firewall so it is just using the default cert that was already installed and it used 1024 bits for the public key. Is there a way to change that to 2048 without having them purchase a new cert? Any help would be greatly appreciated. Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 04:37:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/self-signed-cert/m-p/2520237#M235555</guid>
      <dc:creator>Benjamin Saito</dc:creator>
      <dc:date>2019-03-12T04:37:52Z</dc:date>
    </item>
    <item>
      <title>Yes - first generate a new</title>
      <link>https://community.cisco.com/t5/network-security/self-signed-cert/m-p/2520238#M235558</link>
      <description>&lt;P&gt;Yes - first generate a new RSA key (making sure to specify&amp;nbsp;2048-bit key length) and then a new self-signed certificate using that key. Change the binding of your outside interface to tie to that newly created certificate.&lt;/P&gt;&lt;P&gt;After doing that, your users should see the 2048-bit key usage in the SSL certificate. I've been setting up ones I do like that lately and can confirm it works. See screen shot below.&lt;/P&gt;&lt;P&gt;&lt;IMG src="https://community.cisco.com/legacyfs/online/media/capture_28.png" class="migrated-markup-image" /&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 13 Aug 2014 21:14:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/self-signed-cert/m-p/2520238#M235558</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2014-08-13T21:14:50Z</dc:date>
    </item>
  </channel>
</rss>

