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

.well-known: update security.txt #9

Merged
merged 1 commit into from
Mar 19, 2021
Merged

.well-known: update security.txt #9

merged 1 commit into from
Mar 19, 2021

Conversation

herbetom
Copy link
Member

@herbetom herbetom commented Mar 17, 2021

sur5r
sur5r previously approved these changes Mar 17, 2021
Copy link
Member

@sur5r sur5r left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

Can we add an Encryption field in the future?

@herbetom
Copy link
Member Author

Yes, hoewer it needs to be discussed if we want to link to personal keys (i added [email protected] and created #8 to publish the coresponding public key) or how we would like to handle that.

@herbetom
Copy link
Member Author

securitytxt/security-txt#206 would be nice

@herbetom herbetom force-pushed the update_securitytxt branch 4 times, most recently from de68893 to 03acbfb Compare March 18, 2021 01:54
@herbetom herbetom force-pushed the update_securitytxt branch from 03acbfb to 2fd9ddf Compare March 18, 2021 01:57
@herbetom herbetom requested a review from sur5r March 18, 2021 18:26
@herbetom herbetom merged commit 86c01f9 into main Mar 19, 2021
@herbetom herbetom deleted the update_securitytxt branch March 19, 2021 21:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants