News for hackers. Stuff that matters.

A comment on Mitigating a DDoS on Mastodon. Parent comment

Re:Mitigating a DDoS on Mastodon by koroshitekure on Friday December 06, 2019 @07:27AM (#21721176)
oh, i found out where the leak was

it's right at the end of the article - the attacker was abusing the "create a preview card of any posted URL" feature - he'd post a link, wait for pleroma to go and grab the url to preview it, then narrow down which one was mine based on user agent

i added an upstream proxy and anonymised the user agent, so even if he were to do that, the most he'd find was my proxy box

[ Parent | on HN ]
Re:Mitigating a DDoS on Mastodon by chvanikoff on Friday December 06, 2019 @10:09AM (#21722396)
That might be what you are talking about, but just to confirm: Pleroma has an ability to proxy outbound requests via `pleroma.http` config out of the box
[ Parent | on HN ]
Re:Mitigating a DDoS on Mastodon by koroshitekure on Friday December 06, 2019 @10:15AM (#21722457)
yeah that's what I'm using

I also pull-requested a user agent anonymisation setting (pleroma.http.user_agent) to make this better

[ Parent | on HN ]
Re:Mitigating a DDoS on Mastodon by TrueDuality on Friday December 06, 2019 @12:10PM (#21723766)
Did you consider using Tor to make those kind of outbound requests? I've done that in that past for a similar situation to avoid leaking IPs, there is a latency overhead but it solved my issue pretty quickly. There were some sites that were blocking Tor exits but the vast majority were successful (enough that when the feature failed it didn't really matter).
[ Parent | on HN ]