Latest release? about exploitdb HOT 11 CLOSED

@g0tmi1k no worries, I wrote a custom livecheck

Josephs-MacBook-Pro:Livecheckables joe$ brew livecheck exploitdb
exploitdb : 2016-12-24 ==> 2017-07-07
Josephs-MacBook-Pro:Livecheckables joe$ cat exploitdb.rb 
class Exploitdb
  livecheck :url => "https://github.com/offensive-security/exploit-database/releases",
            :regex => %r{href="/offensive-security/exploit-database/releases/tag/([0-9,\.\-]+)"}
end

from exploitdb.

There is a daily release/tag ~ https://github.com/offensive-security/exploit-database/releases
Whatever is the latest at the time of upstream should be used.
Today is 2017-07-07 ~ https://github.com/offensive-security/exploit-database/archive/2017-07-07.zip. This is what should be used.

It doesn't matter too much as the database (and its resource files), gets self updated via git (searchsploit -u).
The only thing that doesn't get updated via the in-built update system is searchsploit itself (which has had a few updates recently ~ https://github.com/offensive-security/exploit-database/commits/master/searchsploit). This is where having the homebrew package updated helps!

from exploitdb.

Thanks for the quick response! 🥇

from exploitdb.

You're welcome!
Thanks for getting homebrew updated (been meaning todo it myself for a while, just kept on forgetting!)

from exploitdb.

@g0tmi1k in that case it would be helpful to remove the explicit release https://github.com/offensive-security/exploit-database/releases/tag/2017-06-13

The GitHub API currently points to that, not the current tag. Visit https://github.com/offensive-security/exploit-database/releases/latest to see what I mean.

from exploitdb.

Thanks for the heads up @ilovezfs .
Looks like there was 2x "dated" tags the API was pointing too (13-06-2017 & 03-05-2014). Should now be fixed.

from exploitdb.

@g0tmi1k yup, much better! There is still a problem with the livecheck unfortunately:

$ brew livecheck exploitdb
exploitdb (guessed) : 2016-12-24 ==> 12312014

That ancient tag is considered greatest in terms of version order. Livecheck runs

git ls-remote https://github.com/offensive-security/exploit-database.git

and I can see there are quite a few of those that will be considered greater than the current tag.

We can probably craft a custom livecheck if it's not feasible for you to remove those.

from exploitdb.

At this stage, we are unable to remove them (there is an automated system in place that handles the daily action).
I just removed the 'manual' tags that was done by either myself or @dookie2000ca - can't really delete all the others. Sorry!

I'm not aware of livecheck and have very limited knowledge with git ls-remote, so I'm not sure how its guessing what the latest release is.
Going forward, What else could we do to help out?

from exploitdb.

Great stuff!

...I've just done brew tap homebrew/livecheck. Looks like I have a new toy to play with ;)

from exploitdb.

@g0tmi1k cool! I've just pushed the exploitdb livecheck: Homebrew/homebrew-livecheck@8e4668b

from exploitdb.

Time to update ;)

from exploitdb.