-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi,
------- Original Message ------- On Friday, March 3rd, 2023 at 17:31, Bo Berglund <bo.bergl...@gmail.com> wrote: <snip> > > > > The simple answer is, try it! > > > > > > Hmm, nothing seems to have happened: > > > --------------------------- > > > $ ./easyrsa upgrade pki > > > > > > Notice > > > ------ > > > Your PKI is fully up to date. > > > ---------------------------- > > > This is due to a v3 'vars' file existing prior to running the upgrade. > > To remedy this, simply rename 'vars' to 'vars.backup', for example. > > > Well, I did not copy my old vars file to the new EasyRSA-3.1.2 dir, instead I > edited > The existing vars.example file in order to increase the expire time from 10 > to 20 years > and saved it as vars. > > So the vars file is a version 3 vars file as a copy of the vars.example plus > some edits. > > Is that not what one should do? > The upgrade code assumes that you have a v2 ./keys and associated files. It assumes the upgrade is completed if it finds a v3 vars file. If you introduce a v3 vars file prior to running the upgrade then the upgrade will not run. This is all good test data, thanks, R -----BEGIN PGP SIGNATURE----- Version: ProtonMail wsBzBAEBCAAnBQJkAjQ4CRBPl5z2a5C4nRYhBAm8PURno41yecVVVU+XnPZr kLidAAB6ewf+KmUFj1l7LSpZdkVvcyDEFW82HgOQYS6+DqTzisbY9kxcDvgZ j0/FVpfR6VIhsm82cNCis724ItPV2ZZq1ZoLK+yFiZ6ftZvebkFQ4UquM7FB XiliQilBX6Doj4KoEElNZ/fjfD0LWYW+BL4cVaqvhXmvs+ORnWMB5nCUbiA2 JXmtQzqBWf+FtSrH5tDvYSH19/vCh11Ue8QJsbqFwLAwnjsqy4e+y4+Eut4J OJ1dt+a5Y0IqVjXdM8NZE4BWIG5C/Jt9FT8KyfI/+hgrOXoJPAWFCfAnQXPd sQcMxFUXUTr6nT6MdkqidmbQw+qIJCeNrADh5FVftZnu2wsj76SJlQ== =VvqL -----END PGP SIGNATURE-----
publickey - tincantech@protonmail.com - 0x09BC3D44.asc
Description: application/pgp-keys
publickey - tincantech@protonmail.com - 0x09BC3D44.asc.sig
Description: PGP signature
_______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
