Upgrading openssh overwrites user-modified config files

[vinc17@…]

The openssh port shouldn't overwrite user-modified config files (ssh_config and sshd_config), or should introduce some mechanism to do config file upgrades safely. For instance, contents between some markers could be preserved, e.g.

# BEGIN local configuration
...
# END local configuration

In such a case, such configuration should be near the beginning of the file. The ssh_config man page says:

     For each parameter, the first obtained value will be used.  The configu-
     ration files contain sections separated by ``Host'' specifications, and
     that section is only applied for hosts that match one of the patterns
     given in the specification.  The matched host name is the one given on
     the command line.

     Since the first obtained value for each parameter is used, more host-spe-
     cific declarations should be given near the beginning of the file, and
     general defaults at the end.

I don't know about sshd_config. I suppose that the same rule is applied.

[wsiegrist@…]

Un-assigning due to dropping maintainership.

[(none)]

Milestone Port Bugs deleted

[vinc17@…]

I think it should be assigned to the new maintainer...

The bug is still present in openssh @5.5p1 for both the config files in /etc/ssh and org.macports.OpenSSH.plist (which disables sshd).

[jon+mp@…]

This bug recently bit me too, and my /opt/local/etc/ssh_config changed were wiped.

[ttelford.groups@…]

This bug keeps biting me - every single time the OpenSSH configuration is updated.

[nonstop.server@…]

Cc Me!

[neverpanic (Clemens Lang)]

The openssh port in its current version preserves existing copies of $prefix/etc/ssh/ssh{,d}_config. I'm not sure why it should preserve modifications to the launchd plist, though.

I consider this fixed, please re-open if you think different (pun intended!).