<?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 Re: C9800-40 Crypto Log in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/c9800-40-crypto-log/m-p/4787621#M252675</link>
    <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&lt;SPAN&gt;-&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;Review the&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;9800&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp;device configuration&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;with the CLI command :&lt;/SPAN&gt;&lt;STRONG&gt;&amp;nbsp;&lt;/STRONG&gt;&lt;FONT color="#008000"&gt;&lt;STRONG&gt;show&amp;nbsp; tech&lt;/STRONG&gt;&amp;nbsp;&amp;nbsp;&lt;STRONG&gt;&lt;U&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;wireless&lt;/U&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;, have the output analyzed by&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://cway.cisco.com/tools/WirelessAnalyzer/" target="_blank" rel="noopener nofollow noreferrer" data-saferedirecturl="https://www.google.com/url?q=https://cway.cisco.com/tools/WirelessAnalyzer/&amp;amp;source=gmail&amp;amp;ust=1662270212514000&amp;amp;usg=AOvVaw1v8X824xUFwNwiDM_o5Fxf"&gt;https://cway.cisco.com/&lt;WBR /&gt;tools/WirelessAnalyzer/&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp; , please note do not use classical&lt;/SPAN&gt;&lt;FONT color="#FF0000"&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;show tech-support&lt;/FONT&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;(short version) , use the command denoted in green for Wireless Analyzer.&amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;EM&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;You may get more insights as to where this message&amp;nbsp; is applicable , or why it occurs ,&amp;nbsp;&lt;BR /&gt;&lt;/EM&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Also post the output of :&amp;nbsp; &lt;STRONG&gt;show wireless mobility summary&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;M.&lt;/P&gt;</description>
    <pubDate>Mon, 06 Mar 2023 13:44:41 GMT</pubDate>
    <dc:creator>Mark Elsen</dc:creator>
    <dc:date>2023-03-06T13:44:41Z</dc:date>
    <item>
      <title>C9800-40 Crypto Log</title>
      <link>https://community.cisco.com/t5/wireless/c9800-40-crypto-log/m-p/4787519#M252670</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;The following log appears on the 9800 device. Is there a cause and solution?&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;%CRYPTO_ENGINE-4-CSDL_&lt;/SPAN&gt;&lt;WBR /&gt;&lt;SPAN&gt;COMPLIANCE_RSA_WEAK_KEYS: RSA keypair CISCO_IDEVID_SUDI_LEGACY is in violation of Cisco security compliance guidelines and will be rejected by future releases.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Model : C9800-40 2EA HA&lt;/P&gt;
&lt;P&gt;Version : 17.6.5&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 06 Mar 2023 01:07:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/c9800-40-crypto-log/m-p/4787519#M252670</guid>
      <dc:creator>김성진</dc:creator>
      <dc:date>2023-03-06T01:07:49Z</dc:date>
    </item>
    <item>
      <title>Re: C9800-40 Crypto Log</title>
      <link>https://community.cisco.com/t5/wireless/c9800-40-crypto-log/m-p/4787621#M252675</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&lt;SPAN&gt;-&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;Review the&lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;9800&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp; &amp;nbsp;device configuration&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;with the CLI command :&lt;/SPAN&gt;&lt;STRONG&gt;&amp;nbsp;&lt;/STRONG&gt;&lt;FONT color="#008000"&gt;&lt;STRONG&gt;show&amp;nbsp; tech&lt;/STRONG&gt;&amp;nbsp;&amp;nbsp;&lt;STRONG&gt;&lt;U&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;wireless&lt;/U&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;, have the output analyzed by&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;A href="https://cway.cisco.com/tools/WirelessAnalyzer/" target="_blank" rel="noopener nofollow noreferrer" data-saferedirecturl="https://www.google.com/url?q=https://cway.cisco.com/tools/WirelessAnalyzer/&amp;amp;source=gmail&amp;amp;ust=1662270212514000&amp;amp;usg=AOvVaw1v8X824xUFwNwiDM_o5Fxf"&gt;https://cway.cisco.com/&lt;WBR /&gt;tools/WirelessAnalyzer/&lt;/A&gt;&lt;SPAN&gt;&amp;nbsp; , please note do not use classical&lt;/SPAN&gt;&lt;FONT color="#FF0000"&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;show tech-support&lt;/FONT&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;(short version) , use the command denoted in green for Wireless Analyzer.&amp;nbsp; &amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;EM&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;You may get more insights as to where this message&amp;nbsp; is applicable , or why it occurs ,&amp;nbsp;&lt;BR /&gt;&lt;/EM&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; Also post the output of :&amp;nbsp; &lt;STRONG&gt;show wireless mobility summary&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;M.&lt;/P&gt;</description>
      <pubDate>Mon, 06 Mar 2023 13:44:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/c9800-40-crypto-log/m-p/4787621#M252675</guid>
      <dc:creator>Mark Elsen</dc:creator>
      <dc:date>2023-03-06T13:44:41Z</dc:date>
    </item>
    <item>
      <title>Re: C9800-40 Crypto Log</title>
      <link>https://community.cisco.com/t5/wireless/c9800-40-crypto-log/m-p/4787638#M252679</link>
      <description>&lt;P&gt;Looks to me like some SSH keys issue looking at the errors&lt;/P&gt;
&lt;P&gt;can you post show IP ssh and show ssh&amp;nbsp; ( also trust point config smart license here)&lt;/P&gt;</description>
      <pubDate>Mon, 06 Mar 2023 08:32:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/c9800-40-crypto-log/m-p/4787638#M252679</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2023-03-06T08:32:35Z</dc:date>
    </item>
    <item>
      <title>Re: C9800-40 Crypto Log</title>
      <link>https://community.cisco.com/t5/wireless/c9800-40-crypto-log/m-p/4788029#M252695</link>
      <description>&lt;P&gt;So CSDL is the Cisco Secure Development Lifecycle.&amp;nbsp; I cannot find the IOS changes well documented anywhere (there is a more general CSDL blog) but at some point recently they introduced these changes to IOS-XE to try to remove all use of legacy hashes and ciphers and only allow the latest and strongest.&amp;nbsp; Suffice to say it was a disaster and prevented thousands of customers from upgrading IOS because it blocked all sorts of config which simply couldn't be updated overnight because of compatibility with other equipment and software which doesn't support the latest options.&amp;nbsp; As a result numerous different bugs have raised to address this and eventually in 17.6.4 they warned (and created exceptions) but did not block most legacy config.&amp;nbsp; Finally in 17.6.5 (also in 17.9.1) there is an undocumented (but still appears in numerous of Cisco's own config examples) line of config which completely disables CSDL (because it was still blocking a few odd things and they probably got tired of raising bugs to fix each one).&amp;nbsp; The change is implemented by&amp;nbsp;&lt;A href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvy60839" target="_blank" rel="noopener"&gt;https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvy60839&lt;/A&gt;&amp;nbsp;and the line of config (not even mentioned in the bug itself) is "&lt;FONT face="courier new,courier"&gt;crypto engine compliance shield disable&lt;/FONT&gt;"&lt;/P&gt;
&lt;P&gt;So on the one hand you should be moving to avoid using legacy (insecure) options like MD5/DES/3DES/SHA1 etc but in the meantime if you don't want to see those warnings then use that command.&amp;nbsp; It usually requires a reload to take effect but if it's not causing you any problems you can configure it and wait till the next planned reload.&lt;/P&gt;
&lt;P&gt;Note that the above is my opinions and what I've pieced together myself from various sources of info and observations and personal experience of half a router config disappearing when trying to upgrade before 17.6.4.&amp;nbsp; It seems the feature was not thought through very well before adding to IOS-XE and there have been multiple rounds of clean-up ever since.&lt;/P&gt;
&lt;P&gt;Also take a look at&amp;nbsp;&lt;A href="https://bst.cisco.com/bugsearch/bug/CSCvd45116" target="_blank" rel="noopener"&gt;https://bst.cisco.com/bugsearch/bug/CSCvd45116&lt;/A&gt;&amp;nbsp;and make sure you are using SSH key with strong modulus (at least 2048 - recommend 4096).&lt;/P&gt;</description>
      <pubDate>Mon, 06 Mar 2023 15:07:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/c9800-40-crypto-log/m-p/4788029#M252695</guid>
      <dc:creator>Rich R</dc:creator>
      <dc:date>2023-03-06T15:07:51Z</dc:date>
    </item>
  </channel>
</rss>

