diafygi / diafygi/gethttpsforfree

Add some security headers, including CSP and HPKP

Open
#80 1 comment 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
JavaScript
Stars
2.2k
Forks
277
PR merge metrics
No merged PRs in 30d

Description

It would be nice to have some security headers: https://securityheaders.io/?q=https%3A%2F%2Fgethttpsforfree.com%2F

Especially a CSP could be very helpful here, as you can very strictly limit the JS use. However you may have to rewrite a few JS parts to be CPS-compatible (to not have to allow `insecure-eval`).
Also have a look at [report-uri](https://report-uri.io/) where you can collect CPS and HPKP violation reports.

As for HPKP [please be cautious with the LE client](https://community.letsencrypt.org/t/http-public-key-pinning-hpkp/2450). You might want to follow [this best practises](https://community.letsencrypt.org/t/hpkp-best-practices-if-you-choose-to-implement/4625).

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the securityheaders.io report linked in the issue, then review how this project serves its web responses and JavaScript. Define a CSP without insecure-eval where possible, assess the requested report-uri and HPKP settings against the linked guidance, and verify that the resulting headers and client behavior meet the security goals.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.