SSL peers problem running cif_crontool first time

[GoogleCodeExporter]

I just did a new install of CIF and thought I did all the right steps, ie. all 
the installs and builds finished with no errors.  For the initial run of:

time /opt/cif/bin/cif_crontool -f -d && /opt/cif/bin/cif_crontool -d -p daily 
&& /opt/cif/bin/cif_crontool -d -p hourly

I'm getting these errors:

/opt/cif/bin/cif_feedparser -c /opt/cif/etc/zeustracker.cfg -f configs -T 
medium at /opt/cif/bin/cif_crontool line 145.
failed to get feed: https://zeustracker.abuse.ch/monitor.php?urlfeed=configs
500 Can't verify SSL peers without knowning which Certificate Authorities to 
trust0 at /opt/cif/bin/cif_crontool line 147.

using wget for that URL seems to work without an SSL complaint:
cif@netperf ~ $ wget https://zeustracker.abuse.ch/monitor.php?urlfeed=configs
--2012-04-20 14:00:24--  
https://zeustracker.abuse.ch/monitor.php?urlfeed=configs
Resolving zeustracker.abuse.ch... 64.12.239.115, 64.12.249.115, 205.188.27.206, 
...
Connecting to zeustracker.abuse.ch|64.12.239.115|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/xml]
Saving to: `monitor.php?urlfeed=configs'

    [ <=>                                   ] 21,396       106K/s   in 0.2s    

2012-04-20 14:00:25 (106 KB/s) - `monitor.php?urlfeed=configs' saved [21396]

And the retrieved file has what look like configs.  

The failures were for urlfeeds of binaries and configs. 

I can try to comment out the offending lines in the zeustracker.cfg file, but 
knowing how to resolve the error would be better.

Thanks,

ted

Original issue reported on code.google.com by tfrohl...@gmail.com on 20 Apr 2012 at 9:09

[GoogleCodeExporter]

what distro are you running, i'm guessing the perl modules (Crypt::SSLeay) 
doesn't have adequate access to the system certificate store...( just a guess ?)

Original comment by saxjazm...@gmail.com on 21 Apr 2012 at 11:39

[GoogleCodeExporter]

also, join the mailing list if you haven't already and re-post this. See if we 
can get insight from others who might have run into this and we can get it 
documented...

Original comment by saxjazm...@gmail.com on 23 Apr 2012 at 12:31

[GoogleCodeExporter]

Original comment by saxjazm...@gmail.com on 4 May 2012 at 12:09

• Changed state: WontFix