That's the mail thread where the problem was discussed; sorry our pastebin stuff disappeared but it turns out the pastebin variety we use had a bug where it would treat permanent entries as one-month entries, so all our configs disappeared.
I can't post easy repro instructions because getting an x509 infrastructure working isn't easy :) I don't and didn't have time to set up a fresh VM and try to reproduce from scratch because i've never used one of those certificate wizards.
Surely if you are going to package a version of a program that is unstable source-wise, the package should be updated regularly to reflect this?
On a side note, I feel the barrier to reporting a bug is very high; I very greatly resent having to create an account just to report a bug (a bug which doesn't affect me since I had to switch to a manually maintained version anyway; reporting was just a courtesy to the community); the implication that I should then waste valuable time compiling repro details for a bug which the developers of the software have confirmed (and have confirmed a fix for) seems wrong to me.
Hi Thierry:
http:// sourceforge. net/mailarchive /forum. php?thread_ name=dac97fdc77 ef4700eab65450a 4fc2451% 40127001. org&forum_ name=openvpn- users
That's the mail thread where the problem was discussed; sorry our pastebin stuff disappeared but it turns out the pastebin variety we use had a bug where it would treat permanent entries as one-month entries, so all our configs disappeared.
I can't post easy repro instructions because getting an x509 infrastructure working isn't easy :) I don't and didn't have time to set up a fresh VM and try to reproduce from scratch because i've never used one of those certificate wizards.
Surely if you are going to package a version of a program that is unstable source-wise, the package should be updated regularly to reflect this?
On a side note, I feel the barrier to reporting a bug is very high; I very greatly resent having to create an account just to report a bug (a bug which doesn't affect me since I had to switch to a manually maintained version anyway; reporting was just a courtesy to the community); the implication that I should then waste valuable time compiling repro details for a bug which the developers of the software have confirmed (and have confirmed a fix for) seems wrong to me.