News for hackers. Stuff that matters.
Re:Security alerts on GitHub by BugsJustFindMe on Thursday November 16, 2017 @01:33PM (#15715210)
Appears to be only for Ruby gems and Node.js packages. It's a start, though I was hoping to be able to indicate C++ library dependencies.

The lack of Python requirements.txt support is a bit odd, since it's conceptually quite similar to the two supported mechanisms.

Re:Security alerts on GitHub by Dunedan on Thursday November 16, 2017 @02:51PM (#15715943)
In the meanwhile you can use a combination of pre-commit (http://pre-commit.com/) and safety-db (https://github.com/pyupio/safety-db) in form of https://github.com/Lucas-C/pre-commit-hooks-safety

That allows you to run a check for vulnerable packages before each commit and via CI.

Re:Security alerts on GitHub by nerdwaller on Thursday November 16, 2017 @09:24PM (#15718466)
Also for python `pipenv check`[0] to do security checks (obviously for known vulnerabilities) if you use pipenv[1] to manage dependencies.

[0] https://docs.pipenv.org/advanced.html#detection-of-security-...

[1] https://github.com/kennethreitz/pipenv

Re:Security alerts on GitHub by username223 on Thursday November 16, 2017 @07:14PM (#15717921)
Another cost of every language wanting at least one of its own dependency managers, often tightly integrated with the build system. The least-bad solution at this point would be to spin up a clean image, install the package in question, and figure out what else was also installed.
Re:Security alerts on GitHub by dflock on Thursday November 16, 2017 @01:48PM (#15715328)
> with Python support coming in 2018.
Re:Security alerts on GitHub by sciurus on Thursday November 16, 2017 @04:07PM (#15716628)
Yeah, but for proper python support you need to handle setup.py too, which being python code is more complex.

https://python-packaging.readthedocs.io/en/latest/dependenci...

Re:Security alerts on GitHub by scrollaway on Thursday November 16, 2017 @05:19PM (#15717212)
Re:Security alerts on GitHub by nikcub on Thursday November 16, 2017 @07:08PM (#15717874)
and Pipfile - which is what i've switched to in recent projects, example[0]

Altho you can write to one of the other formats or read from it - you'd have to tell the scanner what the true build source is

[0] https://github.com/kennethreitz/pipenv/blob/master/Pipfile

Re:Security alerts on GitHub by nerdwaller on Thursday November 16, 2017 @09:25PM (#15718475)
I mentioned this elsewhere here, but check out `pipenv check`[0] and just run it in CI or as a precommit hook.

[0] https://docs.pipenv.org/advanced.html#detection-of-security-...

Re:Security alerts on GitHub by jdc0589 on Thursday November 16, 2017 @07:58PM (#15718148)
I imagine they are just going to pick one.
Re:Security alerts on GitHub by Rotareti on Friday November 17, 2017 @01:36AM (#15719589)
> The lack of Python requirements.txt support is a bit odd

I hope they go with Pipfile/Pipfile.lock [0] and pipenv [1] rigth away!

[0] https://github.com/pypa/pipfile

[1] https://github.com/kennethreitz/pipenv

Re:Security alerts on GitHub by pknopf on Thursday November 16, 2017 @01:39PM (#15715268)
How would you effectively do this in a way that is cross-build-platform friendly? CMAKE? autoconf? submodules?

I don't see that happening.

Re:Security alerts on GitHub by adekok on Thursday November 16, 2017 @02:47PM (#15715898)
Text files?

If people get value from it, editing a simple text file once or twice a year wouldn't be difficult.

Re:Security alerts on GitHub by scott_karana on Thursday November 16, 2017 @03:58PM (#15716561)
Adding a second source of truth sounds like a bad idea to me. Now you have to update it in lockstep? No thanks.
Re:Security alerts on GitHub by icebraining on Thursday November 16, 2017 @04:39PM (#15716905)
You could make the build tool generate this standard file.
Re:Security alerts on GitHub by scott_karana on Thursday November 16, 2017 @06:11PM (#15717568)
It's still a many to many problem in both cases.

Option 1: Adding feature to npm/composer/gem/pip ad infinitum

Option 2: add per-language parser support to the alerting tool instead.

Option 2 doesn't necessitate a new (information-duplicating, still potentially error prone) standard, and can likely leverage available, tested libraries ;-)

Re:Security alerts on GitHub by matt_kantor on Thursday November 16, 2017 @08:53PM (#15718369)
On the other hand, option #1 requires neither effort nor consent from GitHub to onboard new languages/dependency managers.
Re:Security alerts on GitHub by adekok on Thursday November 16, 2017 @09:22PM (#15718459)
A few things things:

* any non Javascript / ruby / go languages don't have standard packages, package names, etc.

* any non Javascript / ruby / go languages may be using one of many build systems. It's just too hard to troll through random build systems to see what dependencies are used

* therefore, a simple text file is what will work, and is what will be trivial for everyone to use

* if you find it too hard to update one line in a text file when you add (for example) a new dependency on libldap... you shouldn't be programming

Re:Security alerts on GitHub by _Codemonkeyism on Friday November 17, 2017 @01:30AM (#15719554)
" any non Javascript / ruby / go"

Would have thought Maven popularized standard package names and build dependency (POM) files.

Re:Security alerts on GitHub by oblio on Friday November 17, 2017 @05:49AM (#15720895)
Even more than that, Maven came up with the groupId concept, which I think is under-utilized by many other package managers... The leftpad fiasco could have been mitigated with it, for example.
Re:Security alerts on GitHub by adekok on Friday November 17, 2017 @07:14AM (#15721367)
How many C / C++ projects use Maven?
Re:Security alerts on GitHub by pknopf on Thursday November 16, 2017 @02:51PM (#15715946)
I see.

A text file that just declares that "this project uses lib 2.1". It isn't a part of the build system in any way.

That would be awesome.

Re:Security alerts on GitHub by pavel_lishin on Thursday November 16, 2017 @03:57PM (#15716551)
Support for POM files would be nice, too.
Re:Security alerts on GitHub by RhodesianHunter on Thursday November 16, 2017 @05:59PM (#15717493)
Especially since adding pom and/or gradle files would knock out support for a half-dozen languages.
Re:Security alerts on GitHub by gonzoyumo on Thursday November 16, 2017 @07:17PM (#15717935)
https://gemnasium.com just launched maven support, you can give it a try!
Re:Security alerts on GitHub by rasjani on Friday November 17, 2017 @02:25AM (#15719856)
Point probably for lacking support for other than npm&gem packages is that for those langs/formats, there is a good sources for getting that sort of data externally.
Re:Security alerts on GitHub by hobarrera on Friday November 17, 2017 @02:18PM (#15725100)
Actually, Pipfiles are more akin to the two supported mechanisms, requirements.txt is not always used with version pinning