wget unable to verify certs on fresh install
 

I'm trying to get Slackware64 14.2 up and running on a new Kaby Lake system I just built. The installation completes successfully and appears to work, but wget will not connect to any https sites, and gives the following error:

Unable to locally verify the issuer's authority.

It then recommends that I connect insecurely, which I definitely don't want to do.

I have Slackware64 running on all my other systems, so I'm totally baffled as to why this is happening. Other threads describing this problem offered solutions that did not resolve the problem for me.

Note that this is happening on a fresh, full installation. I noticed during the install that it prompted me to insert the next disc, which has never happened before, don't know if this might be a clue or not?

I also briefly compared the openssl.cnf file with the one on my laptop (which works), and could see no difference in the two.

I'm officially out of ideas at this point, if anyone could point me in the right direction it would be greatly appreciated!

I imagine that for some reason it didn't install the full Slackware. If it asked for a disk, you may have accidentally downloaded the 32bit CD ISO rather than the 64bit DVD ISO.

Can you run the following to see how many packages you have installed?

There should be around 1250 packages with a full install minus KDEI.

It might. This is only supposed to happen in case you install using several ISO images (e.g. to fit on CDs instead of a DVD). As I assume this is not the case, I would assume there is an issue with your installation media and the installation was not complete or some step failed.

tl;dr : check the integrity of the ISO image, write it again on the installation media (at low speed if on a DVD, do not forget "sync" if on an USB device) and reinstall.

PS I didn't see bassmadrigal's post before clicking "save". Let's say our responses complete each other. ;)

That was my first thought as well, but the disc I made is 2.6GB, and contains the slackware64 directory.

After running the command that bassmadrigal suggested, it shows I have 1088 packages installed, which is a few less than the estimate provided.

It seems surprising that the installation would even result in a bootable system if the disc was bad, but that does seem like the next logical step, so I will try Didier Spaier's suggestion and report back with my results.

It's possible you're having problems with the ca-certificates doinst.sh, try running this at a root prompt:

Edit: second thoughts, no, don't bother, I think Didier is right actually :)

Thanks for the suggestion, this was actually one of the solutions I found before posting here, but it didn't help.

After re-downloading and verifying new installation media, the install did not ask for another disc like it was doing previously, and I had 1251 packages installed out of the box.

wget, and everything else, appears to be working fine now. Shame on me for not at least verifying the checksum before burning the disc!

Thank ya'll so much for your assistance, it is greatly appreciated!