Live data from Hacker News

Code scanning for security vulnerabilities now available

github.blog

51–60 of 125 posts

Re: Code scanning for security vulnerabilities now available

#51
Bio Etihad cancellation policy - Read how to cancel etihad flight booking within 24 hour and how to get refund on cancellation.More info: https://airlinesreservationsdeals.com/etihad-airways/flight-cancellation-policy/" rel="nofollow">https://airlinesreservationsdeals.com/etihad-airways/flight-...

Re: Code scanning for security vulnerabilities now available

#52
post #38

Earlier quoted context omitted.

There's a genuine security fatigue issue (much like event fatigue) that comes from false positives. Unfortunately that doesn't reduce the value of the scanning - the onus is on the false positives. At the very least, running and pruning scans should happen on projects so that at least we can have the conversation. It's like PCI (as an example, not an ideal); PCI isn't perfect, but at least it encourages a conversatio…

Automated proof of vulnerability is valuable. Kafkaesque pattern matching, is not.

These warnings are disorientingly and illogically complex in a surreal or nightmarish way?

Re: Code scanning for security vulnerabilities now available

#53

Open Source authors [1] [2] (including myself) have complained of automatic security scans. They yield way too many false positives, increasing the burden of maintaining repositories. Specially troublesome are when e.g. the "vulnerability" (if it's even one) is in a devDependency that is not deployed to production. In theory automatic vulnerability scans sounds great, but having every repo ping you with not-actually-…

At some point many beginner devs migrated from StackOverflow to Github because their really bad question were being closed there, and now they just overwhelm open source authors

I'm glad it's not just me seeing this - My repos aren't even that popular and some of the issues just seem to be "help me build my project..."

Re: Code scanning for security vulnerabilities now available

#55

Bio Etihad cancellation policy - Read how to cancel etihad flight booking within 24 hour and how to get refund on cancellation.More info: https://airlinesreservationsdeals.com/etihad-airways/flight-...

Read how to cancel etihad flight booking within 24 hour and how to get refund on cancellation.More info: https://airlinesreservationsdeals.com/etihad-airways/flight-...

Re: Code scanning for security vulnerabilities now available

#56
post #14

In the not-so-distant future: Code snippet scanning for copyright infringement or Stack Overflow attribution. 2 years? 4?

>In the not-so-distant future: Code snippet scanning for copyright infringement

Will never happen. Can you imagine what would occur if Github started harrassing private repo owners for including GPL licensed code? Or automatically making them public? All their customers would bolt immediately. Copyright infringement is Github's bread and butter.

Stack Overflow attribution is equally unlikely. The same group that says Oracle's claim that Java's API is not original and unworthy of copyright protection, cannot then turn around and claim 30 lines of code from SO is original and deserves recognition.

Re: Code scanning for security vulnerabilities now available

#57
post #52

Earlier quoted context omitted.

Automated proof of vulnerability is valuable. Kafkaesque pattern matching, is not.

These warnings are disorientingly and illogically complex in a surreal or nightmarish way?

You did find a mild way of putting it.

Re: Code scanning for security vulnerabilities now available

#58

Open Source authors [1] [2] (including myself) have complained of automatic security scans. They yield way too many false positives, increasing the burden of maintaining repositories. Specially troublesome are when e.g. the "vulnerability" (if it's even one) is in a devDependency that is not deployed to production. In theory automatic vulnerability scans sounds great, but having every repo ping you with not-actually-…

I don't mind help in finding these problems, what I LOATHE though is when people trust the tool more than me and (for example) prevent me from pushing something that disagrees with the tool. So somewhere I imagine some manager will force their devs to make this tool happy and that's wrong.

Re: Code scanning for security vulnerabilities now available

#59
post #18

Pass from me, given the published pricing is: > Contact Sales to learn more

Recently I learned in a conversation [0] (about SaaS in general, not GitHub in particular) that you passing is actually the desired outcome and it's by design.

So, I guess, "well done"? (it hurts a little though, I'm too in the camp of wanting to see the pricing beforehand)

[0]: https://news.ycombinator.com/item?id=24630106

Re: Code scanning for security vulnerabilities now available

#60
post #38

Earlier quoted context omitted.

There's a genuine security fatigue issue (much like event fatigue) that comes from false positives. Unfortunately that doesn't reduce the value of the scanning - the onus is on the false positives. At the very least, running and pruning scans should happen on projects so that at least we can have the conversation. It's like PCI (as an example, not an ideal); PCI isn't perfect, but at least it encourages a conversatio…

Automated proof of vulnerability is valuable. Kafkaesque pattern matching, is not.

That's only true based on a certain level of care, which sadly is not always the case. Say you have a codebase that wasn't built well. Let's say your code scanner finds you at the very least the text "-----BEGIN R/DSA PRIVATE KEY-----*-----END R/DSA PRIVATE KEY-----". In my codebases that'll find nothing, but for many people, they just found SSH keys committed in plaintext. The same is true for any 1k/2k (++etc) string. It highlights what could be a private key and worth at least looking at.

Neither is proof of a vulnerability. Both I will gladly, always 100% validate.

Post reply on HN