Skip to content

Feat/flatpak policy type - #164

Merged
eniac111 merged 3 commits into
masterfrom
feat/flatpak-policy-type
Sep 5, 2026
Merged

Feat/flatpak policy type#164
eniac111 merged 3 commits into
masterfrom
feat/flatpak-policy-type

Conversation

@eniac111

@eniac111 eniac111 commented Sep 5, 2026

Copy link
Copy Markdown
Member

Closes #57

…og (#57)

Add a Flatpak policy type that manages remotes and applications on agent
nodes, plus a server-indexed application catalog (Flathub built in) that
the policy editor searches.

Signed-off-by: Blagovest Petrov <blagovest@petrovs.info>
Signed-off-by: Blagovest Petrov <blagovest@petrovs.info>
Comment thread server/internal/flatpakcatalog/fetch.go Fixed
…forgery)

A
Catalog fetches took admin-supplied URLs (the .flatpakrepo probe and
create-from-URL) with only an https-scheme check and same-host redirect
allowlist, so a registered repository could point the server at loopback,
link-local metadata endpoints or internal networks.

- ValidateHTTPSURL applies a strict regexp to the raw URL before parsing:
  https only, plain host name or IPv4 literal, no credentials
- an address policy refuses loopback, unspecified, link-local, multicast
  and broadcast addresses, and private/CGNAT ranges unless
  BOR_FLATPAK_CATALOG_ALLOW_PRIVATE_NETWORKS=true (internal mirrors)
- the transport resolves names itself and dials only approved addresses
  (DNS pinning); TLS 1.2 minimum
- tests for URL validation, the IP policy and blocked targets

Signed-off-by: Blagovest Petrov <blagovest@petrovs.info>
@eniac111
eniac111 merged commit f0a6d95 into master Sep 5, 2026
30 checks passed
@eniac111
eniac111 deleted the feat/flatpak-policy-type branch September 5, 2026 12:06
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.

Support for Flatpak package management

2 participants