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.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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:
Code:
https://usageinfo.website.com/
Resolving usageinfo.website.com... xxx.xxx.xxx.xxx
Connecting to usageinfo.website.com|xxx.xxx.xxx.xxx|:443... connected.
ERROR: cannot verify usageinfo.website.com's certificate, issued by â/C=US/O=VeriSign, Inc./OU=VeriSign Trust Network/OU=Terms of use at https://www.verisign.com/rpa (c)10/CN=VeriSign Class 3 Secure Server CA - G3â
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.
- Are you sure they didn't change anything else on the server?
- What is the http code returned ?
- Maybe you need to use the Basic authentication (encode a "loginassword" in base64)
Last edited by MisterBark; 07-04-2012 at 10:07 PM.
First I would put --no-check-certificate before, but I don't think it's the problem.
Tried that, but no change.
Quote:
- Are you sure they didn't change anything else on the server?
I have no idea, or know how to find out
Quote:
- What is the http code returned ?
302. When it fails on login, it just returns the main page, so it'll always be 302.
Quote:
- 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.
Update: I believe I've got the proper certificate.
I used openssl to obtain the cert, and then ran through openssl again to verify, recieving an OK status.
So, now it appears as though my --post-data "UserName=user&Password=password" does not work, and so I'm thinking it's because now it's using requiring encryption, so perhaps a different approach?
I'm still trying with both wget & curl to see which one wins.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.