Skip to content

pyinfra seems to have trouble using openssh CA signed user certificates #1569

@martijnvanveelen

Description

@martijnvanveelen

Is your feature request related to a problem? Please describe

I've setup a user pyinfra for all hosts using certificate based access with on openssh CA.
Although I've informed pyinfra inventory of all the required field still I need to create entries for all hosts in ssh/config with the specific key and signed certificate files for the pyinfra user.

I;ll solve this by moving pyinfra from venv to container. However, when using venv in a sudoer account on the control client it creates a lot of administrative overhead in the ssh/config (double entries for normal user account and pyinfra user like myhost and myhost-pyinfra entries.

Describe the solution you'd like

Whatever works for ssh from CLI should work when running pyinfra.
So if this works 'ssh pyinfra@host' with openssh CA signed host/user certificates then pyinfra running in venv should just be able to work without any overhead required (or just adding the info in the inventory.py)

Metadata

Metadata

Assignees

Labels

connectorsConnector issues - builtin integrations with other tools.dependency issueIssues in dependencies that affect pyinfra.

Type

No fields configured for Bug.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions