Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have a web page that I had a script run at midnight and log on to and extract information to put into a database.
The maintainers of the page have upgraded and (good for them) made it more secure with SSL. However, now I'm trying to rewrite my script, and am unable to get past the SSL. The closest I get is a message that it cannot verify the certificate, so I know it's trying.
This will return me to the logon screen, instead of logging on. If I remove the "--no-check-certificate" option, then I get:
Resolving usageinfo.website.com... xxx.xxx.xxx.xxx
Connecting to usageinfo.website.com|xxx.xxx.xxx.xxx|:443... connected.
Unable to locally verify the issuer's authority.
To connect to usageinfo.website.com insecurely, use "--no-check-certificate".
First I would put --no-check-certificate before, but I don't think it's the problem.
Tried that, but no change.
- Are you sure they didn't change anything else on the server?
I have no idea, or know how to find out
- What is the http code returned ?
302. When it fails on login, it just returns the main page, so it'll always be 302.
- Maybe you need to use the Basic authentication (encode a "login : password" in base64)
That did not work.
It appears as though I'm unable to verify the Verisign CA certificate. There's options in wget to specify a file or directory to check certificates, but searching online, I've not found how to obtain such files that I could reference.