Open yuxisun1217 opened 2 years ago
The issue is that the Certificates.p7m uses rsaEncryption (PKCS#1 v1.5 encryption) combined with 3DES-CBC cipher, neither of which are supported in the FIPS provider on RHEL-9.1.
Azure should generate the file using RSA-OAEP encryption combined with AES128-CBC or AES256-CBC
I am facing a similar issue, wherein certificate creation fails while on FIPS enabled RHEL 9 machine. I tried to enable the FIPS providers as well but it is failing to load the fips provider. Has someone succeeded to resolve this issue?
The issue is that Azure is not FIPS compatible, there's nothing that OpenSSL or Red Hat can do to retain FIPS compliance and allow processing of those messages. Please contact Azure support about this issue.
Describe the bug: A clear and concise description of what the bug is. In RHEL-9, if use WALA as provision agent(no cloud-init) and FIPS is enabled in the image, the VM provision failed because
Failed to decrypt /var/lib/waagent/Certificates.p7m
.Distro and WALinuxAgent details (please complete the following information):
Steps
fips-mode-setup --enable
). Remove cloud-init package. Set OS.EnableFIPS=y in /etc/waagent.confLog file attached If possible, please provide the full /var/log/waagent.log file to help us understand the problem better and get the context of the issue. waagent.log