- #Xquartz m1 mac serial number
- #Xquartz m1 mac pro
- #Xquartz m1 mac password
#Xquartz m1 mac serial number
Same serial number but the lid's been completely replaced (missing a scratch), which is fine. Got it back from their Houston, TX repair facility this morning (round trip: about 88 hours). I sent this system in to Apple via the Genius Bar for a screen replacement (the delaminating problem recall) on Monday. Ends at the same "open confirm rwindow" spot with the same error. #Xquartz m1 mac password
Exact same behavior regardless if password or key. This is not a DNS timeout (i.e., fixed by UseDNS). In this case I'm going over wifi to a server that is on Ethernet on the same subnet. I know I was able to ssh to this server on Monday morning. Below is a session example from a server on my LAN. There is no VPN running on the mac (or the servers). If I sudo to root on the Macbook and try the same ssh, I get the same result. FileZilla using SFTP and the same credentials (and port) works just fine. Weird! I assume they're all using some common library underneath but.what? By that I mean I see the same behavior in macOS native Terminal, iTerm2, and RoyalTS. It does this regardless of application. Used the key on another system and it worked fine, as expected. Hung in the exact same spot with the exact same error. I did quite a lot of diagnosis, but just to completely eliminate the server side, I did this: (1) gen'd a new ssh key, (2) spun up a new Deb 9 VM at Digital Ocean with that key, (3) tried ssh with that key. ssh does this regardless of destination. 
All other network on the Mac is fine (Safari, Outlook, Screen Sharing, etc.). This is just straight up ssh from the command line - no X forwarding or anything. 
When I try to ssh anywhere, after entering my password, the ssh session hangs immediately after authentication.
#Xquartz m1 mac pro
I have a MacBook Pro running Mojave 10.14.1.
0 kommentar(er)
