"*DDoS-Guard*, a dodgy Russian firm that also hosts the official site
for the terrorist group*Hamas"*
https://krebsonsecurity.com/2021/01/hamas-may-be-threat-to-8chan-qanon-online/#more-53893
It must be put through their abuse form:
https://www.cloudflare.com/abuse/form
On 12/01/2021 1:21 pm, steve payne wrote:
All of them are being hosted through Cloudflare and I have tried
multiple times to bring this to their attention. It has been
unsuccessful and it is allowing this spam
All abuse complaints must be put through their abuse form:
https://www.ovh.com/world/abuse/
On 12/01/2021 1:21 pm, steve payne wrote:
OVH, but trying to contact them about this has been useless.
Does anyone else find it crazy that without Mr Guilmette, this would all
go un-noticed?
Why does RIPE not employ its own researchers doing what he is doing?
and more importantly, how much of this crap is occurring that even he
himself has not yet noticed?
On 21/12/2020 11:16 am, Ronald F.
Amongst the greatest mysteries of the shady underbelly of the internet:
how to pronounce "Guilmette"
--
Is it possible to move a motion to rename this working group from Anti
Abuse WG to "The promotion of abuse working group"?
Because this entire working group is a farce.
On 12/11/2020 11:31 pm, Angela Dall'Ara wrote:
Dear Jordi,
The WGCC task, as defined in Section 4 of the PDP, is it to
...@heanet.ie www.heanet.ie
Registered in Ireland, No. 275301. CRA No. 20036270
*From:* anti-abuse-wg on behalf of PP
*Sent:* Monday 5 October 2020 11:04
*To:* anti-abuse-wg@ripe.net
*Subject:* Re: [anti-abuse-wg] [policy
You don't know that it was "marginal" support, because no count was ever
conducted.
The Chair never asked for a "vote", and then when people didn't "vote"
(because they had never been asked to), they concluded (wrongly) that
there was no support for the proposal.
On 5/10/2020 8:51 pm,
I don't understand why it would exclude the use of forms to submit abuse
information.
When submitting by a form, it reaches the host nearly 100% of the time.
The same cannot be said for email based submissions.
On 20/07/2020 11:07 pm, Petrit Hasani wrote:
Dear colleagues,
Policy proposal
bases, especially the larger ones) and public WiFi Hotspots, which can
be used for abusive activities, too.
I don't know who "PP" is (probably the same person which posts under
the nickname "Petras Simeon" on Twitter and on various boards), but he
contacted us and ou
The complaint to RIPE mechanism should only be an escalation mechanism
when the ISP does not respond.
The cost of dealing with the investigation by RIPE should be passed on
to the irresponsibly resource holder who did not properly respond to the
abuse complaint.
On 7/07/2020 6:26 pm,
I see a lot of discussion, but no formal policy proposal.
On 25/06/2020 7:23 pm, Serge Droz via anti-abuse-wg wrote:
On 25.06.20 10:22, PP wrote:
Perhaps a code of conduct, with de-registration of resources if the
entity does not comply, and enforcement costs to be levied against the
annual
will make your service
better for the people that legitimately need it.
The VPN business is, not unlike the Domain business: A lot of greedy
people with big egos.
This is not a technical issue.
Best
Serge
On 25.06.20 09:26, PP wrote:
Firstly, reporting it to the LEO does not cause the resources
,
--
Shane
On 25/06/2020 08.03, PP wrote:
So who at RIPE is responsible for allocating this resource, and what
policy can be introduced to prevent the allocation of IP address
resources to irresponsible organizations like this one?
SpamHaus have it listed as the worlds number one source
that his service is not contributing
towards free speech but hinders it.
Tonu
CERT-EE
On 25.06.2020 04:15, PP wrote:
Botnet controllers on VPN provider that refuses to act:
organisation: ORG-SL751-RIPE
org-name: Freedom Of Speech VPN
org-type: OTHER
address
:Re: botnet controllers
Date: Wed, 24 Jun 2020 21:49:21 +0200
From: i...@ghlc.biz
To: PP
On 2020-06-24 13:03, PP wrote:
Hello!
Please note that all mentioned IPs belong to non-logging VPN services.
No user logs are kept.
Sincerely yours
David Craig
SBL488704
185.140.53.75/32
16 matches
Mail list logo
