This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/anti-abuse-wg@ripe.net/
[anti-abuse-wg] Adding a "Security Information" contact?
- Previous message (by thread): [anti-abuse-wg] Adding a "Security Information" contact?
- Next message (by thread): [anti-abuse-wg] General List Behaviour & "personal data in the RIPE Database"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Alessandro Vesely
vesely at tana.it
Mon Jun 20 18:04:07 CEST 2022
Hi, On Tue 07/Jun/2022 11:45:05 +0200 Max Grobecker wrote: > Our abuse mailbox is not overflowing with these, of course, but it makes > semi-automated handling a bit painful. For example, we would like to forward > these information to our customers, but we wont need to take further action > on this, because we refuse to break into the offices of our customers at > night and patch their software. sorry to bother, but I hardly got that. Are these IP-driven messages? Don't CERTs lookup the abuse address with RDAP or WHOIS? Why doesn't the abuse address point (in)directly to the relevant IP user? That is, what's wrong in automatically forwarding CERT's security notices? I cannot understand how doing so entailS obligations to reach the customer's premises at night. Best Ale --
- Previous message (by thread): [anti-abuse-wg] Adding a "Security Information" contact?
- Next message (by thread): [anti-abuse-wg] General List Behaviour & "personal data in the RIPE Database"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]