Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

security.txt #34

Open
travi opened this issue Jan 2, 2018 · 2 comments
Open

security.txt #34

travi opened this issue Jan 2, 2018 · 2 comments

Comments

@travi
Copy link
Member

travi commented Jan 2, 2018

No reason not to

@kjbrum
Copy link

kjbrum commented Oct 25, 2019

@travi I can get this taken care of, what information needs to be added?

@travi
Copy link
Member Author

travi commented Oct 26, 2019

so, i'm a little on the fence around how to handle this one with current timing. i'm a little cautious about putting an email in the file in clear text for spam reasons.

ideally, we'd point to our contact page, but we dont have one yet. (i could have sworn that i'd created an issue for that previously, but there is one now. My plan for adding the contact page has been to do so after transitioning to the new site so that it doesnt turn into a rabbit hole that delays the transition.

i'd love to include a public key as well, but i'm not sure what the right answer is there either. we do have a keybase team set up, but i'm not sure if that gives us the option of having a public key that we can distribute that enables the team to decrypt messages. if its available, i didnt find it in the brief looking ive done.

while getting this file in place will be straight forward, it might be a little early to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants