Instead, the process that 3.4.0 introduces is that upgrading the client should only take place when a OpenVPN server administrator is available at a moments notice to address if/when OpenVPN Connect's upgrade process just breaks something. While the error log is well worded and make sense of what is needed for anyone familiar with working with OpenVPN logs that is not how this reads to a novice. Currently the upgrade process doesn't leave anything of the previous version and the download page does not provide any archive of the previous versions either. (2) As a second option, there should be an easy method to choose to fall-back to the previous version of the client. It could also offer to collect the email address of the OpenVPN server administrator to send a report/nastygram about what changes were needed. It should then offer to automatically perform the removal unsupported options at the click of a button. (1) A prompt explaining what the client needs to remove from the configuration file to proceed. There should have been two options given to users of OpenVPN Connect to maintain a high level of trust: ![]() The way this was handled may unintentionally increase novice user distrust for upgrading the client in the future.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |