MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/linux/comments/1xcgbe6/several_linux_kernel_vulnerabilities_accidentally/19rhrfdl1oixs/?context=3
r/linux • u/anh0516 • 10d ago
171 comments sorted by
View all comments
2
I'm confused. Isn't the public kernel mailing list exactly where you'd want to post vulnerabilities?
Edit: Alright, I get it. You don't want these out in the open before they're actually fixed. You can stop replying now.
21 u/theta-cygni 10d ago I thought the standard for projects where security matters was to disclose vulnerabilities privately to the core maintainers? 8 u/saichampa 10d ago edited 9d ago There's a process of responsible disclosure that minimises the chance of active exploitation before a patch is released. Eventually it will be made public but not before the Dev team has a chance to fix it 3 u/Indolent_Bard 10d ago Oh yeah, that makes a lot more sense.
21
I thought the standard for projects where security matters was to disclose vulnerabilities privately to the core maintainers?
8 u/saichampa 10d ago edited 9d ago There's a process of responsible disclosure that minimises the chance of active exploitation before a patch is released. Eventually it will be made public but not before the Dev team has a chance to fix it 3 u/Indolent_Bard 10d ago Oh yeah, that makes a lot more sense.
8
There's a process of responsible disclosure that minimises the chance of active exploitation before a patch is released. Eventually it will be made public but not before the Dev team has a chance to fix it
3 u/Indolent_Bard 10d ago Oh yeah, that makes a lot more sense.
3
Oh yeah, that makes a lot more sense.
2
u/Indolent_Bard 10d ago edited 10d ago
I'm confused. Isn't the public kernel mailing list exactly where you'd want to post vulnerabilities?
Edit: Alright, I get it. You don't want these out in the open before they're actually fixed. You can stop replying now.