Add setting to disallow insecure transports
- Dominant language
- Python
- Stars
- 140
- Forks
- 45
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
[See original issue on GitLab](https://gitlab.com/BuildStream/buildstream/-/issues/408)
In GitLab by [[Gitlab user @TheRealMichaelCatanzaro]](https://gitlab.com/TheRealMichaelCatanzaro) on May 28, 2018, 14:49
## Background
For GNOME, we should have a setting to disable all insecure transports. http://, ftp://, git:// etc. Basically, anything that is not https:// should fail. Ideally BuildStream would notice when beginning a build that an insecure URL has been added to the project and refuse to build anything, but it's fine as long as it fails at some point.
It should apply cross-junction, so e.g. if the freedesktop SDK adds an element that uses a http:// URI, that should fail rather than downloading anything via http://.
## Task description
[//]: # (Short summary of the action to be executed)
* [ ] Action 1
* [ ] Action 2
* [ ] Action 3
## Acceptance Criteria
Should be able to add a setting to project.refs to disable insecure transports
----
Contributor guide
Research direction
Start from the project.refs configuration and the code that validates or fetches project and junction sources. Trace where transport URLs are checked, including cross-junction sources. Done means a project setting can reject insecure transports such as http://, ftp://, and git:// before anything is downloaded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100