You are not logged in.
Pages: 1
I am using a script that shows if I have new messages on gmail. the script is:
import os
import string
#Enter your username and password below within double quotes
# eg. username="username" and password="password"
username="xx"
password="xx"
com="wget -O - https://"+username+":"+password+"@mail.google.com/mail/feed/atom --no-check-certificate"
temp=os.popen(com)
msg=temp.read()
index=string.find(msg,"<fullcount>")
index2=string.find(msg,"</fullcount>")
fc=int(msg[index+11:index2])
if fc==0:
print "0 new"
else:
print str(fc)+" new"
When I run conky, I receive these errors:
--2008-02-07 06:04:38-- https://username:*password*@mail.google.com/mail/feed/atom
Resolving mail.google.com... 66.249.83.19
Connecting to mail.google.com|66.249.83.19|:443... connected.
WARNING: cannot verify mail.google.com's certificate, issued by `/C=ZA/O=Thawte Consulting (Pty) Ltd./CN=Thawte SGC CA':
Unable to locally verify the issuer's authority.
HTTP request sent, awaiting response... 401 Unauthorized
Connecting to mail.google.com|66.249.83.19|:443... connected.
WARNING: cannot verify mail.google.com's certificate, issued by `/C=ZA/O=Thawte Consulting (Pty) Ltd./CN=Thawte SGC CA':
Unable to locally verify the issuer's authority.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/xml]
Saving to: `STDOUT'[ <=> ] 369 --.-K/s in 0s
2008-02-07 06:04:43 (98.3 MB/s) - `-' saved [369]
As far I ask I can tell, this wasnt happening before. This error seems to slow down conky.
Any ideas on how to fix it?
Thanks
Offline
have a look at your computer clock/time
Offline
huh?
Offline
Here is another script you might try:
http://conky.sourceforge.net/gmail.pl
Instructions are in the script.
Offline
thanks. I'll try that.
im just wondering about certificates in general, though. I've had similiar trouble accessing gmail through claws and using https trackers in rtorrent. I was able to solve the rtorrent issue, but not the gmail issue (which is probably related to my conky script errors).
any tips for getting gmail certificates installed?
Offline
I've submitted a package to the AUR called, 'ca-certificates', that is a port of the Gentoo ebuild by the same name. It provides the common root certificates.
In the mean time, wget has an option that you can use to tell it to not try to validate certificates. It will still print out the annoying warnings though. The option is "--no-check-certificate".
EDIT: I guess it helps to read the previous posts more closely... I see that you are already using that option.
EDIT2: I just tested the gmail wget command with my own gmail account. (I have the ca-certificates package installed of course ) It worked without any of the annoying certificate warnings.
Last edited by yabbadabbadont (2008-02-17 00:46:57)
Offline
I've submitted a package to the AUR called, 'ca-certificates', that is a port of the Gentoo ebuild by the same name. It provides the common root certificates.
In the mean time, wget has an option that you can use to tell it to not try to validate certificates. It will still print out the annoying warnings though. The option is "--no-check-certificate".
EDIT: I guess it helps to read the previous posts more closely... I see that you are already using that option.
EDIT2: I just tested the gmail wget command with my own gmail account. (I have the ca-certificates package installed of course ) It worked without any of the annoying certificate warnings.
Nice - thanks yabbadabbadont.
Offline
i prefer to install curl, and use the cert file in that.
"Be conservative in what you send; be liberal in what you accept." -- Postel's Law
"tacos" -- Cactus' Law
"t̥͍͎̪̪͗a̴̻̩͈͚ͨc̠o̩̙͈ͫͅs͙͎̙͊ ͔͇̫̜t͎̳̀a̜̞̗ͩc̗͍͚o̲̯̿s̖̣̤̙͌ ̖̜̈ț̰̫͓ạ̪͖̳c̲͎͕̰̯̃̈o͉ͅs̪ͪ ̜̻̖̜͕" -- -̖͚̫̙̓-̺̠͇ͤ̃ ̜̪̜ͯZ͔̗̭̞ͪA̝͈̙͖̩L͉̠̺͓G̙̞̦͖O̳̗͍
Offline
i prefer to install curl, and use the cert file in that.
That would be fine, if it were installed in such a way that openssl would use it by default, instead of forcing users to figure out how to get their apps to use it. Most of whom don't even know why they are getting certificate errors and/or warnings in the first place.
I just figured that, if it was good enough for Debian (and Gentoo's ebuild uses the Debian deb), then it would be good enough for me too. Since I had already gone to the trouble of porting the ebuild to a PKGBUILD, I figured that I might as well share the result to any who would like it.
Offline
Pages: 1