We are not building SSH implementation. We are using PuTTY code for that. And PuTTY does not have FIPS compliance.
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
It is simply a matter of compiling the OpenSSL FIPS module and then compiling OpenSSL with the FIPS option and linking to the OpenSSL FIPS module that was built.
I really am not a spammer!!! Please do unban me
Your ban algorythm refused the preceding post because of two words until I changed the spelling.
I attempted to make a second post describing the level of fail of the word filter and was banned by username and by IP address.
Both words are contained within the PuTTY quote section.
Please unban me, I am not a spammer!
Not intended as final answer, but for reference
I think that Level 1 is implied with SSL? Although that document suggests the addition of hardware level encryption.
Levels 2, 3, and 4 pretty much cannot be done in software. If someone gains physical access to your hardware you have to as sume that you've been pwned.
LEGAL WARNING: Use of PuTTY, PSCP, PSFTP and Plink is illegal in countries where encryption is outlawed. I believe it is legal to use PuTTY, PSCP, PSFTP and Plink in England and Wales and in many other countries, but I am not a la wyer and so if in doubt you should seek legal advice before downloading it. You may find this site (<invalid hyperlink removed by admin>) useful (it's a survey of cryptography laws in many countries) but I can't vouch for its correctness.