Serving A Kickstart File Over Https With Self-signed Certificate

Home » CentOS » Serving A Kickstart File Over Https With Self-signed Certificate
CentOS 1 Comment

I am currently using https for the –url and –repo options in a kickstart file. The yum repo files are also set to do the same. Both of them have a setting (noverifyssl and sslverify=no, respectively) and this works as expected to pass –insecure to curl. However, I cannot figure out how to also serve the kickstart file itself. ks=user:pass@url works as a url, but I get the “Problem with the SSL CA cert” error. Is there a kernel cmdline option? I have tried different variations of noverifyssl and rd_noverifyssl but haven’t lucked upon the right one and I’m not finding the answer in google. This is CentOS6, btw.

Thanks!

One thought on - Serving A Kickstart File Over Https With Self-signed Certificate

  • I figured it out. NOVERIFYSSL is the correct kernel cmdline option. I
    must have mistyped it when I was going through all the permutations.

LEAVE A COMMENT