News for hackers. Stuff that matters.
Re:NVD Damage Continued by DannyBee on Tuesday June 13, 2023 @12:12PM (#36312354)
So?

That's a different problem to deal with a different way.

People keep lying to me, so i'm going to ignore what they tell me and make it up myself doesn't seem like it's going to generate great results.

Put another way - "NVD making stuff up that is not accurate" is not a solution for "other people making stuff up that is not accurate".

If you want responsibility, you have to incentivize it somehow, whether carrot or stick. This doesn't achieve that. They can tell their customers whatever they want, and then blame any difference on NVD being mean.

Re:NVD Damage Continued by _a_a_a_ on Tuesday June 13, 2023 @12:59PM (#36313177)
>> vendors underreporting and underscoring their security issues

> So?

So he comprehensively refuted your point by explaining why

Re:NVD Damage Continued by tptacek on Tuesday June 13, 2023 @05:18PM (#36317514)
No, he called out the obvious reason why NVD would decide it needs to operate this way, without acknowledging that the process they've come up with doesn't work, and is sort of an industry embarassment.