Skip to content

Conversation

@lool
Copy link
Contributor

@lool lool commented Nov 14, 2025

Review http vs https usage in the project and use https where it makes sense.

  • fix!(debos): Use https for APT by default
  • fix(ci): Bootstrap chroots with https
  • feat(Makefile): Also set https_proxy

This is particularly important in the context of compliance as http:// might be seen as insecure, or at least lacking confidentiality.

lool added 3 commits November 14, 2025 13:51
Using http:// for APT repositories by default made sense for Debian and
debos years ago for client performance, server load and caching
friendliness, but it compromised privacy and can be seen under a bad
light when looking at it from a cybersecurity standpoint.

Change the default Debian mirror (deb.debian.org) from http to https.

Signed-off-by: Loïc Minier <[email protected]>
Use https instead of http for the Debian mirror when creating build
chroots.

Signed-off-by: Loïc Minier <[email protected]>
This typically won't help for caching, but is symetric to http proxy
handling and can help with connectivity.

Signed-off-by: Loïc Minier <[email protected]>
@basak-qcom
Copy link
Contributor

I'm OK with shipping sources.list with https, but can we continue to use plain http for development and testing please? Otherwise caching becomes impossible.

@basak-qcom
Copy link
Contributor

(which is going to slow down development iterations massively)

@github-actions
Copy link

Test Results

 2 files  ±0   6 suites  ±0   6m 50s ⏱️ ±0s
20 tests ±0  20 ✅ ±0  0 💤 ±0  0 ❌ ±0 
64 runs  ±0  64 ✅ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 8b58150. ± Comparison against base commit 8c913de.

@github-actions
Copy link

Test jobs for commit 8b58150

@basak-qcom
Copy link
Contributor

I understand this will be more of a pain to implement whatever we do. The best I can think of is to parameterise whether we want http or https, perhaps default to https for safety, allow the developer to override for local builds, and maybe add some tests to ensure that there are no plain http:// in sources.list at the end.

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