Add security.txt

[oehm-smith]

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ x ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• [ NA] My code follows the code style of this project. (No code changes made)
• [ x ] My change requires a change to the documentation.
• [ x ] I have updated the documentation accordingly.
• [ x ] I have read the CONTRIBUTING document.
• [ NA ] I have added tests to cover my changes.
• [ NA ] All new and existing tests passed. (No code changes made)

[coliff]

Thanks for the PR - It's an interesting addition. I hadn't previously heard of this. it doesn't appear to be very well known (pun not intended) yet.

If this PR were to be merged, the additions to the /dist/ would also need to be made in the /src/ dir - otherwise they'll get rewritten when a new build is made. Also I think additional info is needed on that page to let users know that they need to edit the security.txt file before being used - the file there is just a starter template.

[roblarsen]

I see a lot of 404s for this well-known location. I think this would be a good educational addition. I don't know if the file itself should be there or it should just be documented. But anything that solves a persistent 404 is good in my book.

[oehm-smith]

PR updated with feedback.

[coliff]

Thanks again for this PR @oehm-smith - we've decided to give this a mention in the 'extend' docs with a link to https://securitytxt.org/ for more details.
Will be part of the #2074 PR

[oehm-smith]

Cool no worries Christian.  Apologies for not getting back to it as always became a lower priority.

…

On 9/10/18 4:55 pm, Christian Oliff wrote: Thanks again for this PR @oehm-smith <https://github.com/oehm-smith> - we've decided to give this a mention in the 'extend' docs with a link to https://securitytxt.org/ for more details. Will be part of the #2074 <#2074> PR — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2026 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACcCsxJLGDcpopDkvK1QRzo22ieocn5Vks5ujDpegaJpZM4SFKTc>.