[Emerging-Sigs] Anyone else having pulledpork update issues?
cummingsj at gmail.com
Wed Oct 26 10:23:50 EDT 2011
Sweet, thanks for letting us know!
On Wed, Oct 26, 2011 at 8:17 AM, Kevin Ross <kevross33 at googlemail.com>wrote:
> Got it, it wanted IO::Socket:SSL though never warned until I used verbose
> mode. Strange thing is one of the sensors this started happening on was
> updating happily last week and wasn't changed (though the others were and
> stopped working so I thought I was being stupid and missed something out
> then other one stopped).
> Oh well it is working now. Thanks :D
> On 26 October 2011 15:09, JJC <cummingsj at gmail.com> wrote:
>> Generally this is attributable to a certificate issue. I would run in
>> extra verbose mode (-vv) and there should be some more specific errors about
>> the connection issue.
>> On Wed, Oct 26, 2011 at 2:58 AM, Kevin Ross <kevross33 at googlemail.com>wrote:
>>> Anyone else having similar issues? Strange thing is this was working only
>>> the other week. Same thing happens if ET only, if using HTTP etc and it was
>>> updating successfully before.
>>> _____ ____
>>> `----,\ )
>>> `--==\\ / PulledPork v0.6.1 the Smoking Pig <////~
>>> .-~~~~-.Y|\\_ Copyright (C) 2009-2011 JJ Cummings
>>> @_/ / 66\_ cummingsj at gmail.com
>>> | \ \ _(")
>>> \ /-| ||'--' Rules give me wings!
>>> \_\ \_\\
>>> Checking latest MD5 for snortrules-snapshot-2910.tar.gz....
>>> Error 500 when fetching
>>> https://www.snort.org/reg-rules/snortrules-snapshot-2910.tar.gz.md5 at
>>> /etc/snort/pulledpork/pulledpork.pl line 453
>>> 'snortrules-snapshot-2910.tar.gz', '/tmp/', '
>>> https://www.snort.org/reg-rules/') called at /etc/snort/pulledpork/
>>> pulledpork.pl line 1758
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Emerging-sigs