Skip to content

Add .well-known/security.txt file #9048

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

Merged
merged 1 commit into from
Jul 17, 2024
Merged

Add .well-known/security.txt file #9048

merged 1 commit into from
Jul 17, 2024

Conversation

carols10cents
Copy link
Member

Follow-up work to #8791 now that the page is live!

@carols10cents carols10cents force-pushed the well-known-security branch 2 times, most recently from 5a2ea5e to c3090ce Compare July 9, 2024 17:49
@carols10cents
Copy link
Member Author

uhhhh the tests are failing because linking with cc failed because there's no space left..... does a cache somewhere need cleared?

@@ -0,0 +1,2 @@
Contact: https://crates.io/policies/security
Expires: 2025-06-25T00:00:00.000Z
Copy link
Contributor

Choose a reason for hiding this comment

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

We're 100% going to forget this, aren't we?

I wonder if we should have a scheduled GitHub action that monitors this and tells us if it's close. (I can write that after this gets merged.)

Copy link
Member

Choose a reason for hiding this comment

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

hmm, that's a good point. I guess alternatively the file is small enough that we could also generate it on startup and serve it from the axum server 🤔

Copy link
Member Author

Choose a reason for hiding this comment

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

well the point is that a person should look at it every once in a while.........

@LawnGnome
Copy link
Contributor

LawnGnome commented Jul 10, 2024

uhhhh the tests are failing because linking with cc failed because there's no space left..... does a cache somewhere need cleared?

(At least) #9030 also failed for the same reason. Weird.

I've opened #9050 and will see what I can figure out. (Decidedly not a CI or GitHub Actions expert over here.)

Copy link

codecov bot commented Jul 11, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.11%. Comparing base (d0093d0) to head (80ecab3).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #9048   +/-   ##
=======================================
  Coverage   89.11%   89.11%           
=======================================
  Files         280      280           
  Lines       28216    28217    +1     
=======================================
+ Hits        25145    25146    +1     
  Misses       3071     3071           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

And expires on crates.io's birthday, which everyone knows is June 25.

Generated using https://securitytxt.org/.
@Turbo87 Turbo87 force-pushed the well-known-security branch from 80ecab3 to 16d58ed Compare July 17, 2024 06:55
@Turbo87 Turbo87 changed the title Link to crates.io's security page from README.md and .well-known/security.txt Add .well-known/security.txt file Jul 17, 2024
@Turbo87 Turbo87 enabled auto-merge (squash) July 17, 2024 06:57
@Turbo87 Turbo87 merged commit 091acc4 into main Jul 17, 2024
9 checks passed
@Turbo87 Turbo87 deleted the well-known-security branch July 17, 2024 07:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

4 participants