I’m using PuTTY 0.70 on Windows 10 to connect to a remote VPS running Debian Linux, but I keep getting a “PuTTY Fatal Error: Couldn’t agree a client-to-server MAC (available hmac-sha2-512)” Other ssh client terminals are connecting just fine for me from the same machine, so this problem has to be a configuration within PuTTY.
First a quick overview of situation. Replaced three old 486 Windows machines with Mac Minis. Main use is connecting to our ERP system, taking orders from customers live over the phone. Trouble is, the java front end to ERP system is slower using Safari than it was in IE on a 486!!! (the mind boggles - actually, it doesn't, I blame Sun for bloating the java run-time). OK, remaining Win clients use Putty and it's lightning fast (ERP is running on RedHat server, putty logs in with SSH and only returns text to the Putty client).
I know OS X has a terminal, however, I've been trying for the last two years to get an Xterm on a Linux box to play ball and I still can't so I don't expect to make a Mac terminal step in line any quicker. I do, however, know how to make Putty work. So, I've installed X11, I've installed the software to build stuff (gcc, etc.) but Putty won't build (no GTK - or, more likely, libgtk).
I installed Darwin Ports but that can't find a GTK to install. Anyone built and running Putty? Oh, in case you don't know what I'm talking about. It does, according to the FAQ build as an application that will run under X11 on OS X. Thanks for any help you can give. Click to expand. I agree with the others.
YouTube as of now acknowledges video content in the various audio format as AVI, MP4, MOV, WMV, and WebM. How to convert youtube videos to mp3 on macbook pro. But one question that pokes in the mind is that YouTube does not support audio format WAV.
You definitely won't make anything go faster by trying to build putty on X11 under Linux or OS X. Make it work with the built in tools, or maybe something like (a reportedly faster VT100/xterm emulator than Terminal) could also help. Putty only really exists to make up for the fact that CMD.EXE and command line ssh and telnet are poor replacements for an xterm.
What are the hangups you have seen using Linux? Are there any 'special' settings you use in putty or is it just straight out ssh or telnet? Code: xmodmap -e 'keycode 88 = 0xFF5A' xrdb -merge. First a quick overview of situation. Replaced three old 486 Windows machines with Mac Minis.
Main use is connecting to our ERP system, taking orders from customers live over the phone. Trouble is, the java front end to ERP system is slower using Safari than it was in IE on a 486!!! (the mind boggles - actually, it doesn't, I blame Sun for bloating the java run-time).
Adobe photoshop cs6 mac. OK, remaining Win clients use Putty and it's lightning fast (ERP is running on RedHat server, putty logs in with SSH and only returns text to the Putty client). I know OS X has a terminal, however, I've been trying for the last two years to get an Xterm on a Linux box to play ball and I still can't so I don't expect to make a Mac terminal step in line any quicker. I do, however, know how to make Putty work. So, I've installed X11, I've installed the software to build stuff (gcc, etc.) but Putty won't build (no GTK - or, more likely, libgtk). I installed Darwin Ports but that can't find a GTK to install. Anyone built and running Putty? Oh, in case you don't know what I'm talking about.
![Putty Putty](https://i.pinimg.com/736x/df/18/c9/df18c95208f02b80fa1de15a13d8c2a1--wine-reviews-terminal.jpg)
It does, according to the FAQ build as an application that will run under X11 on OS X. Thanks for any help you can give. Click to expand.Odd. I had no idea that PuTTY worked on anything apart from Windows until this post. I guess that I never had the need for a dedicated ssh client on Unix/OS X with the ssh command line. Try using DarwinPorts to compile putty, it will resolve your dependancies automatically buy building and installing what you don't need. I had a look around for a PuTTY equivalent on Mac OS X, but couldn't find one.
Using the Terminal isn't for everyone, so I'm surprised that there is a hole in the market here. Click to expand.Thats a pretty snobbish attitude, and I know plenty of people who use ssh to access text based interfaces (not always a command line) who are not comfortable with bring up a Terminal window and typing 'ssh user@server' every time they want to log in. These are all on the Windows side of course, using either PuTTY or the official SSH client.