Bug 1172549 - openssh: add socket file too?
Summary: openssh: add socket file too?
Status: IN_PROGRESS
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Hans Petter Jansson
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-05 08:08 UTC by Ludwig Nussel
Modified: 2022-01-11 08:47 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ludwig Nussel 2020-06-05 08:08:38 UTC 
How about adding a socket activation unit in addition to the service file for ssh?
Wondering about that in the context of MicroOS. On slow ARM devices, openssh seems to need a noticable amount of cpu to launch at boot and may not be needed hanging around most of the time anyways. The device's purpose mostly would be reading sensors or such, it typically won't serve user logins. So having sshd launched on demand via socket seems to be more resource friendly there.
Comment 1 Ludwig Nussel 2020-06-08 15:57:41 UTC 
Fedora has a solution for that. Socket or service can be used there:
https://src.fedoraproject.org/rpms/openssh/tree/master

Also their approach to calling keygen looks smart.
Comment 2 Hans Petter Jansson 2022-01-10 21:46:48 UTC 
Thanks for suggesting it. Do you know if we need to patch any code for this? I'm guessing no?
Comment 3 Ludwig Nussel 2022-01-11 08:47:53 UTC 
I'm not into openssh but from a brief look at the Fedora patches it seems like no special one required.