On Mon, October 15, 2018 12:51 pm, Frank T Brady wrote:
Well, Rick - that sounds like a very user-unfriendly policy for ARRL toSo you mean that you'd prefer that the ARRL should leave a security
vulnerability open for more than a DECADE after the patch has been put out
there? Maybe you vendor should have updated your software in that time?
(Framework 3.5 sp1 came out in August 2008)