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

Requirement (Gold level): Secured delivery against man-in-the-middle (MITM) attacks #1190

Open
UlisesGascon opened this issue Jan 4, 2024 · 5 comments

Comments

@UlisesGascon
Copy link
Member

We agreed on #1175 to open an issue to follow up a discussion about this requirement for Node.js (cc: @mhdawson @ljharb @RafaelGSS)

The project website, repository (if accessible via the web), and download site (if separate) MUST include key hardening headers with nonpermissive values. (URL required)

Context

Potential actions

TBD

@ljharb
Copy link
Member

ljharb commented Jan 6, 2024

I assume if the website has CORS and HSTS set up, this will be satisfied.

Copy link
Contributor

github-actions bot commented Apr 6, 2024

This issue is stale because it has been open many days with no activity. It will be closed soon unless the stale label is removed or a comment is made.

Copy link
Contributor

github-actions bot commented Jul 6, 2024

This issue has been inactive for 90 days. It will be closed in 14 days unless there is further activity or the stale label is taken off.

Copy link
Contributor

github-actions bot commented Oct 5, 2024

This issue has been inactive for 90 days. It will be closed in 14 days unless there is further activity or the stale label is taken off.

@github-actions github-actions bot added the stale label Oct 5, 2024
@ljharb
Copy link
Member

ljharb commented Oct 5, 2024

all the issues in this repo are probably never stale

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