unhinge@programming.dev to Linux@lemmy.mlEnglish · 9 months agoHow do you track security vulnerabilities?message-squaremessage-square34fedilinkarrow-up182arrow-down16file-text
arrow-up176arrow-down1message-squareHow do you track security vulnerabilities?unhinge@programming.dev to Linux@lemmy.mlEnglish · 9 months agomessage-square34fedilinkfile-text
Do you rely on mailing lists or news articles for security vulnerabilities? Please share. I only got to know about xz/liblzma [1] and curl [2] [3] vulnerabilities through lemmy (maybe because of high severity?). 1 ↩︎ 2 ↩︎ 3 ↩︎
minus-squareResponsabilidade@lemmy.eco.brlinkfedilinkPortuguêsarrow-up2·9 months agoI rely on Lemmy and in pacman -Syyu everyday
minus-squareunhinge@programming.devOPlinkfedilinkEnglisharrow-up1·edit-29 months agoThen, what does a package maintainer rely on? Edit: I’m so dumb. It’s obvious they’d check original developer’s repo or issue tracker. I’m sorry
minus-squareResponsabilidade@lemmy.eco.brlinkfedilinkarrow-up2·9 months agoI don’t know… I guess in mailing lists and pages like RSS feed from main enterprises like SuSE, Red Hat and Canonical
minus-squareⲇⲅⲇ@lemmy.mllinkfedilinkarrow-up1·9 months agoYou can track this kind of stuff on Mastodon also, join into a security instance (like https://infosec.exchange/explore) or start following them from another instance.
I rely on Lemmy and in
pacman -SyyueverydayThen, what does a package maintainer rely on?Edit: I’m so dumb. It’s obvious they’d check original developer’s repo or issue tracker. I’m sorry
I don’t know… I guess in mailing lists and pages like RSS feed from main enterprises like SuSE, Red Hat and Canonical
You can track this kind of stuff on Mastodon also, join into a security instance (like https://infosec.exchange/explore) or start following them from another instance.