What's new

Any need to generate new .crt, .key, .ovpn when moving from an old OpenVPN?

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

gbguy71

Occasional Visitor
Apologies if this has been covered, but I can't find the answer.

In 2015 I generated .crt, .key, and .ovpn files and am moving to a new router and the latest Merlin. I was using these same files successfully from a 2018 Merlin release. Is there any need to go through the generation process again?

I guess that the real question is "Once you generate these files how do you know if you ever need to generate them again to work with the latest OpenVPN?"

TIA
 
OpenVPN may be backward compatible, at least they didn't remove support for mainstream encryption ciphers, but I would recommend you to regenerate as you may be using outdated encryption ciphers.

On how to know if regeneration is required, you can check the configuration in your .ovpn file for features that were removed, such as outdated encryption ciphers.

If you don't want to regenerate the key and ca, you only need to edit the .ovpn to modify the outdated content, but you still need to re-import the modified .ovpn to the client.
 
Last edited:

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top