Selfhosted

39931 readers

463 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Do any of you bother writing abuse emails? (lemmy.fmhy.ml)

submitted 1 year ago* (last edited 1 year ago) by Dirt@lemmy.fmhy.ml to c/selfhosted@lemmy.world

31 comments fedilink hide all child comments

I was logged into my Cloudflare account today attempting to setup Tunnels when I noticed various security events related to my domain. Upon further inspection I realized that they all originated from a Microsoft Owned IP address (I'm assuming somebody running a Azure VM instance).

Looking into the actual request headers I can see that whatever bot was running was looking for common PHP exploits or unsecured endpoints.

I usually ignore such instances as I have proper firewall rules both on the Cloudflare side as well as my local network side so I'm doubting there's actually any threat to my network. However, I decided today to email the abuse contact provided from the WHOIS details. Was wondering if anybody else had experience with writing these? Is it even worth writing them or do they just end up being a waste of time?

Edit: Thanks everybody for the responses! Seems that it's up in the air if I'll ever get a response back. Maybe that's okay - Looks like the general consensus is that these usually do end up getting taken seriously (at least by some providers). I guess I'll keep composing away even if it's just an exercise in good internet stewardship :)

you are viewing a single comment's thread
view the rest of the comments

[–] rs5th@lemmy.scottlabs.io 22 points 1 year ago* (last edited 1 year ago) (3 children)

I’ve actually done this for a Microsoft owned IP before. Someone was Wordpress-scanning a particularly fragile application of one of my clients (which was not Wordpress) which was causing it to fall over. The scan stopped within an hour of sending the abuse email.

Edit to add: I used to work in a NOC for a tier 1 ISP. We had an “abuse department” (a couple people) that investigated these and opened tickets with the NOC. I’ve emailed customers and disconnected circuits as a result of abuse emails, so I wouldn’t say they’re totally useless, but I’m sure it depends on the company involved.

[–] ptz@dubvee.org 3 points 1 year ago* (last edited 1 year ago) (1 children)

Wait, what? To their abuse@microsoft.com or whatever email (whatever's listed in whois)?

I've had Azure IPs absolutely hammering my VoIP server and absolutely none of the reports I sent were even acknowledged. Ended up just blocking the entire Azure CIDR range in the firewall.

AWS, OTOH, got back to me within about an hour and a resolution within 3.

[–] rs5th@lemmy.scottlabs.io 5 points 1 year ago

Yep! Just for whatever the abuse contact was in whois. Could have been coincidence, or maybe just whoever was on shift in Azure town at the time. I don’t remember if I got a response or not from MS.

load more comments (1 replies)