openssh loads sshd?

Scott Webster sewebster at gmail.com
Wed Jul 21 13:31:31 PDT 2010


On Wed, Jul 21, 2010 at 7:20 AM, Daniel J. Luke <dluke at geeklair.net> wrote:
> On Jul 21, 2010, at 12:59 AM, Ryan Schmidt wrote:
>> This message is not unique to this port; all ports that have MacPorts-generated startupitems get this output displayed. Do you have a suggestion for how the message could be revised in such a way that would keep it applicable both to ports where the daemon is optional (as apparently in the case of openssh) and in cases where it is the sole purpose of the port?
>
> for the specific case of openssh, we could split the port and have an openssh-server port that just installs the launchd plist
>

That would probably work.  Another possibility is sending the user a
message during installation (ui_msg?) that tells them what is going on
(each maintainer would have to add a customized message to their port
if necessary).  And/or we could have the default installs (assuming
user performs instructed actions) leave the system in a secure state,
so perhaps with the ssh server installed but not running, or running
but with logins disabled etc.  Of course then we'd want to provide
instructions on how to configure and activate the service.

Anyway, there is a tradeoff between reducing work for the user (ie.
turn on what they likely want) and surprising some people with
unexpected situations (eg. me almost running an ssh server without
realizing it).

Scott


More information about the macports-users mailing list