Hi, Siva

We don¡¯t think this is a real problem. The cert is saved as NV variable just like any other EFI variables, there are some basic checks like verify it¡¯s a valid DER-encoded certificate before saving the certificate, and TLS config driver also provides a page to allow user to delete unused cert from system.

If someone want to fill the NV variable storage full with garbage, they can simply use SetVaraible service, not necessary to use this page.

Best Regards
Siyuan

From: Sivaraman Nainar <sivaramann@amiindia.co.in>
Sent: 2019Äê12ÔÂ24ÈÕ 13:17
To: devel@edk2.groups.io; Wu, Jiaxin <jiaxin.wu@intel.com>; Fu, Siyuan <siyuan.fu@intel.com>
Cc: Madhan B. Santharam <madhans@ami.com>; Arun Subramanian B <arunsubramanianb@ami.com>; Arun Sura Soundara Pandian <arunsuras@amiindia.co.in>; Bhuvaneshwari M R <bhuvaneshwarimr@amiindia.co.in>; Ramesh R. <rameshr@ami.com>
Subject: reg: HTTPS Certificate Validation During Enrollment

Hello all:

Right now the HTTPS Certificates are getting validated during TlsConfigCertificate()by HTTPDxe Driver.

But during enrollment of certificate via TLSDXE driver, it does not have any validation and it keep appending the TLSCaCert variable with the certificate provided.

Assume an invalid certificate keep loaded via TLS Auth configuration page, the NVRAM would be filled with garbage.

Is there any plan to have certificate validation during Enrollment?

-Siva