Disable root SSH authentication altogether #24
Labels
No labels
0 points
0.5 points
1 point
13 points
2 points
21 points
3 points
34 points
5 points
55 points
8 points
ambition
application-offering
ambition
configure-applications
ambition
front-end
ambition/install-applications
ambition
security
ambition
switch-host
ambition
update-applications
ambition
user-management
api service
blocked
component: fediversity panel
component: nixops4
documentation
estimation high: >3d
estimation low: <2h
estimation mid: <8h
infinite points
productisation
project-management
question
role: application developer
role: application operator
role: hosting provider
role: maintainer
security
technical debt
testing
type unclear
type: bug
type: deliverable
type: key result
type: objective
type: task
type: user story
user experience
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Blocks
Depends on
#291 code passes security check
fediversity/fediversity
#295 limit security impact of SSH access to service VMs
fediversity/fediversity
#100 migrating application data between hosting providers
fediversity/fediversity
#494 data model used
fediversity/fediversity
#599 diagnosing services
fediversity/fediversity
#883 infra includes hypervisor
fediversity/fediversity
Reference
fediversity/fediversity#24
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?
After discussion in the Matrix channel, and as mentioned in #20 (comment), we should get rid of root SSH authentication altogether.
this would then raise the question on how we might handle deployment in such a way as to better limit attack surface.
implementation notes.
ideas:
rootto using@wheelusers with password-less sudo. NixOps4 did not support this yet, so this may depend on it being subsumed (after #494).nitspull-based updatesappvm- unmaintainednixless-agent: on command node pulls update from cachereplace the node with a new one based on the new configuration (needs state transfer, see #100)- overkillkubernetes(#598) - overkillkiara referenced this issue2025-05-05 19:48:02 +02:00
incus exec, drop deployment SSH #1112now that #1112 landed, this seems used still mostly for (in either case mostly for non-incus deployment methods, as that also offers
incus exec):