OUTPOSTPM Update for Winlink
Posted: Wed Dec 30, 2015 3:08 pm
Howdy gang - Hope this finds all of you well and wishing you and yours a Happy New Year.
Below is an update from the author of OUTPOSTPM which is an excellent packet program that I have installed and use at the State of Montana DES, Lewis & Clark EOC/Alternate EOC, St. Peter's Hospital, and at my home station.
Cheers Bill K7MT
Hello Outpost Users,
I hope you all had a good Christmas and holiday, and got a chance to enjoy some time off! I wanted to give you all a heads-up on the next Outpost change coming within a few weeks.
WHAT’S NEXT… RELEASE v3.1
Outpost v3.1 will address the change planned by the Winlink Team to support Secure Logon. This Outpost release is a very focused release with very few changes planned. See the details in the v3.1 Release Content Description document for details. Essentially, the 2 big changes are:
1. #1099: Implement BBS User Access Control. This change removes the telnet logon and passwords currently stored as part of the TNC/Telnet setting and directly associates them with a Call Sign or Tactical Call. This change will also provide Winlink users with the place to store your Winlink Secure Logon Password.
2. #1278: Manage the Winlink Secure Logon interaction. This changes detects and handles all responses to the Winlink Secure Logon challenge (whether by Telnet of CMS/RF access) and sends back the correct response based on your password.
There are 3 additional minor changes that further cleans up some of the telnet password handling. See the Release Content Doc for details.
RELEASE PLAN
The last message from the Winlink Team states they plan to make Secure Logon mandatory as of 15 April 2016. The Outpost 3.1 release is now in final testing and I hope to have it out to you by the 15 January 2016. This should give everyone plenty of time to do any telnet password migration well before the 15-April deadline. I will include instructions on how to do the migration as part of the release.
That’s it! In the meantime, I wish you and your family a very Happy and Healthy New Year!
Best regards,
Jim KN6PE
Below is an update from the author of OUTPOSTPM which is an excellent packet program that I have installed and use at the State of Montana DES, Lewis & Clark EOC/Alternate EOC, St. Peter's Hospital, and at my home station.
Cheers Bill K7MT
Hello Outpost Users,
I hope you all had a good Christmas and holiday, and got a chance to enjoy some time off! I wanted to give you all a heads-up on the next Outpost change coming within a few weeks.
WHAT’S NEXT… RELEASE v3.1
Outpost v3.1 will address the change planned by the Winlink Team to support Secure Logon. This Outpost release is a very focused release with very few changes planned. See the details in the v3.1 Release Content Description document for details. Essentially, the 2 big changes are:
1. #1099: Implement BBS User Access Control. This change removes the telnet logon and passwords currently stored as part of the TNC/Telnet setting and directly associates them with a Call Sign or Tactical Call. This change will also provide Winlink users with the place to store your Winlink Secure Logon Password.
2. #1278: Manage the Winlink Secure Logon interaction. This changes detects and handles all responses to the Winlink Secure Logon challenge (whether by Telnet of CMS/RF access) and sends back the correct response based on your password.
There are 3 additional minor changes that further cleans up some of the telnet password handling. See the Release Content Doc for details.
RELEASE PLAN
The last message from the Winlink Team states they plan to make Secure Logon mandatory as of 15 April 2016. The Outpost 3.1 release is now in final testing and I hope to have it out to you by the 15 January 2016. This should give everyone plenty of time to do any telnet password migration well before the 15-April deadline. I will include instructions on how to do the migration as part of the release.
That’s it! In the meantime, I wish you and your family a very Happy and Healthy New Year!
Best regards,
Jim KN6PE