code passes security check #291
Labels
No labels
ambition
application-offering
ambition
configure-applications
ambition
front-end
ambition/install-applications
ambition
security
ambition
switch-host
ambition
update-applications
ambition
user-management
blocked
component
api-service
component
fediversity-panel
component
nixops4
documentation
points
0
points
0.5
points
1
points
13
points
2
points
21
points
3
points
34
points
5
points
55
points
8
points
infinite
productisation
project-management
question
role
application-developer
role
application-operator
role
hosting-provider
role
maintainer
security
technical debt
testing
type
bug
type
deliverable
type
key-result
type
objective
type
task
type
unclear
type
user-story
user experience
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
#228 [D2.3] brought into production [2027-11-01]
fediversity/fediversity
#24 Disable root SSH authentication altogether
fediversity/fediversity
#26 Set up a secret management scheme
fediversity/fediversity
#87 Replace snakeoil-key with proper secret
fediversity/fediversity
#127 Keeping applications' nix packages up-to-date
fediversity/fediversity
#155 Address CI friction between security and caching
fediversity/fediversity
#198 switch panel db from sqlite to postgresql
fediversity/fediversity
#272 support password-protected personal SSH keys for deploying services in development
fediversity/fediversity
#295 limit security impact of SSH access to service VMs
fediversity/fediversity
#313 back-end supports multiple users
fediversity/fediversity
#314 ephemeral state is automatically provisioned
fediversity/fediversity
#463 secrets may be handled securely w.r.t. use in PRs
fediversity/fediversity
#493 portable ephemeral state
fediversity/fediversity
#614 catch up on nixpkgs updates
fediversity/fediversity
#633 nodes can identify one another
fediversity/fediversity
#991 internal networks secured
fediversity/fediversity
#1090 remote code execution and external repo pins for service portability
fediversity/fediversity
#1178 prefix-based source allowlist mechanism defeated by forgejo's upward navigation
fediversity/fediversity
#1217 openbao secrets engine for application-specific credential refresh
fediversity/fediversity
#1916 panel: allow only known procedures in the authorization callback, and only from api/
fediversity/fediversity
#1918 panel: destroy the deployments of an account when the account is removed
fediversity/fediversity
#1917 panel: refuse
/ in user names, and match the owner of a deployment exactly
fediversity/fediversity
#1922 panel: remove the windmill access to the SSH key of the panel and tf-env
fediversity/fediversity
#1939 api: refuse to start without
AUTHZ_CALLBACK_URL outside of development
fediversity/fediversity
Reference
fediversity/fediversity#291
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
In order to verify Fediversity may be put into production, we should have our code pass an independent security compliance audit in adherence to the standards set out in the General Data Protection Regulation (GDPR).
To ensure this serves our goals, this check should cover code spanning at least the features laid out in:
Achieving this would involve at least:
c.f. https://codeberg.org/kiara/e2ed-hetzner/issues/10
securityto security auditsecurity auditto code passes security auditcode passes security auditto code passes security checkkiara referenced this issue2025-06-09 23:00:55 +02:00
/in user names, and match the owner of a deployment exactlyAUTHZ_CALLBACK_URLoutside of development