News for hackers. Stuff that matters.
Re:Security.txt by goatsi on Sunday March 14, 2021 @03:43PM (#26458250)
The last time this came up on HN it got quite a negative review from someone who had tried it on several sites: https://news.ycombinator.com/item?id=19152145

It apparently attracted automated scanners and the signal to noise ratio was atrocious.

Re:Security.txt by aasasd on Sunday March 14, 2021 @06:49PM (#26460272)
People here dislike HackerOne, but afaiu it solves this exact problem. It's the first line of ‘support’ for security reporters.

The fact that the industry currently needs this kind of solution is absurdly comedic. Basically, it would make actual sense to require people to pay ten bucks when posting a report—if they think the report is reasonable and that they would get paid for it.

Re:Security.txt by tptacek on Sunday March 14, 2021 @07:16PM (#26460506)
It’s a good platform, but it really doesn’t solve the time-sink problem, even if you pay for triage services. Triage can knock down well-known patterns of bogus stuff, but so can you; the real problem is the truly wacky stuff people come up with.
Re:Security.txt by fractionalhare on Sunday March 14, 2021 @10:25PM (#26461951)
I can see and read the JavaScript source code if I intercept the requests! Please pay me $100.
Re:Security.txt by marco_craveiro on Friday March 19, 2021 @06:40AM (#26511844)
Hi @fractionalhare, apologies for the spam but I am trying to read a post you made a few months ago on implementing Exp [1] but it seems the site is down. Is there a different source perhaps? Many thanks for your time.

[1] https://www.pseudorandom.com/implementing-exp

Re:Security.txt by selfhoster11 on Sunday March 14, 2021 @07:44PM (#26460745)
I'd never enter in a paid interaction without some sort of escrow that will make sure I'm not screwed over for the crime of being a good citizen. The victim could just keep the cost of the report without ever refunding. Innocent people will keep getting caught by this even long after the company acquires a reputation for never providing refunds.
Re:Security.txt by aasasd on Sunday March 14, 2021 @11:24PM (#26462307)
Since the escrow sees your report, it sounds like HackerOne.

HO will just create paid tiers where for a smallish subscription price, people actually take your reports seriously.

Re:Security.txt by 67868018 on Monday March 15, 2021 @11:36AM (#26467226)
Smart contracts on Ethereum blockchain... force them to set a date to pay you and go public. They can't back out.

Going to need a lot of work in the next few years to make something like this viable, but ETH could make it possible

Re:Security.txt by aasasd on Monday March 15, 2021 @05:41PM (#26469523)
Are you saying that Eth can somehow withhold info until a future time when it automatically becomes public? How would that work?
Re:Security.txt by 67868018 on Thursday March 18, 2021 @07:38AM (#26501617)
Ethereum has a Turing complete programming language inside
Re:Security.txt by aasasd on Saturday March 20, 2021 @11:47AM (#26523927)
Yeah so? Think about it. How do you make a blob of data unreadable by people on Thursday but readable on Friday? You can't do it without a trusted third-party.

If Eth has a solution for this, it would mean it basically solves trust in general, which is a persistent pain in all of infosec.

Re:Security.txt by Anunayj on Sunday March 14, 2021 @07:42PM (#26460728)
posting your email in a not easily parsable way can save you a lot of spam. (rot13 it, break up characters, etc). Atleast that should cut most of the spam. This might be not standard, but I do not really see why we would need security.txt to be parsable by robots.
Re:Security.txt by orionblastar on Sunday March 14, 2021 @10:26PM (#26461953)
I just use GNUPG and encrypt it.
Re:Security.txt by Anunayj on Monday March 15, 2021 @07:30AM (#26464657)
encrypt with my private key?
Re:Security.txt by mike_d on Sunday March 14, 2021 @07:11PM (#26460468)
security.txt is a flag that you may have a bug bounty program, and as a result are a potential source of revenue.

It is time arbitrage between big companies taking security seriously (willing to pay large bounties) and that amount being higher than a monthly or yearly wage in some internet-connected regions. If they throw enough nets into the sea all year, eventually one pays off and they end up living quite well.

Re:Security.txt by superkuh on Monday March 15, 2021 @12:53AM (#26462756)
What does it mean when I enabled this on my personal (for fun) websites years ago on a whim? I don't have a bug bounty program.
Re:Security.txt by __throwawy9 on Sunday March 14, 2021 @07:18PM (#26460523)
Putting all of these files at root is going to be like have old rusty cars and stained mattresses in front of your house years from now.

The web is not a junkyard.

Re:Security.txt by dmurray on Sunday March 14, 2021 @08:33PM (#26461175)
The proposal is to place the file at /.well-known/security.txt.

And even if it wasn't, there is plenty of namespace room to put every file someone argues for in a 2-page RFC at root. After all, there are only 1024 low-numbered TCP ports and we haven't run out of those yet.

Re:Security.txt by __throwawy9 on Sunday March 14, 2021 @09:57PM (#26461777)
Don’t get me wrong; I dig file-based interfaces, but each time they add another file, it’s another request.

And it’s Anglocentric to continue to unnecessarily put multiple English words into the path; those can’t be touched-up with a later RFC to support Japanese in the file content via a Lang attribute.

The whole thing is shit bad, I’m sorry. Just come up with something that makes fucking sense for once.

Re:Security.txt by GoblinSlayer on Monday March 15, 2021 @03:39AM (#26463418)
Trap them with a honeypot: disable HSTS and automatically delete all messages containing "HSTS" string.
Re:Security.txt by 177tcca on Monday March 15, 2021 @11:34PM (#26472672)
Does this work?
Re:Security.txt by kjrose on Sunday March 14, 2021 @06:26PM (#26460018)
This would be my concern. It seems like a really good tool to attract the attention of bad actors.
Re:Security.txt by peterthehacker on Monday March 15, 2021 @03:16AM (#26463310)
The Contact field can point to a landing page.

> A link or e-mail address for people to contact you about security issues. Remember to include "https://" for URLs, and "mailto:" for e-mails

Using a landing page should improve the signal/noise ratio. Google, for example, points to a landing page [0] and GitHub points to their HackerOne profile.

[0]https://g.co/vulnz

[1]https://hackerone.com/github