Normally, when Apple upgrades files in /etc (/private/etc), they usually copy 
the current version into a file with a suffix of “orig” or “previous”, of 
something along those lines.  After you upgrade, you should check whether your 
original file has copied into a backup, and  merge the two (there might be some 
changes that Apple makes you might want to consider in your final version).

Jonathan

> On Jul 24, 2020, at 3:35 PM, Harry Goldschmitt via X11-users 
> <[email protected]> wrote:
> 
> I have made changes to sshd_config so that incoming X connections work. Of 
> course as documented on the net, they disappear every time I upgrade my OSx, 
> currently 10.15.6. Apple rewrites the /private/etc/ssh/sshd_config file.
> 
> I'm making 2 modifications to /private/etc/ssh/sshd_config:
> 
> X11Forwarding yes
> XAuthLocation /opt/X11/bin/xauth
> 
> From sshd 7.3p1, an Include statement is available in sshd_config, which can 
> point to a directory. The directory can be empty or authorized users can add 
> their own files to be included in sshd_config, overriding what's in the base. 
> My sshd is 8.x (depending on whether I use Apple's or homebrew's). I don't 
> believe there's a default directory.
> 
> I'm currently running a shell script at login to see if Apple has changed my 
> sshd_config, and issue an alert, if so.
> 
> Does anyone know if Apple is planning on supporting the Include statement 
> soon, or if there's another way around this?
> 
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> X11-users mailing list      ([email protected])
> Help/Unsubscribe/Update your Subscription: 
> https://lists.apple.com/mailman/options/x11-users/jprescott12%40icloud.com
> 
> This email sent to [email protected]

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription: 
https://lists.apple.com/mailman/options/x11-users/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to