For those selfhosting stuff that's publicy accessible, do you serve a security.txt?

15 days ago by nawan to c/selfhosted

slazer2au 37 points 15 days ago

No, because it invites beg bounties and slop reports.

path: 0 26109273, hotness: undefined, score: 37, children: 2
synestine 7 points 14 days ago

If you run any sort of public facing website, you'll likely get some of those eventually.

path: 0 26109273 26118699, hotness: undefined, score: 7, children: 1
Pomal 1 point 13 days ago

Inherently this. Keeping security/spam/admin@ open are generally benevolent behaviors for the internet. The more appropriate response is to start blocking domains and hosting providers from contacting those channels. If someone cares, they’ll reach out.

Microsoft properties on the other hand, can suck my whole asshole.

path: 0 26109273 26118699 26141984, hotness: undefined, score: 1, children: 0
oha 27 points 15 days ago

Yes, but I should probably also put one up on my other domains

path: 0 26108459, hotness: undefined, score: 27, children: 4
B0rax 11 points 15 days ago

Nice domain!

path: 0 26108459 26108601, hotness: undefined, score: 11, children: 2
officermike 19 points 15 days ago

American Psycho business card gif

path: 0 26108459 26108601 26108721, hotness: undefined, score: 19, children: 0
oha 2 points 14 days ago

thanks!

path: 0 26108459 26108601 26125706, hotness: undefined, score: 2, children: 0
Hal 4 points 14 days ago

I was gonna say you had it in the wrong place, but it looks like you also serve it in the /.well-known/ location as well.

path: 0 26108459 26117446, hotness: undefined, score: 4, children: 0
lambalicious 23 points 15 days ago

No, it's free real estate for scams, slop and the like.

path: 0 26109793, hotness: undefined, score: 23, children: 0
ahmedezat_katteb 9 points 14 days ago

I do, but with a few tweaks that cut most of the junk the other comments mention:

  • Point Contact: at a dedicated alias, not your main inbox, and filter it hard. If the noise gets bad you can drop the alias without touching anything else.
  • Add a Policy: line linking to a short page that says plainly there is no bug bounty and no payment for reports. Most beg-bounty mails are mass-sent with a payment ask, so this gives you something to point them at and lets you bin them without guilt.
  • Don't forget Expires:, it's actually required by RFC 9116 and a lot of hand-written files leave it out. Set a calendar reminder to bump it.
  • Serve it at /.well-known/security.txt; the root path is only a legacy fallback.

Whether it's worth it for a homelab is debatable, but if you host anything other people rely on (a Matrix/Lemmy instance, a shared Nextcloud), having one real contact path beats someone finding a hole and having nowhere to send it.

path: 0 26122649, hotness: undefined, score: 9, children: 0
xyro 8 points 15 days ago

Nope, maybe I should ! Thanks for the reminder !

path: 0 26108639, hotness: undefined, score: 8, children: 0
majster 8 points 15 days ago

Do people actually contact you with that?

path: 0 26110202, hotness: undefined, score: 8, children: 2
3abas 5 points 15 days ago

I have a security.txt with an email to report vulnerabilities and a public key to encrypt sensitive information. The only reports I ever got were on the contract us form, unencrypted.

path: 0 26110202 26111840, hotness: undefined, score: 5, children: 0
moldy_rice 4 points 14 days ago

Yep. Looots of phishing emails.

path: 0 26110202 26121559, hotness: undefined, score: 4, children: 0
motruck 4 points 15 days ago

Why so people ignore that too?

path: 0 26109558, hotness: undefined, score: 4, children: 0
lntl 3 points 15 days ago

Nope.

path: 0 26110806, hotness: undefined, score: 3, children: 0
selfhosted
selfhosted

@lemmy.world

login for more options
62975
6798
5747

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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

go to feed...