Skip to content
This repository has been archived by the owner on Nov 5, 2024. It is now read-only.

[Request] Notify Maintainers Of Vulnerable Packages #8

Closed
zero77 opened this issue Oct 28, 2020 · 3 comments
Closed

[Request] Notify Maintainers Of Vulnerable Packages #8

zero77 opened this issue Oct 28, 2020 · 3 comments

Comments

@zero77
Copy link

zero77 commented Oct 28, 2020

Package maintainers are often busy and may end up leaving support for old packages and not updating their package.

To improve security and hopefully save time for maintainers could an automated email alert be sent to maintainers with vulnerable packages notifying them that a package they maintain is vulnerable.

This may need addressing beforehand:
repology/repology-updater#1045

@AMDmi3
Copy link
Member

AMDmi3 commented Oct 28, 2020

I don't think I'm ever going to add email support to any of my projects, for it is an archaic, overcomplicated, insecure and unreliable service. In Repology, we also don't know maintainers for all packages, can't distinguish relevant and not relevant (e.g. groups, proxy maintainers) maintainers, and not all maintainers are in fact emails (there are fake IDs like username@aur or username@github).

There's much cleaner way which involves extending (already supported) atom feeds, and it's in fact the last item left unchecked in original issue regarding vulnerabilities support #15 - I somehow forgot that it still needs to be implemented.

I don't think #1045 is a show-stopper for this, as it's more related to resetting no longer relevant vulnerable states, while we're talking here about one-shot events which may be ignored if known to be not relevant.

@zero77
Copy link
Author

zero77 commented Oct 29, 2020

@AMDmi3 Thanks for your response.
I am not sure i follow, how would atom feeds notify maintainers that their package contains a vulnerability.
Unless we are able to confirm the maintainers monitor the feeds.

@AMDmi3
Copy link
Member

AMDmi3 commented Oct 29, 2020

Why would we need to confirm that?

@zero77 zero77 closed this as completed Sep 21, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants