Broken SSH client on Mavericks

I am unaware of any problem with ssh in Mavericks. If all of your co-workers are having the same problem, I suspect you are all doing the same thing wrong.

Create a new user accunt on your machine. Take whatever procedures you used to setup your current account, and don't do them. Create an ssh key using default options. Try again. Copy the working settings and permissions from this account to your other accounts.

I added this to the Maverick machine and all works like a chrame

sudo vi /etc/ssh_config

# i

TCPKeepAlive yes

ServerAliveInterval 5

# ZZ

i see. i still have the problem myself.

Maverick is the worst version i every used.

If you are unwilling to do even the most basic troubleshooting like creating a new account or using -v then you are going to have a very difficult time. I don't know what is going on with your system, but installing an update on top of it is the last thing you want to do. This story gets repeated with each and every update. People's systems are misconfigured and they refuse to accep tthat possibility. Then, as each update comes and goes they get ever more angry that their problem isn't fixed.

SSH is not the same as Tylenol. If one "-v' doesn't help, try two, or even three.

impossibleplanet wrote:

(still hoping for a response sans snark)

Now that's going to be difficult, especially when I ask for debug ssh output and you only give me part of it.

Luckily, what you have given me is sufficient. You are authenticating correctly but your server is flaking out just at the last minute. This is a common problem among the many Linux versions out there. It has nothing to do with Mavericks because it existed for many years prior.

I don't know what the actual problem or definitive fix is. If you Google "debug2: channel 0: open confirm rwindow 0 rmax 32768" (with the quotes) you will find any Linux-specific threads on the problem. It could be a reverse DNS problem. It could be a driver problem. It could be a permissions problem. It could be dead sshd processes. It could be that you need to update openssh on the server. The only thing I know for sure is that this is a problem that has existed since 2005 at least. I even found a very similar thread here on ASC where I suggested a very similar Google search 3 years ago. That problem was fixed with a permissions repair and turning off LDAPv3.

impossibleplanet wrote:

The problem with a server side solution is that it's not just our internal servers that are doing it. I can't interact with external git repositories, either. If this really were a server problem, then not only would everyone else be having the problem, but every SSH server in the world would have to patch their servers, right?

But if it were a Mavericks problem then everyone in the world running Mavericks would have the same issue, right? That is the fundamental difference between OS X and Linux. All Mavericks machines, unless the user messes with them, are identical. Each and every Linux machine is a unique operating system, unlike any other. I don't mean SUSE is different than Ubuntu. I mean two identical-looking Ubutu machines sitting next to each other can, and probably will, be different. Having a LInux server be misconfigured is the rule rather than the exception.

Also, I appreciate your help, please don't assume that everyone on the planet knows ssh -v -v -v is the proper debugging method for this particular problem.

When the topic is using ssh to login into Linux servers, you bet I make that assumption.

I bet, by your 22,745 points, that been doing this for a long time, but it's almost never as obvious to everyone as you think it is and most people are unlikely to have same level of google-fu as you or the time to read through 10,000 possible results. (See BobHarris' respectful and level-headed response in the thread you just posted. Compare that to the accusatory tone you took in your very first response to this question). This is the sort of thing that scares off people who are not tech-savvy and I hate it more than anything. I've been in tech support and even if people acted like lazy idiots, I still treated them with respect.

You have an interested perspective on respect. I am not the one who used the term "idiot" or engaged in any personal attacks. You are welcome to wait for Bob to come along to this thread if you so desire.

I respectually suggest that if you want to get your problem fixed, you should talk to your own IT staff. They have access to the server config files and to the log files. Networking is a complicated endeavour. Just because something works doesn't mean it is configured correctly. One of the telltale indicators that it is improperly configured is a mysterious failure after a client-side update. You will not be able to resolve your issue by looking at only one side of the equation.

I am very concerned at the tone that etresoft is taking on this whole issue. Here is the comment from etresoft;

"If you are unwilling to do even the most basic troubleshooting like creating a new account or using - v gthen you are going to have a very difficult time. I dont know what is going on with your system but installing an update on top of it is the last thing you want to do. This story gets repeated with each and every update. People's systems are misconfigured anbd they refuse to accept that possibility. then, as each update comes and goes they get ever more angry that their problem isn't fixed."

I found this response very alarming. First of all the comment that "installing an update on top of it is the last thing you want to do." Hmmm. Aren't updates supposed to work on top of previous updates from Apple? Since when has it been necessary to completely redo the whole system or, as I have seen in many threads on this problem, simply wipe the hard drive clean and start all over? Apple needs to fix the update entirely, and be willing to pay users for the problems they are encountering, which are many. I have made this recommendation before and will repeat it until Apple is willing to acknowledge their error and back up the Apple name with real service.

I have seen that etresoft has said that users can request an refund if they choose. So this needs to be acknowledged PUBLICLY not just in this forum that Apple needs to be willing to back up their product with refunds for serious errors on Apple's part.

note; I have seen many many comments on these problems when one just googles mavericks. So Apple is already notified of world wide problems on Mavericks. Apple must be willing to acknowledge the error with Mavericks updates and make full refunds without individual requests for refunds.

The tones of the rest of etresoft's responses on this whole issue make me very angry and I am not even affected...yet....since I am very wise and am not going to update to Mavericks. In fact, every time I am notifeid there is an update to my well running Lion system, I refuse the update, lest Apple sneak in a Mavericks "fix" I don't want. I have also recommended to many others who are wishing to buy Apple products that they refuse any products with Mavericks installed.

Last of all is the recommendation later that impossibleplanet contact their IT staff. Did I fail to miss something, but it sounds to me as if impossibleplant is the IT staff..or something very close to an IT staff member. I have read many many many threads on problems IT staffs are encountering with Mavericks, I find it disengenous to ask users with substantial IT knowledge to have to undergo difficult fixes to errors in Apple's programs.

Etresoft and Apple must accept the fact that Mavericks is a flawed update and that the fault does NOT lie with the poor respondents who are being treated as if they are "unwilling to do the most baic troubleshooting" necessary.

So on behalf of the many many respondents to etresoft's comments, I respectfully ask that etresoft acknowledge the update is flawed and use utmost care and COURTESY in helping those with problems.

But anyhow... the connection lost is delayed by this

/etc/ssh_config

TCPKeepAlive no

ServerAliveInterval 120

So i try now to increse and decrese the 120 value to get a positive result

but it takes hours

First_step wrote:

I found this response very alarming. First of all the comment that "installing an update on top of it is the last thing you want to do." Hmmm. Aren't updates supposed to work on top of previous updates from Apple?

Alarming? Oh come on! The original poster refered to waiting for 10.9.1 to fix the problem. That is always a bad idea and I said exactly why.

Apple needs to fix the update entirely, and be willing to pay users for the problems they are encountering, which are many.

Pay users because they are trying to ssh into misconfigured Linux servers? Yes! I'm going to be rich!

I have seen that etresoft has said that users can request an refund if they choose.

No, you seem to be following me around in the forums trying to pick a fight. The only reference to a refund request that I have made was in reference to an accidental Mac App Store download.

The tones of the rest of etresoft's responses on this whole issue make me very angry and I am not even affected...

I suggest not getting angry about things that don't affect you. Otherwise, you life will get very unhappy, very quickly.

Last of all is the recommendation later that impossibleplanet contact their IT staff. Did I fail to miss something, but it sounds to me as if impossibleplant is the IT staff..or something very close to an IT staff member. I have read many many many threads on problems IT staffs are encountering with Mavericks, I find it disengenous to ask users with substantial IT knowledge to have to undergo difficult fixes to errors in Apple's programs.

The original poster has made no claim about being part of the IT staff and, in fact, scolded me over my assumption about ssh debugging expertise.

I respectfully ask that etresoft acknowledge the update is flawed

Request denied.

and use utmost care and COURTESY in helping those with problems.

If you, or anyone else, has a problem with the tone of my responses, you are free to use the "report post" button to alert the hosts and ask them to remove or edit myposts. If you do not have the 150 points required to enable that button, you can start a new thread in Using Apple Support Communities and make sure to refer back to this thread so people know what you are referring to. The hosts monitor that forum on a regular basis.

However, I am not an employee of Apple and am I under no obligation to mimic Apple's emotion-free support style. I reserve to the right to act and respond like a normal human being should I feel the need to do so. Bummer.