IMPORTANT UPDATE!
Uncategorized
4
Posts
4
Posters
0
Views
-
IMPORTANT UPDATE!
“The detection order will not be part of the EU presidency’s new compromise proposal. It will remain voluntary for tech giants to search for child sexual abuse material.”
Danish Minister of Justice, Peter Hummelgaard, confirms today that Denmark is backing down and dropping mandatory scanning.
Thank you all for raising your voices!
-
IMPORTANT UPDATE!
“The detection order will not be part of the EU presidency’s new compromise proposal. It will remain voluntary for tech giants to search for child sexual abuse material.”
Danish Minister of Justice, Peter Hummelgaard, confirms today that Denmark is backing down and dropping mandatory scanning.
Thank you all for raising your voices!
@chatcontrol Thank god , we can finally be at rest knowing our privacy won't be compromised. At least for now.
-
IMPORTANT UPDATE!
“The detection order will not be part of the EU presidency’s new compromise proposal. It will remain voluntary for tech giants to search for child sexual abuse material.”
Danish Minister of Justice, Peter Hummelgaard, confirms today that Denmark is backing down and dropping mandatory scanning.
Thank you all for raising your voices!
@chatcontrol till next time...
-
IMPORTANT UPDATE!
“The detection order will not be part of the EU presidency’s new compromise proposal. It will remain voluntary for tech giants to search for child sexual abuse material.”
Danish Minister of Justice, Peter Hummelgaard, confirms today that Denmark is backing down and dropping mandatory scanning.
Thank you all for raising your voices!
@chatcontrol Phew, glad that they backed down. Sure, it may pop up again and big corpos can scan stuff. But I'm really glad that mandatory scanning won't be enforced.
I say that, for now, let's celebrate!
Feed RSS
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@sio MEGLIO UN FUMETTO O UN ETTO DI FUMO?
-
"eh, ma è lì che stanno TUTTI!"
dicono quelli che pensano le persone dovrebbero usare il loro software open source, invece che quello commerciale che già usano TUTTI... 😅
-
@ansuz that's very useful information, thanks.
-
@oblomov my approach involves a nodejs service and applies a chain of fairly complicated rules to categorize each one.
Depending on how different requests are classified it then writes offending IPs to a different log which fail2ban follows. I don't think I could accomplish the same with fail2ban alone, or at least if I could it would be much less readable.
Still, the write-to-a-log-to-ban is a nice API and I appreciate that fail2ban handles the rest of the details with so little attention.
-
@Uilebheist OK maybe I exaggerated for this 8-D
-
@oblomov RIght, if one assume it's 146.174.128.0/17 and 202.76.128.0/17 - they are both Huawei cloud.
Which I note I was already banning and I wonder why.
-
@Uilebheist no idea. For the time being I've manually banned 146.174.0.0/16 202.76.0.0/16 and things are smoother.
-
I've given the fail2ban conf doc a quick read, but this doesn't seem to be easy to detect, and it would be of limited use probably, unless the detection is done at a wider subnet level.
