Most of the time, security update is minor version update, so it's
enough to change version numbers
in slackbuild, end everything should build fine.
So, there is no need to wait for anyone, this is Slackware, You take
care of yourself :-)
Best regards,
Adis
___
On Sat, 14 Jul 2012 14:48:31 -0700
"Bradley D. Thornton" wrote:
[...]
> There are plenty of SBo's that we don't get any sort of security
> notification on, and while it is prudent to follow the security lists
> for any such app that you install, I think that with regards to SBo's
> most of us don'
I keep an eye on the following sites to know of software
vulnerabilities:
http://web.nvd.nist.gov/view/vuln/search
http://packetstormsecurity.org/
There are times when vulnerabilities are not quickly addressed in SBo,
because it takes time to update/approve the new updates in the
repository. How
I personally keep any packages built by SBo SlackBuilds up to date with
the version hosted on slackbuilds.org (sbopkg makes this easy). If there
is reason not to for a specific application, then it is my job to make
sure it is patched. Other than that, SBo relies on its maintainers for
security upd
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
On 07/14/2012 11:49 AM, Slackware Security Team wrote:
>
> [slackware-security] pidgin (SSA:2012-195-02)
>
> New pidgin packages are available for Slackware 12.2, 13.0, 13.1, 13.37,
> and -current to fix security issues.
Something that I had
