Add support for alternative location of the public key (not $HOME/.ssh/authorized_keys)

Bug #1983437 reported by Jose Guedez
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
charm-local-users
Fix Released
Wishlist
Mert Kirpici

Bug Description

When using sshd configurations that are not the default (for example, when using userdir-ldap [0]), the intended public key location might be different from the standard $HOME/.ssh/authorized_keys.

In those cases the charm configures the users as usual, but remote sessions don't work because of the missing file with the public keys. It would be useful to be able to configure the location of the file, for example: /etc/ssh/user-authorized-keys/$USER, while keeping the default behaviour if no special configuration is provided.

[0] https://charmhub.io/userdir-ldap

Tags: bseng-340

Related branches

Andrea Ieri (aieri)
tags: added: bseng-340
Changed in charm-local-users:
assignee: nobody → Mert Kirpici (mertkirpici)
status: New → In Progress
Changed in charm-local-users:
milestone: none → 22.10
status: In Progress → Fix Committed
Revision history for this message
Mert Kirpici (mertkirpici) wrote :

This feature is included in rev15 of the local-users charm. It is in the candidate channel.

Changed in charm-local-users:
importance: Undecided → Wishlist
Changed in charm-local-users:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.