Friday, May 04, 2018

SSH Secure Shell Connections with MacWise and High Sierra

If you cannot connect to a host using secure shell (ssh) with MacWise, it could be a problem with High Sierra and cipher keys.
You may get a message similar to this when trying to connect to the host:

Unable to negotiate with xxx.xxx.xxx.xxx port 22: no matching cipher found. Their offer: aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,
aes192-cbc,aes256-cbc,rijndael-cbc

This is not a problem with MacWise. It is an issue with MacOS High Sierra 10.13
You can get around this problem by specifying a cipher in the Secure Shell Connection settings in MacWise.

Select Secure Shell Connection... from the Connection Menu in MacWise.
Then enter a cipher by using the -c option in the Additional Login Options field.
For instance, -c aes256-cbc
That option would use the  cipher, aes256-cbc

Currently, High Sierra supports these ciphers:
3des-cbc
aes128-cbc
aes192-cbc
aes256-cbc
rijndael-cbc@lysator.liu.se
aes128-ctr
aes192-ctr
aes256-ctr
aes128-gcm@openssh.com
aes256-gcm@openssh.com

chacha20-poly1305@openssh.com

You can verify this by opening the terminal app and entering
ssh -Q cipher

Your host may not support all of the ciphers that High Sierra supports.
So, when you connect to the host and it responds with "no matching cipher found", you can look at the list of ciphers that it offers and use one of those that high sierra also supports.



Friday, January 05, 2018

Crash when upgrading to High Sierra from older versions of MacWise

Upgrading to High Sierra with versions of MacWise prior to 16.2.3 could possibly cause abnormally large window sizes and a crash that corrupted the MacWise settings file.

It is unknown why this happens and it seems to be a problem on a low percentage of Macs.
Version 16.2.3 or later fixes this problem by detecting incorrect window sizes and sets them back to default sizes.

If possible, you should upgrade to MacWise 16.2.3 or later before installing Mac OS High Sierra or later to avoid the crash.

Wednesday, January 03, 2018

Function Keys and Arrow Keys with MacWise using Telnet and Kermit

MacOS High Sierra 10.13 removed telnet.
By default, MacWise version 16 now uses Kermit for telnet connections when it detects MacOS 10.13 or later.
It also enables two Kermit options by default:
"Use SLnet options for Kermit"  and "Echo Kermit Characters"

Not all host servers work properly with those two options.
If you are getting double characters on your screen, then uncheck "Echo Kermit Characters"

If your arrow keys and function keys do not work, then uncheck "Use SLnet options for Kermit"
Note that other factors can cause arrow keys and function keys not to work.

If you cannot log into your host, then put a checkmark on "Use SLnet options for Kermit"
You may see the following errors when opening a connection if it is unchecked:
Negotiations...
The Telnet server is not sending required responses
Telnet waiting for response to WILL KERMIT

Telnet waiting for response to DO KERMIT


Friday, September 29, 2017

MacWise 16.0.8 Compatible with Mac OS High Sierra and telnet

Apple, in their infinite wisdom, has removed Telnet from Mac OS High Sierra 10.13

If you have been using MacWise version 16.0.6 or earlier with telnet and upgrade to High Sierra, you will not be able to connect to your host because the telnet command is missing from High Sierra.

The solution is to install Kermit.
MacWise version 16.0.7 or later includes a Kermit Installer.
Version 16.0.8 has the Kermit Installer built into MacWise.

Run MacWise and select Kermit Installer from the Help Menu.

Put a checkmark on Kermit under the Connection Menu in MacWise

You will now be able to open a Telnet Connection with MacWise.

Saturday, January 28, 2017

MacWise Function Keys with Touch Bar on MacBook Pro

MacBook Pro with Touch Bar does not have real function keys.
Instead, it displays function keys in the Touch Bar.
By default, the function keys are not displayed in the Touch Bar when you run MacWise.

You can get around this problem in four ways:

1. Since function keys are displayed at the bottom of the MacWise window, you can click on them with the mouse.

2. If you hold down the Fn key, the function keys will appear temporarily on the Touch Bar if you have the following option set in your Keyboard Preferences...
(You must always press Fn in combination with a Touch Bar fkey)

Select System Preferences from the Apple Menu.

In System Preferences, choose Keyboard.
Then click the Keyboard tab.

Change "Press Fn key to" Show F1,F2,etc. Keys

3. You can use the Option key in combination with number keys for function keys.
For instance Option 1 is Fkey 1

4. (Requires MacWise version 15.4 or later).

Select "Activate Touch Bar on Startup" from the Connection Menu.
Then follow the instructions.

Note: "Activate Touch Bar on Startup" menu item will only be available on Touch Bar MacBooks.

Now, each time you run MacWise, the FKEYS will appear in the Touch Bar and you do not need to hold down the Fn key.



Saturday, October 03, 2015

MacWise and El Capitan

MacWise versions prior to 15.2 may have problems loading fonts with El Capitan (Mac OS 10.11)
You may get an error, " ActivateFontFromResourcesFile error -985 "
If you get that error, the MacWise font may not have loaded and can cause cursor positioning and screen clearing problems.


MacWise version 15.2 and later now attempts to load fonts from it's resources folder. If that fails, it looks for fonts in the MacWise Fonts folder.
The installer now has the option to drag MacWise Fonts to the Fonts folder (MacWise will alert you if that needs to be done)

If you are running MacWise version 14 or older, there is a $59.00 upgrade charge for version 15.
The order form is here...

The latest version of MacWise is here...


Thursday, April 17, 2014

Mac Wireless Sleep / Wake Wireles Connection Problem and Fix

Since the release of Mavericks in October 2013, there has been a widespread problem with Macs that are unable to reconnect to a wireless network after waking from sleep. This is most prevelant on MacBooks because they are on battery power most of the time and are set to sleep after two minutes of inactivity by default. MacBooks are also mobile and can be used in many locations.
The problem is caused by an interaction with Bluetooth and specifically Bluetooth devices that use Advanced Audio Distribution Profile (A2DP) which is used to stream bluetooth audio from devices such as Bluetooth headsets and Bluetooth speakers.

For more information and a fix...