<?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 Thanks Marvin, that Qualys in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asdm-aes-256-not-supported/m-p/2790186#M915711</link>
    <description>&lt;P&gt;Thanks Marvin, that Qualys SSL check is gold. Do you have any idea when AES-256 might be in the road-map for ASDM?&lt;/P&gt;</description>
    <pubDate>Wed, 16 Dec 2015 17:50:02 GMT</pubDate>
    <dc:creator>Phillip Simonds</dc:creator>
    <dc:date>2015-12-16T17:50:02Z</dc:date>
    <item>
      <title>ASDM AES-256 Not Supported?</title>
      <link>https://community.cisco.com/t5/network-security/asdm-aes-256-not-supported/m-p/2790184#M915709</link>
      <description>&lt;P&gt;Last night we went to upgrade our firewalls so that only TLS1.x and AES-256/SHA-1 can be used for VPN connections into the box. After doing so, ASDM stopped working, AnyConnect is still working without issue.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Java reported a SSL handshake error. I went to re-enable encryption mechanisms one by one and determined that AES-128/SHA1 is the highest encryption algorithm I can connect via ASDM on. I tried updating ASDM to the latest version and 7.5(2) won't connect on anything higher than AES-128 either. We are using&amp;nbsp;a self signed certificate on the inside interface, so I enabled ASDM on the outside where we have a valid third party cert and tried connecting via &lt;A href="https://&amp;lt;url&amp;gt;/admin" target="_blank"&gt;https://&amp;lt;url&amp;gt;/admin&lt;/A&gt; to make sure it wasn't a certificate issue, and no dice.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;It's a little odd to me that ASDM wouldn't support AES-256. I'm wondering if anyone has any ideas as to why I can't connect on AES-256 and/or a workaround. It would also be O.K. to use AES-128 for ASDM connections internally and AES-256 for VPN connections; but I don't see any way to enable the SSL encryption methods on a per-application use, it seems I can only configure them globally and am thus stuck with allowing VPN connections to use AES-128 if they so choose (I made sure connections will negotiate to AES-256 before trying AES-128, but I'd like to completely disable AES-128).&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Specs below, thanks in advance for your assistance.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;Specs&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;&lt;/SPAN&gt;ASA Version: 9.2(2)4&lt;/P&gt;
&lt;P&gt;ASDM Version: 7.4(2), I also tried 7.5(2)&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 13:38:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asdm-aes-256-not-supported/m-p/2790184#M915709</guid>
      <dc:creator>Phillip Simonds</dc:creator>
      <dc:date>2020-02-21T13:38:44Z</dc:date>
    </item>
    <item>
      <title>I think it's an ASDM</title>
      <link>https://community.cisco.com/t5/network-security/asdm-aes-256-not-supported/m-p/2790185#M915710</link>
      <description>&lt;P&gt;I think it's an ASDM limitation. I see the same thing on my ASA running the latest ASA software 9.5(2) with ASDM 7.5(2).&lt;/P&gt;
&lt;P&gt;Qualys SSL check is pretty happy with that though - I get a A- on a test against my ASA.&lt;/P&gt;</description>
      <pubDate>Tue, 15 Dec 2015 22:56:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asdm-aes-256-not-supported/m-p/2790185#M915710</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2015-12-15T22:56:25Z</dc:date>
    </item>
    <item>
      <title>Thanks Marvin, that Qualys</title>
      <link>https://community.cisco.com/t5/network-security/asdm-aes-256-not-supported/m-p/2790186#M915711</link>
      <description>&lt;P&gt;Thanks Marvin, that Qualys SSL check is gold. Do you have any idea when AES-256 might be in the road-map for ASDM?&lt;/P&gt;</description>
      <pubDate>Wed, 16 Dec 2015 17:50:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asdm-aes-256-not-supported/m-p/2790186#M915711</guid>
      <dc:creator>Phillip Simonds</dc:creator>
      <dc:date>2015-12-16T17:50:02Z</dc:date>
    </item>
    <item>
      <title>I was thinking about this and</title>
      <link>https://community.cisco.com/t5/network-security/asdm-aes-256-not-supported/m-p/2790187#M915712</link>
      <description>&lt;P&gt;I was thinking about this and found an article confirming my suspicion.&lt;/P&gt;
&lt;P&gt;ASDM is just a Java applet. As such, it uses the security afforded it by your local Java installation's libraries.&lt;/P&gt;
&lt;P&gt;I found confirmation in this TAC note:&amp;nbsp;http://www.cisco.com/c/en/us/support/docs/security/adaptive-security-device-manager/110282-asdm-tshoot.html#prblm13&lt;/P&gt;
&lt;P&gt;I tested the instructions and (...wait for it...)&amp;nbsp;- it works!&lt;/P&gt;
&lt;P&gt;I went to Oracle's download page for my Java version 8 here:&amp;nbsp;http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html&lt;/P&gt;
&lt;P&gt;I then unzipped those files and put them in the proper subdirectory according to the readme. It was a bit tricky to figure exactly which of the several Java directories ASDM was using - I did that by right clicking the process on task manager and going to the file location.&lt;/P&gt;
&lt;P&gt;(&lt;STRONG&gt;Note&lt;/STRONG&gt;: when you upgrade Oracle, it may write a new directory - so you will have to re-do this step periodically.)&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Given that, I put the two new files in, changed my SSL custom cipher to exclude AES-128 and then relaunched ASDM. I started Wireshark with a capture filter for my ASA address and watched the TLS 1.2 handshake negotiate AES-256 encryption.&lt;/P&gt;
&lt;P&gt;Along the lines of "it didn't happen if there are no pictures", extra points for the screenshot of the actual packet decode (open in new tab to zoom):&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;IMG src="https://community.cisco.com/legacyfs/online/media/asdm_aes-256.png" class="migrated-markup-image" /&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Dec 2015 23:15:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asdm-aes-256-not-supported/m-p/2790187#M915712</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2015-12-16T23:15:51Z</dc:date>
    </item>
    <item>
      <title>Thanks Mark! This worked</title>
      <link>https://community.cisco.com/t5/network-security/asdm-aes-256-not-supported/m-p/2790188#M915713</link>
      <description>&lt;P&gt;Thanks Marvin! This worked great.&lt;/P&gt;</description>
      <pubDate>Thu, 31 Dec 2015 04:13:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asdm-aes-256-not-supported/m-p/2790188#M915713</guid>
      <dc:creator>Phillip Simonds</dc:creator>
      <dc:date>2015-12-31T04:13:56Z</dc:date>
    </item>
    <item>
      <title>Marvin, you are a life saver!</title>
      <link>https://community.cisco.com/t5/network-security/asdm-aes-256-not-supported/m-p/2790189#M915714</link>
      <description>&lt;P&gt;Marvin, you are a life saver! While everyone else is adamant that installing the certificates into the Java settings was all that's needed, I could NOT get it to work, until now.&lt;/P&gt;
&lt;P&gt;Thank you sir&lt;/P&gt;</description>
      <pubDate>Fri, 27 May 2016 04:09:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asdm-aes-256-not-supported/m-p/2790189#M915714</guid>
      <dc:creator>vizualpro</dc:creator>
      <dc:date>2016-05-27T04:09:24Z</dc:date>
    </item>
    <item>
      <title>Thank you!!!</title>
      <link>https://community.cisco.com/t5/network-security/asdm-aes-256-not-supported/m-p/2790190#M915715</link>
      <description>&lt;P&gt;Thank you!!!&lt;/P&gt;</description>
      <pubDate>Tue, 26 Jul 2016 19:39:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asdm-aes-256-not-supported/m-p/2790190#M915715</guid>
      <dc:creator>JESSICA Walsh</dc:creator>
      <dc:date>2016-07-26T19:39:41Z</dc:date>
    </item>
    <item>
      <title>The jre-6u45-windows 64bit</title>
      <link>https://community.cisco.com/t5/network-security/asdm-aes-256-not-supported/m-p/2790191#M915716</link>
      <description>&lt;P&gt;The jre-6u45-windows 64bit java client works fine with many ASDM versions.&lt;BR /&gt;I had this trouble before and this was the solution.&lt;/P&gt;
&lt;P&gt;http://www.oracle.com/technetwork/java/javase/downloads/java-archive-downloads-javase6-419409.html#jre-6u45-oth-JPR&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 20 Dec 2016 23:09:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asdm-aes-256-not-supported/m-p/2790191#M915716</guid>
      <dc:creator>7layer</dc:creator>
      <dc:date>2016-12-20T23:09:14Z</dc:date>
    </item>
    <item>
      <title>Thanks so much.  As of 2017</title>
      <link>https://community.cisco.com/t5/network-security/asdm-aes-256-not-supported/m-p/2790192#M915717</link>
      <description>&lt;P&gt;Thanks so much. &amp;nbsp;As of 2017 the JAVA encryption files are located here:&lt;/P&gt;
&lt;P&gt;http://www.oracle.com/technetwork/java/javase/downloads/jce8-download-2133166.html&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Also, here is the SSL command on the ASA to use strong ciphers. &amp;nbsp;These AES256 ciphers are supported by AnyConnect 4.x, and you will score an A- with 100% strong ciphers from ssllabs.com with this setting:&lt;/P&gt;
&lt;P&gt;ssl cipher tlsv1.2 custom "DHE-RSA-AES256-SHA256:AES256-SHA256"&lt;/P&gt;</description>
      <pubDate>Fri, 19 May 2017 21:27:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asdm-aes-256-not-supported/m-p/2790192#M915717</guid>
      <dc:creator />
      <dc:date>2017-05-19T21:27:42Z</dc:date>
    </item>
    <item>
      <title>While you can work in ASDM</title>
      <link>https://community.cisco.com/t5/network-security/asdm-aes-256-not-supported/m-p/2790193#M915718</link>
      <description>&lt;P&gt;While you can work in ASDM once launched using the above cipher suite, I have not been able to launch ASDM with them enabled. If I set to medium I can launch it, then switch back to the above and control the ASA through ASDM, but that can be a PITA.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;ASDM does not work at all when ssl tlsv1.2 is set to high.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 27 Jun 2017 19:18:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asdm-aes-256-not-supported/m-p/2790193#M915718</guid>
      <dc:creator>tahscolony</dc:creator>
      <dc:date>2017-06-27T19:18:00Z</dc:date>
    </item>
    <item>
      <title>Yes it does.  I'm connected</title>
      <link>https://community.cisco.com/t5/network-security/asdm-aes-256-not-supported/m-p/2790194#M915719</link>
      <description>&lt;P&gt;Yes it does. &amp;nbsp;I'm connected to ASDM 7.8(1) now, using&amp;nbsp;&lt;/P&gt;
&lt;P&gt;ssl server-version&amp;nbsp;tlsv1.2&lt;/P&gt;
&lt;P&gt;ssl cipher tlsv1.2 custom "&lt;SPAN&gt;DHE-RSA-AES256-SHA256:AES256-SHA256"&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;which is even more restrictive than ssl cipher tlsv1.2 high.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Read Marvin's response. &amp;nbsp;You need to update JAVA with the high encryption files dowloaded from oracle. &amp;nbsp;You can't connect to ASDM unless you update JAVA. &amp;nbsp;It's not an ASDM issue, it's a java issue.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 27 Jun 2017 20:21:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asdm-aes-256-not-supported/m-p/2790194#M915719</guid>
      <dc:creator />
      <dc:date>2017-06-27T20:21:22Z</dc:date>
    </item>
  </channel>
</rss>

