Do you think this is fair?
"Problems that only trigger using legacy dependencies are not considered security problems."
github.com/curl/curl/pull/1608…
#curl
Do you think this is fair?
"Problems that only trigger using legacy dependencies are not considered security problems."
github.com/curl/curl/pull/1608…
#curl
daniel:// stenberg://
Unknown parent • • •Nemo_bis 🌈
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to Nemo_bis 🌈 • • •Mika Rautio
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to Mika Rautio • • •Winni Neessen
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to Winni Neessen • • •Wolf480pl
in reply to daniel:// stenberg:// • • •:thonk:
in reply to daniel:// stenberg:// • • •@bagder
Stephen Paulger
in reply to daniel:// stenberg:// • • •if it’s a supported version of the dependency then the issue should be reported to the dependency. If it’s not supported then there’s nothing for you or the dependency’s developer to fix.
Your conditions are such that there should be very few people affected. So it seems to me entirely reasonable, maybe there are exceptions you would encounter but you still have the ability to decide to do something in those exceptional cases.
daniel:// stenberg://
in reply to Stephen Paulger • • •Stephen Paulger
in reply to daniel:// stenberg:// • • •truh
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to truh • • •abadidea
in reply to daniel:// stenberg:// • • •👾cosmicvisitors
in reply to daniel:// stenberg:// • • •Christen Lofland
in reply to daniel:// stenberg:// • • •So yes, making a CVE is a public good because it will call out poor practices more clearly and label them with a reason to stop that isn’t easy to ignore.
Joshua J. Drake
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
Unknown parent • • •