This cannot possibly be related to the SSH update. Unfortunately, screen artifacts sounds like it could be a failing GPU.I happened to download and install the latest SSH update after which my MBP started to show occasional screen artifacts with occasional reboot after. This is Console output -
It hasn’t happened with a previous version. Hope the log helps.Oct 8 08:11:43 localhost kernel[0]: KQueueScanContinuePatch: Pre-Patch: Bytes at kqueue_scan_continue panic location: 48 8d 3d bb f3 19 00 48 8d 35 11 f4 19 00 44 89 fa 30 c0 e8 bc b5 c5 ff 45 31 e4 49 8b b5 80 00 00 00 4c 89 f7 44 89 e2 Oct 8 08:11:43 localhost kernel[0]: KQueueScanContinuePatch: Post-Patch: Bytes at kqueue_scan_continue panic location: 41 bc 09 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 49 8b b5 80 00 00 00 4c 89 f7 44 89 e2 Oct 8 08:11:43 7cd1c3_apple ReportPanic[247]: ReportPanic could not stat /Library/Logs/DiagnosticReports/Kernel_2018-01-01-020028_MD1012.panic Oct 8 08:30:13 localhost kernel[0]: KQueueScanContinuePatch: Pre-Patch: Bytes at kqueue_scan_continue panic location: 48 8d 3d bb f3 19 00 48 8d 35 11 f4 19 00 44 89 fa 30 c0 e8 bc b5 c5 ff 45 31 e4 49 8b b5 80 00 00 00 4c 89 f7 44 89 e2 Oct 8 08:30:13 localhost kernel[0]: KQueueScanContinuePatch: Post-Patch: Bytes at kqueue_scan_continue panic location: 41 bc 09 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 49 8b b5 80 00 00 00 4c 89 f7 44 89 e2 Oct 8 08:30:24 localhost ReportPanic[288]: ReportPanic could not stat /Library/Logs/DiagnosticReports/Kernel_2018-01-01-020028_MD1012.panic Oct 8 08:30:24 localhost ReportPanic[291]: ReportPanic could not stat /Library/Logs/DiagnosticReports/Kernel_2018-01-01-020028_MD1012.panic
Unfortunately, there are no kernel panic logs saved. The only thing showing up is those kernel patch messages I posted earlier.cab you paste the panic log? Given that chromium causes kernel panic for instance, i wouldn't say it's impossible for it to somehow tickle something in the kernel leading to this issue, but it's probably unlikely given openssh doesn't use that many weird apis
So when your computer has finished starting back up, you don’t see a dialog that says "Your computer restarted because of a problem” with a "Report” button that opens a crash log?Unfortunately, there are no kernel panic logs saved. The only thing showing up is those kernel patch messages I posted earlier.
Darn, there must be something I need to fix. It does work for me to log into Sequoia.
Can you try with the -v flag so we can see exactly where it gets stuck? (ssh -v [...])
ssh -o PreferredAuthentications=password -o PubkeyAuthentication=no owner@192.168.xxx.xxx
~$ ssh -v -l owner 192.168.xxx.xxx
OpenSSH_9.9p2, LibreSSL 3.8.2
debug1: Reading configuration data /etc/ssh_config
debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve; disabling
debug1: Connecting to 192.168.xxx.xxx [192.168.xxx.xxx] port 22.
debug1: Connection established.
debug1: identity file /Users/owner/.ssh/id_rsa type -1
debug1: identity file /Users/owner/.ssh/id_rsa-cert type -1
debug1: identity file /Users/owner/.ssh/id_ecdsa type -1
debug1: identity file /Users/owner/.ssh/id_ecdsa-cert type -1
debug1: identity file /Users/owner/.ssh/id_ecdsa_sk type -1
debug1: identity file /Users/owner/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file /Users/owner/.ssh/id_ed25519 type -1
debug1: identity file /Users/owner/.ssh/id_ed25519-cert type -1
debug1: identity file /Users/owner/.ssh/id_ed25519_sk type -1
debug1: identity file /Users/owner/.ssh/id_ed25519_sk-cert type -1
debug1: identity file /Users/owner/.ssh/id_xmss type -1
debug1: identity file /Users/owner/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_9.9
debug1: Remote protocol version 2.0, remote software version OpenSSH_9.9
debug1: compat_banner: match: OpenSSH_9.9 pat OpenSSH* compat 0x04000000
debug1: Authenticating to 192.168.xxx.xxx:22 as 'owner'
debug1: load_hostkeys: fopen /Users/owner/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh_known_hosts2: No such file or directory
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: sntrup761x25519-sha512
debug1: kex: host key algorithm: ssh-ed25519
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: SSH2_MSG_KEX_ECDH_REPLY received
debug1: Server host key: ssh-ed25519 SHA256:5tg5gRtOUj8kJUfaorkIMbNS72NOmcc3HvKgZ+8YDIE
debug1: load_hostkeys: fopen /Users/owner/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh_known_hosts2: No such file or directory
debug1: Host '192.168.xxx.xxx' is known and matches the ED25519 host key.
debug1: Found key in /Users/owner/.ssh/known_hosts:1
debug1: ssh_packet_send2_wrapped: resetting send seqnr 3
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: Sending SSH2_MSG_EXT_INFO
debug1: expecting SSH2_MSG_NEWKEYS
debug1: ssh_packet_read_poll2: resetting read seqnr 3
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey in after 134217728 blocks
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_ext_info_client_parse: server-sig-algs=<ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ssh-ed25519@openssh.com,sk-ecdsa-sha2-nistp256@openssh.com,rsa-sha2-512,rsa-sha2-256>
debug1: kex_ext_info_check_ver: publickey-hostbound@openssh.com=<0>
debug1: kex_ext_info_check_ver: ping@openssh.com=<0>
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_ext_info_client_parse: server-sig-algs=<ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ssh-ed25519@openssh.com,sk-ecdsa-sha2-nistp256@openssh.com,rsa-sha2-512,rsa-sha2-256>
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: publickey
And, yes, your patch did also vector SSH to password security without me having to enter the extra SSH arguments to force it to do such. Thank you, sir!@imercado Can you please redownload and reinstall the SSH update and let me know if it works now? I think I fixed it.
Thanks for confirming, I originally missed one of the patches that Apple applies.And, yes, your patch did also vector SSH to password security without me having to enter the extra SSH arguments to force it to do such. Thank you, sir!
No, no "computer restarted because of a problem" thing.So when your computer has finished starting back up, you don’t see a dialog that says "Your computer restarted because of a problem” with a "Report” button that opens a crash log?
If upstream OpenSSH is working for you, by all means use that! However, I wanted to do it "as Apple would".I have compiled OpenSSH_10.2p1 a few days ago from source. Does the Version from Wowfunhappy have any advantages over that? What are the things that Apple compiles into their OpenSSH version? I did not notice anything, that does not work.
Yes I was concerned if there were issues, folks might expect assistance from you, wow - which is not my intention.. I did wonder if it may be best as a separate topic but still under the umbrella of Mavericks.^ A warning that NexPostFacto doesn't provide full OpenGL support, which can cause problems in various apps. Nothing on my website is tested under this environment and I don't know whether there will be issues.
If is your only option, I do understand, but it's not the way I would prefer for people to experience Mavericks.
Make sure you're opening the DMG in icon view, then let me know if it's still unclear!Wowfunhappy, thank you so much for all your great work with Mavericks, I love using my mac again.
I downloaded the snow leopard window controls, but don't understand how to install them, just see install and uninstall folders with readme warning vs hidpi screens. Any help would be appreciated.![]()