About Eric Woodman

Eric Woodman · 06-12-2013

I have two ASA 5520 devices I am configuring which require FIPS 140-2 compliance. One of the FIPS 140-2 requirement states that the device must not use 512-bit or 768-bit RSA keys. I generated a key-pair using modulus 1024 which creates a "<Default-R...

Eric Woodman · 07-08-2013

Thanks for the information Luis. It looks like TAC is my next step.I appreciate your time and help,EOW

Eric Woodman · 07-08-2013

Hi Luis,Thank you again!I am definitely running version 2:***Begin***RADIO-5520# sho run sshssh timeout 5ssh version 2ssh key-exchange group dh-group1-sha1RADIO-5520# sho ssh sessions SID Client IP Version Mode Encryption Hmac St...

Eric Woodman · 07-08-2013

Hi Luis,Thank you for your reply. Output of the "sho crypto key mypubkey rsa" command follows:***Begin***RADIO-5520# sho crypto key mypubkey rsaKey pair was generated at: 08:55:07 PDT Jul 8 2013Key name: Usage: General Purpose Key Modulus Size (bits...

Eric Woodman · 04-12-2013

This solution worked perfectly for me. I suspect my problem arose because I enabled the http server before entering the activation key for 3des. Once enabling the other encryption options for ssl my SDM was fully functional.Thanks!!

Member Since	‎04-12-2013 12:52 PM
Date Last Visited	‎08-18-2017 04:03 AM
Posts	5
Total Helpful Votes Received	5

User Statistics

User Activity

FIPS Compliant RSA Key

Re: FIPS Compliant RSA Key

Re: FIPS Compliant RSA Key

FIPS Compliant RSA Key

Cannot connect to ASA using https