Re: [Openvpn-devel] OpenVPN 2.4.8 released

[Ton van Vliet]

Hi,

For the record: Following your suggestion, I have added KB2921916 to my 
Win7 system, however,when adding another TAP device, the certificate 
chain processing Error 0x800b0109 still appears in setupapi.dev.log


Regards,
Ton.

On 11-11-19 10:22, Simon Rozman wrote:

Hi,


Is your computer perhaps behind in Windows updates? My hunch is that
Digicert's latest root certificate is not availabe in the Windows
certificate store and this causes the failure.

Samuli

thanks for the hint! but I don't know why uninstall/reinstall make
things work?

Mind that this OpenVPN release also brings the TAP-Windows6 driver update -
first one after some years. That's why there were no issues upgrading the
OpenVPN in the past years.

The TAP-Windows6 driver remains loaded when there are TAP adapters present.
Even if adapters are in the "disconnected" state. This makes upgrading the
driver a real challenge. I would suggest disabling all TAP adapters before
attempting the upgrade. Disabling the last of the TAP adapters will cause
Windows kernel to unload the TAP-Windows6, allowing its upgrade.


   our windows 7 update is stay at 2019-8, which is not very far behind.
but we do security-only update to prevent telemetry, I don't know if
that make difference.
   I will try again when windows update mess quiet down. December patch
is always good these years. hope it is the same this year.

1. Windows 7 have issues with SHA-256 signatures. In general, it works. But,
for optimal experience you should install KB2921916 (not available via Windows
Update). Maybe that's the reason for driver signature verification failure
recorded in your log. Probably, this error is recorded in the log on all
Windows 7 computers without KB2921916.

2. Mind that initial release of OpenVPN 2.4.8 is shipped using separate
installers for Windows 7/8/8.1/Server2008R2/Server2012R2 _and_ Windows
10/Server2016/Server2019. Please, make sure you are using the first one on
Windows 7. We do plan to unify the installers back to a single one in future
releases to avoid confusion.

Regards,
Simon


___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel


___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] OpenVPN 2.4.8 released

[d tbsky]

Simon Rozman 
> The TAP-Windows6 driver remains loaded when there are TAP adapters present.
> Even if adapters are in the "disconnected" state. This makes upgrading the
> driver a real challenge. I would suggest disabling all TAP adapters before
> attempting the upgrade. Disabling the last of the TAP adapters will cause
> Windows kernel to unload the TAP-Windows6, allowing its upgrade.

 try to disable TAP Adapter and upgrade. there is no more error
during installation. but when I try to connect it shows the tap device
is in use. reboot is useless.
if I uninstall tap-windows 9.21 first and then upgrade, everything
works fine even without reboot.

we don't have KB2921916 installed and we use correct win7 installer.

Regards,
tbskyd


___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] OpenVPN 2.4.8 released

[Simon Rozman]

Hi,

> > Is your computer perhaps behind in Windows updates? My hunch is that
> > Digicert's latest root certificate is not availabe in the Windows
> > certificate store and this causes the failure.
> >
> > Samuli
>
>thanks for the hint! but I don't know why uninstall/reinstall make
> things work?

Mind that this OpenVPN release also brings the TAP-Windows6 driver update - 
first one after some years. That's why there were no issues upgrading the 
OpenVPN in the past years.

The TAP-Windows6 driver remains loaded when there are TAP adapters present. 
Even if adapters are in the "disconnected" state. This makes upgrading the 
driver a real challenge. I would suggest disabling all TAP adapters before 
attempting the upgrade. Disabling the last of the TAP adapters will cause 
Windows kernel to unload the TAP-Windows6, allowing its upgrade.

>   our windows 7 update is stay at 2019-8, which is not very far behind.
> but we do security-only update to prevent telemetry, I don't know if
> that make difference.
>   I will try again when windows update mess quiet down. December patch
> is always good these years. hope it is the same this year.

1. Windows 7 have issues with SHA-256 signatures. In general, it works. But, 
for optimal experience you should install KB2921916 (not available via Windows 
Update). Maybe that's the reason for driver signature verification failure 
recorded in your log. Probably, this error is recorded in the log on all 
Windows 7 computers without KB2921916.

2. Mind that initial release of OpenVPN 2.4.8 is shipped using separate 
installers for Windows 7/8/8.1/Server2008R2/Server2012R2 _and_ Windows 
10/Server2016/Server2019. Please, make sure you are using the first one on 
Windows 7. We do plan to unify the installers back to a single one in future 
releases to avoid confusion.

Regards,
Simon


smime.p7s
Description: S/MIME cryptographic signature
___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] OpenVPN 2.4.8 released

[d tbsky]

Samuli Seppänen ：
> The error is pretty clear:
>
> Error 0x800b0109: A certificate chain processed, but terminated in a
> root certificate which is not trusted by the trust provider.
>
> Is your computer perhaps behind in Windows updates? My hunch is that
> Digicert's latest root certificate is not availabe in the Windows
> certificate store and this causes the failure.
>
> Samuli

   thanks for the hint! but I don't know why uninstall/reinstall make
things work?

  our windows 7 update is stay at 2019-8, which is not very far
behind. but we do security-only update to prevent telemetry, I don't
know if that make difference.
  I will try again when windows update mess quiet down. December patch
is always good these years. hope it is the same this year.

Regards,
tbskyd


___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] OpenVPN 2.4.8 released

[Samuli Seppänen]

Il 07/11/19 05:46, d tbsky ha scritto:
> 
>> It would be interesting too what error message there is in setupapi.dev.log:
>>
> 
> I found a win7 vm with openvpn 2.4.6. try to upgrade to 2.4.8 and get
> the same result.
> setupapi.dev.log attached. there are some international characters but
> I think they are not important.
> I snapshot the vm before upgrade. so I can repeat the procedure if necessary.
> 
> Regards,
> tbskyd
> 

Hi,

The error is pretty clear:

Error 0x800b0109: A certificate chain processed, but terminated in a
root certificate which is not trusted by the trust provider.

Is your computer perhaps behind in Windows updates? My hunch is that
Digicert's latest root certificate is not availabe in the Windows
certificate store and this causes the failure.

Samuli



signature.asc
Description: OpenPGP digital signature
___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] OpenVPN 2.4.8 released

[d tbsky]

> It would be interesting too what error message there is in setupapi.dev.log:
>

I found a win7 vm with openvpn 2.4.6. try to upgrade to 2.4.8 and get
the same result.
setupapi.dev.log attached. there are some international characters but
I think they are not important.
I snapshot the vm before upgrade. so I can repeat the procedure if necessary.

Regards,
tbskyd
[Boot Session: 2019/11/07 11:24:16.500]

>>>  [Device Install (UpdateDriverForPlugAndPlayDevices) - tap0901]
>>>  Section start 2019/11/07 11:26:35.994
  cmd: "C:\Program Files\TAP-Windows\bin\tapinstall.exe" update "C:\Program 
Files\TAP-Windows\driver\OemVista.inf" tap0901
 dvi: Set selected driver complete.
 dvi: {Build Driver List} 11:26:36.119
 dvi:  Searching for hardware ID(s):
 dvi:   tap0901
 cpy:  Policy is set to make all digital signatures equal.
 dvi:  Processing a single INF: 'c:\program 
files\tap-windows\driver\oemvista.inf'
 inf:  Opened INF: 'c:\program files\tap-windows\driver\oemvista.inf' 
([strings])
 sig:  {_VERIFY_FILE_SIGNATURE} 11:26:36.135
 sig:   Key  = oemvista.inf
 sig:   FilePath = c:\program files\tap-windows\driver\oemvista.inf
 sig:   Catalog  = c:\program files\tap-windows\driver\tap0901.cat
!sig:   Verifying file against specific (valid) catalog failed! 
(0x800b0109)
!sig:   Error 0x800b0109: A certificate chain processed, but 
terminated in a root certificate which is not trusted by the trust provider.
 sig:  {_VERIFY_FILE_SIGNATURE exit(0x800b0109)} 11:26:36.369
 sig:  {_VERIFY_FILE_SIGNATURE} 11:26:36.369
 sig:   Key  = oemvista.inf
 sig:   FilePath = c:\program files\tap-windows\driver\oemvista.inf
 sig:   Catalog  = c:\program files\tap-windows\driver\tap0901.cat
 sig:   Success: File is signed in Authenticode(tm) catalog.
 sig:   Error 0xe242: The publisher of an Authenticode(tm) 
signed catalog has not yet been established as trusted.
 sig:  {_VERIFY_FILE_SIGNATURE exit(0xe242)} 11:26:36.447
 dvi:  Created Driver Node:
 dvi:   HardwareID   - tap0901
 dvi:   InfName  - c:\program 
files\tap-windows\driver\oemvista.inf
 dvi:   DevDesc  - TAP-Windows Adapter V9
 dvi:   DrvDesc  - TAP-Windows Adapter V9
 dvi:   Provider - TAP-Windows Provider V9
 dvi:   Mfg  - TAP-Windows Provider V9
 dvi:   ModelsSec- tap0901.NTamd64
 dvi:   InstallSec   - tap0901.ndi
 dvi:   ActualSec- tap0901.ndi
 dvi:   Rank - 0x00ff
 dvi:   Signer   - OpenVPN Inc.
 dvi:   Signer Score - Authenticode
 dvi:   DrvDate  - 09/27/2019
 dvi:   Version  - 9.24.2.601
 dvi: {Build Driver List - exit(0x)} 11:26:36.447
 dvi: {DIF_SELECTBESTCOMPATDRV} 11:26:36.447
 dvi:  Using exported function 'NetClassInstaller' in module 
'C:\Windows\system32\NetCfgx.dll'.
 dvi:  Class installer == NetCfgx.dll,NetClassInstaller
 dvi:  Using exported function 'NciDeviceInstall' in module 
'C:\Windows\system32\nci.dll'.
 dvi:  CoInstaller 1 == nci.dll,NciDeviceInstall
 dvi:  Using exported function 'WlanDeviceClassCoInstaller' in module 
'C:\Windows\system32\wlaninst.dll'.
 dvi:  CoInstaller 2 == wlaninst.dll,WlanDeviceClassCoInstaller
 dvi:  Using exported function 'WwanDeviceClassCoInstaller' in module 
'C:\Windows\system32\wwaninst.dll'.
 dvi:  CoInstaller 3 == wwaninst.dll,WwanDeviceClassCoInstaller
 dvi:  CoInstaller 1: Enter 11:26:36.494
 dvi:  CoInstaller 1: Exit
 dvi:  CoInstaller 2: Enter 11:26:36.494
 dvi:  CoInstaller 2: Exit
 dvi:  CoInstaller 3: Enter 11:26:36.494
 dvi:  CoInstaller 3: Exit
 dvi:  Class installer: Enter 11:26:36.494
 dvi:  Class installer: Exit
 dvi:  Default installer: Enter 11:26:36.494
 dvi:   {Select Best Driver}
 dvi:Selected driver installs from section [tap0901.ndi] in 
'c:\program files\tap-windows\driver\oemvista.inf'.
 dvi:Class GUID of device remains: 
{4d36e972-e325-11ce-bfc1-08002be10318}.
 dvi:Set selected driver complete.
 dvi:Selected:
 dvi: Description - [TAP-Windows Adapter V9]
 dvi: InfFile - [c:\program 
files\tap-windows\driver\oemvista.inf]
 dvi: Section - [tap0901.ndi]
 dvi: Signer  - [OpenVPN Inc.]
 dvi: Rank- [0x00ff]
 dvi:   {Select Best Driver - exit(0x)}
 dvi:  Default installer: Exit
 dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x)} 11:26:36.510

Re: [Openvpn-devel] OpenVPN 2.4.8 released

[samuli]

Hi,

Il Mercoledì 6 novembre 2019, d tbsky scrive:
> after reading the thread, I think now it's safe to upgrae my windows 7
>  from openvpn 2.4.7 to 2.4.8. so I download the installer and click
> it.
> 
> the installer complains about can not install tap drivers and I click
> ok to let it go. when I try to connect,  openvpn said the tap driver
> is in use and failed.
> I reboot and reinstall but still can not see tap device in my network.
> 
> finally I uninstall  tap and openvpn then install again, this time
> everything is ok, I am lucky.
> so openvpn-gui 2.4.8 upgrade is not as smooth as previous versions.

It would be interesting too what error message there is in setupapi.dev.log:

https://community.openvpn.net/openvpn/wiki/ManagingWindowsTAPDrivers

It seems to me like some changes that were made since the previous release 
cause upgrade issues.

Samuli
___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] OpenVPN 2.4.8 released

[d tbsky]

after reading the thread, I think now it's safe to upgrae my windows 7
 from openvpn 2.4.7 to 2.4.8. so I download the installer and click
it.

the installer complains about can not install tap drivers and I click
ok to let it go. when I try to connect,  openvpn said the tap driver
is in use and failed.
I reboot and reinstall but still can not see tap device in my network.

finally I uninstall  tap and openvpn then install again, this time
everything is ok, I am lucky.
so openvpn-gui 2.4.8 upgrade is not as smooth as previous versions.

Regards,
tbskyd


___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] OpenVPN 2.4.8 released

[Samuli Seppänen]

Hi,

Good to hear that it is working now! Possibly one of the bits we've
flipped in tap-windows6 since the previous release caused this
misbehavior (for you). So far nobody else has reported this problem.

Samuli

Il 04/11/19 00:04, Ton van Vliet ha scritto:
> Hi Simon,
> 
> Thanks for the additional tips.
> 
> I already replied to Samuli yesterday, but only now noticed that I did not 
> reply to the list.
> 
> I did play around with pnputil (Samuli is using it in his script as well), 
> but was not able to remove all drivers with it: some were 'in use', while 
> others were listed but somehow 'invalid'.
> 
> Only after I uninstalled tap-windows6, I was able to remove the 'in use' 
> ones. The other ones were leftover oem.inf files from earlier failing 
> installs.
> 
> I had to re-instantiate all TAP-devices after this, but all is fine now.
> 
> Normally I would prefer to troubleshoot, however, since I apparently am the 
> only one with the problem, I took Samuli's shortcut and uninstalled 
> tap-windows6
> 
> Best regards,
> Ton
> 
> On 03-11-19 17:18, Simon Rozman wrote:
> 
>> Hi Ton,
>>
>> You can also use pnputil.exe (in an elevated command prompt) to check 
>> version, uninstall, and/or install TAP driver manually. The pnputil is a 
>> stock command line utility for driver management on all Windows.
>>
>> I advise you use pnputil to list all your installed TAP-Windows6 drivers - 
>> yes, there may be more than one version installed.  Carefully uninstall all 
>> TAP-Windows6 drivers. "Carefully" in a sense that you pay extra attention to 
>> delete oem.inf entries corresponding to the TAP-Windows6, and not your 
>> graphics card or disk controller.  Note that network interface settings are 
>> stored elsewhere in registry and uninstalling the driver will not delete 
>> them. Your TAP interfaces will just disappear for a while. You already 
>> noticed that phenomena before.
>>
>> Next, install the latest driver - you can use the official installer. Or - 
>> if you already have it installed - find a copy of the driver in C:\Program 
>> Files\TAP-Windows6\driver (your path may vary) and use pnputil to install 
>> the driver. Or - right click on the .inf file and select Install. Your TAP 
>> interfaces should reappear.
>>
>> Also, since you're troubleshooting, I'd strongly advise you to reboot in 
>> between.
>>
>> Best regards,
>> Simon
> 
> 
> 
> ___
> Openvpn-devel mailing list
> Openvpn-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openvpn-devel
> 



___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] OpenVPN 2.4.8 released

[Ton van Vliet]

Hi Simon,

Thanks for the additional tips.

I already replied to Samuli yesterday, but only now noticed that I did not 
reply to the list.

I did play around with pnputil (Samuli is using it in his script as well), but 
was not able to remove all drivers with it: some were 'in use', while others 
were listed but somehow 'invalid'.

Only after I uninstalled tap-windows6, I was able to remove the 'in use' ones. The 
other ones were leftover oem.inf files from earlier failing installs.

I had to re-instantiate all TAP-devices after this, but all is fine now.

Normally I would prefer to troubleshoot, however, since I apparently am the 
only one with the problem, I took Samuli's shortcut and uninstalled tap-windows6

Best regards,
Ton

On 03-11-19 17:18, Simon Rozman wrote:


Hi Ton,

You can also use pnputil.exe (in an elevated command prompt) to check version, 
uninstall, and/or install TAP driver manually. The pnputil is a stock command 
line utility for driver management on all Windows.

I advise you use pnputil to list all your installed TAP-Windows6 drivers - yes, there may be 
more than one version installed.  Carefully uninstall all TAP-Windows6 drivers. 
"Carefully" in a sense that you pay extra attention to delete oem.inf 
entries corresponding to the TAP-Windows6, and not your graphics card or disk controller.  Note 
that network interface settings are stored elsewhere in registry and uninstalling the driver 
will not delete them. Your TAP interfaces will just disappear for a while. You already noticed 
that phenomena before.

Next, install the latest driver - you can use the official installer. Or - if 
you already have it installed - find a copy of the driver in C:\Program 
Files\TAP-Windows6\driver (your path may vary) and use pnputil to install the 
driver. Or - right click on the .inf file and select Install. Your TAP 
interfaces should reappear.

Also, since you're troubleshooting, I'd strongly advise you to reboot in 
between.

Best regards,
Simon


___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] OpenVPN 2.4.8 released

[Ton van Vliet]

I noticed that my last reply was not sent to the mailing list, so this 
is a duplicate of the reply I sent to Samuli Seppänen


Hi,

Thanks for your detailed instructions!

On 02-11-19 8:08, Samuli Seppänen wrote:

Hi,

Il 01/11/19 23:40, Ton van Vliet ha scritto:

Thanks for the info.

A quick reply for now:

On 01-11-19 19:28, Samuli Seppänen wrote:

Hi,

Il 01/11/19 18:58, Ton van Vliet ha scritto:

Hi,

A sincere 'Thank You' to all developers for their continuous work done
on OpenVPN !

Both the 2.4.8-I601-Win7 and 2.4.8-I602-Win7 executables fail with 'An
error occurred installing the TAP device drivers.'

What operating system are you running exactly?

This installation is on Win7 Home Premium (SP1)

Ok.


After running the 2.4.8 installer, all of my (named) TAP devices had
disappeared (I have more than one!)

Reinstalling the previous 2.4.7-Win7 version (twice) brought them all
back to life again.

Is there a way I can get more detailed information about what could be
causing this. It is the first time that I encounter this error.

Yes there is:



In particular check C:\Windows\inf\setupapi.dev.log. It contains
installation logs for Windows drivers in general, not just tap-windows6.
It generally gives a pretty good idea of the problem. It should not have
any sensitive information in it so you can post the relevant lines here.

In the relevant sections are quite a few error lines starting with '!',
but these are present in both the 2.4.7 and 2.4.8 install (most of them
are related to failing verification)

Except for the following lines, which are only present in the 2.4.8 install

!    dvi:  Device 'ROOT\NET\0021' required
reboot: Device has problem: 0x0a: CM_PROB_FAILED_START.
!    dvi:  Device 'ROOT\NET\0012' required
reboot: Device has problem: 0x0a: CM_PROB_FAILED_START.
!    dvi:  Device 'ROOT\NET\0009' required
reboot: Device has problem: 0x0a: CM_PROB_FAILED_START.
!    dvi:  Device 'ROOT\NET\0004' required
reboot: Device has problem: 0x0a: CM_PROB_FAILED_START.
!    dvi:  Device 'ROOT\NET\0005' required
reboot: Device has problem: 0x0a: CM_PROB_FAILED_START.
!    dvi:  Device 'ROOT\NET\0011' required
reboot: Device has problem: 0x0a: CM_PROB_FAILED_START.
!    dvi:  Device 'ROOT\NET\0002' required
reboot: Device has problem: 0x0a: CM_PROB_FAILED_START.
!    dvi:  Device 'ROOT\NET\0013' required
reboot: Device has problem: 0x0a: CM_PROB_FAILED_START.

and the following line, which occurs multiple times (for each TAP device)

!!!  dvi: Device not started: Device has problem:
0x0a: CM_PROB_FAILED_START.

Does that help, or is more information needed to get a clue?

Hi,

I've never seen this particular problem. I'm not sure what "Device 
required reboot" means. Does it suggest rebooting the computer? Maybe
worth a shot if you did not do it already.

If reboot does not help I recommend wiping all traces of tap-windows6
from the computer and then installing 2.4.8-I602-Win7. The process I use
during testing is this:

1) Uninstall tap-windows6
2) Remove traces of tap-windows6 from driver store

Clone or download (as zip):



Launch a Powershell session as an Administrator. Then

cd tap-windows-scripts
./Remove-Tapwindows.ps1

This will display you the tap-windows6 drivers it would remove from
the driver store, something like this:

  Would remove oem.inf
  Would remove oem.inf

In your case there would probably be many of these lines. They all
should start with "oem".

To actually remove the drivers add -Yes parameter:

   ./Remove-Tapwindows.ps1 -Yes

   After this there are no traces of tap-windows6 on your computer.

3) Install 2.4.8-I602-Win7 and see if the problem is gone

--

Let me know if this resolves the problem.


Following your instructions, I managed to remove all tap-windows6 
references.


Apart from the one that was in use, there were 2 other leftover 
oem.inf files that showed up using your script, but which the script 
could not remove (not even with an added -f parameter) but after some 
digging into the registry and windows system folders I managed to get 
rid of these as well.


After that the installation ran flawlessly.

I have no idea why it went wrong this time, as I have been following 
along with all releases for several years without any hick-ups, however, 
as apparently I am the only one having this issue, I fully understand 
your (workaround) approach vector.


Thanks again.

--

Ton


Samuli


--
Ton

On 31-10-19 13:04, Samuli Seppänen wrote:

Hi,

We recently found out that the code signing certificate the 2.4.8
Windows installers use expired a couple of weeks ago. I will get a new
certificate 

Re: [Openvpn-devel] OpenVPN 2.4.8 released

[Simon Rozman]

Hi Ton,

You can also use pnputil.exe (in an elevated command prompt) to check version, 
uninstall, and/or install TAP driver manually. The pnputil is a stock command 
line utility for driver management on all Windows.

I advise you use pnputil to list all your installed TAP-Windows6 drivers - yes, 
there may be more than one version installed.  Carefully uninstall all 
TAP-Windows6 drivers. "Carefully" in a sense that you pay extra attention to 
delete oem.inf entries corresponding to the TAP-Windows6, and not your 
graphics card or disk controller.  Note that network interface settings are 
stored elsewhere in registry and uninstalling the driver will not delete them. 
Your TAP interfaces will just disappear for a while. You already noticed that 
phenomena before.

Next, install the latest driver - you can use the official installer. Or - if 
you already have it installed - find a copy of the driver in C:\Program 
Files\TAP-Windows6\driver (your path may vary) and use pnputil to install the 
driver. Or - right click on the .inf file and select Install. Your TAP 
interfaces should reappear.

Also, since you're troubleshooting, I'd strongly advise you to reboot in 
between.

Best regards,
Simon


smime.p7s
Description: S/MIME cryptographic signature
___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] OpenVPN 2.4.8 released

[Samuli Seppänen]

Hi,

Il 01/11/19 23:40, Ton van Vliet ha scritto:
> Thanks for the info.
> 
> A quick reply for now:
> 
> On 01-11-19 19:28, Samuli Seppänen wrote:
>> Hi,
>>
>> Il 01/11/19 18:58, Ton van Vliet ha scritto:
>>> Hi,
>>>
>>> A sincere 'Thank You' to all developers for their continuous work done
>>> on OpenVPN !
>>>
>>> Both the 2.4.8-I601-Win7 and 2.4.8-I602-Win7 executables fail with 'An
>>> error occurred installing the TAP device drivers.'
>> What operating system are you running exactly?
> 
> This installation is on Win7 Home Premium (SP1)

Ok.

>>
>>> After running the 2.4.8 installer, all of my (named) TAP devices had
>>> disappeared (I have more than one!)
>>>
>>> Reinstalling the previous 2.4.7-Win7 version (twice) brought them all
>>> back to life again.
>>>
>>> Is there a way I can get more detailed information about what could be
>>> causing this. It is the first time that I encounter this error.
>> Yes there is:
>>
>> 
>>
>> In particular check C:\Windows\inf\setupapi.dev.log. It contains
>> installation logs for Windows drivers in general, not just tap-windows6.
>> It generally gives a pretty good idea of the problem. It should not have
>> any sensitive information in it so you can post the relevant lines here.
> 
> In the relevant sections are quite a few error lines starting with '!',
> but these are present in both the 2.4.7 and 2.4.8 install (most of them
> are related to failing verification)
> 
> Except for the following lines, which are only present in the 2.4.8 install
> 
> !    dvi:  Device 'ROOT\NET\0021' required
> reboot: Device has problem: 0x0a: CM_PROB_FAILED_START.
> !    dvi:  Device 'ROOT\NET\0012' required
> reboot: Device has problem: 0x0a: CM_PROB_FAILED_START.
> !    dvi:  Device 'ROOT\NET\0009' required
> reboot: Device has problem: 0x0a: CM_PROB_FAILED_START.
> !    dvi:  Device 'ROOT\NET\0004' required
> reboot: Device has problem: 0x0a: CM_PROB_FAILED_START.
> !    dvi:  Device 'ROOT\NET\0005' required
> reboot: Device has problem: 0x0a: CM_PROB_FAILED_START.
> !    dvi:  Device 'ROOT\NET\0011' required
> reboot: Device has problem: 0x0a: CM_PROB_FAILED_START.
> !    dvi:  Device 'ROOT\NET\0002' required
> reboot: Device has problem: 0x0a: CM_PROB_FAILED_START.
> !    dvi:  Device 'ROOT\NET\0013' required
> reboot: Device has problem: 0x0a: CM_PROB_FAILED_START.
> 
> and the following line, which occurs multiple times (for each TAP device)
> 
> !!!  dvi: Device not started: Device has problem:
> 0x0a: CM_PROB_FAILED_START.
> 
> Does that help, or is more information needed to get a clue?

Hi,

I've never seen this particular problem. I'm not sure what "Device 
required reboot" means. Does it suggest rebooting the computer? Maybe
worth a shot if you did not do it already.

If reboot does not help I recommend wiping all traces of tap-windows6
from the computer and then installing 2.4.8-I602-Win7. The process I use
during testing is this:

1) Uninstall tap-windows6
2) Remove traces of tap-windows6 from driver store

   Clone or download (as zip):

   

   Launch a Powershell session as an Administrator. Then

   cd tap-windows-scripts
   ./Remove-Tapwindows.ps1

   This will display you the tap-windows6 drivers it would remove from
   the driver store, something like this:

 Would remove oem.inf
 Would remove oem.inf

   In your case there would probably be many of these lines. They all
   should start with "oem".

   To actually remove the drivers add -Yes parameter:

  ./Remove-Tapwindows.ps1 -Yes

  After this there are no traces of tap-windows6 on your computer.

3) Install 2.4.8-I602-Win7 and see if the problem is gone

--

Let me know if this resolves the problem.

> 
>> Samuli
>>
>>> -- 
>>> Ton
>>>
>>> On 31-10-19 13:04, Samuli Seppänen wrote:
 Hi,

 We recently found out that the code signing certificate the 2.4.8
 Windows installers use expired a couple of weeks ago. I will get a new
 certificate today evening (~6 hours) and push out new installers.

 This problem only seems to affect the prompt you get when you
 double-click on the installer executable. You probably see "Unknown
 publisher" there. Besides that Windows seems to be perfectly happy with
 the executables and libraries. That is the main reason why a problem
 such as this was able to slip through testing.

 Samuli

 Il 31/10/19 12:27, Samuli Seppänen ha scritto:
> The OpenVPN community project team is proud to release OpenVPN
> 2.4.8. It
> can be downloaded from here:
>
> 
>
> This is primarily a maintenance release with bugfixes and
> 

Re: [Openvpn-devel] OpenVPN 2.4.8 released

[Ton van Vliet]

Thanks for the info.

A quick reply for now:

On 01-11-19 19:28, Samuli Seppänen wrote:

Hi,

Il 01/11/19 18:58, Ton van Vliet ha scritto:

Hi,

A sincere 'Thank You' to all developers for their continuous work done
on OpenVPN !

Both the 2.4.8-I601-Win7 and 2.4.8-I602-Win7 executables fail with 'An
error occurred installing the TAP device drivers.'

What operating system are you running exactly?


This installation is on Win7 Home Premium (SP1)




After running the 2.4.8 installer, all of my (named) TAP devices had
disappeared (I have more than one!)

Reinstalling the previous 2.4.7-Win7 version (twice) brought them all
back to life again.

Is there a way I can get more detailed information about what could be
causing this. It is the first time that I encounter this error.

Yes there is:



In particular check C:\Windows\inf\setupapi.dev.log. It contains
installation logs for Windows drivers in general, not just tap-windows6.
It generally gives a pretty good idea of the problem. It should not have
any sensitive information in it so you can post the relevant lines here.


In the relevant sections are quite a few error lines starting with '!', 
but these are present in both the 2.4.7 and 2.4.8 install (most of them 
are related to failing verification)


Except for the following lines, which are only present in the 2.4.8 install

!    dvi:  Device 'ROOT\NET\0021' required 
reboot: Device has problem: 0x0a: CM_PROB_FAILED_START.
!    dvi:  Device 'ROOT\NET\0012' required 
reboot: Device has problem: 0x0a: CM_PROB_FAILED_START.
!    dvi:  Device 'ROOT\NET\0009' required 
reboot: Device has problem: 0x0a: CM_PROB_FAILED_START.
!    dvi:  Device 'ROOT\NET\0004' required 
reboot: Device has problem: 0x0a: CM_PROB_FAILED_START.
!    dvi:  Device 'ROOT\NET\0005' required 
reboot: Device has problem: 0x0a: CM_PROB_FAILED_START.
!    dvi:  Device 'ROOT\NET\0011' required 
reboot: Device has problem: 0x0a: CM_PROB_FAILED_START.
!    dvi:  Device 'ROOT\NET\0002' required 
reboot: Device has problem: 0x0a: CM_PROB_FAILED_START.
!    dvi:  Device 'ROOT\NET\0013' required 
reboot: Device has problem: 0x0a: CM_PROB_FAILED_START.


and the following line, which occurs multiple times (for each TAP device)

!!!  dvi: Device not started: Device has problem: 
0x0a: CM_PROB_FAILED_START.


Does that help, or is more information needed to get a clue?


Samuli


--
Ton

On 31-10-19 13:04, Samuli Seppänen wrote:

Hi,

We recently found out that the code signing certificate the 2.4.8
Windows installers use expired a couple of weeks ago. I will get a new
certificate today evening (~6 hours) and push out new installers.

This problem only seems to affect the prompt you get when you
double-click on the installer executable. You probably see "Unknown
publisher" there. Besides that Windows seems to be perfectly happy with
the executables and libraries. That is the main reason why a problem
such as this was able to slip through testing.

Samuli

Il 31/10/19 12:27, Samuli Seppänen ha scritto:

The OpenVPN community project team is proud to release OpenVPN 2.4.8. It
can be downloaded from here:



This is primarily a maintenance release with bugfixes and improvements.
The Windows installers (I601) have several improvements compared to the
previous release:

* New tap-windows6 driver (9.24.2) which fixes some suspend and resume
issues
* Latest OpenVPN-GUI
* Considerable performance boost due to new compiler optimization flags

A summary of all included changes is available here:



A full list of changes is available here:



Please note that LibreSSL is not a supported crypto backend. We accept
patches and we do test on OpenBSD 6.0 which comes with LibreSSL, but if
newer versions of LibreSSL break API compatibility we do not take
responsibility to fix that.

Also note that  Windows installers have been built with NSIS version
that has been patched against several NSIS installer code execution and
privilege escalation problems:



Based on our testing, though, older Windows versions such as Windows 7
might not benefit from these fixes. We thus strongly encourage you to
always move NSIS installers to a non-user-writeable location before
running them. Our long-term plan is to migrate to using MSI installers
instead.

Compared to OpenVPN 2.3 this is a major update with a large number of
new features, improvements and fixes. Some of the major features are
AEAD (GCM) cipher and Elliptic Curve DH key exchange support, improved
IPv4/IPv6 dual 

Re: [Openvpn-devel] OpenVPN 2.4.8 released

[Samuli Seppänen]

Hi,

Il 01/11/19 18:58, Ton van Vliet ha scritto:
> Hi,
> 
> A sincere 'Thank You' to all developers for their continuous work done
> on OpenVPN !
> 
> Both the 2.4.8-I601-Win7 and 2.4.8-I602-Win7 executables fail with 'An
> error occurred installing the TAP device drivers.'

What operating system are you running exactly?

> After running the 2.4.8 installer, all of my (named) TAP devices had
> disappeared (I have more than one!)
> 
> Reinstalling the previous 2.4.7-Win7 version (twice) brought them all
> back to life again.
> 
> Is there a way I can get more detailed information about what could be
> causing this. It is the first time that I encounter this error.

Yes there is:



In particular check C:\Windows\inf\setupapi.dev.log. It contains
installation logs for Windows drivers in general, not just tap-windows6.
It generally gives a pretty good idea of the problem. It should not have
any sensitive information in it so you can post the relevant lines here.

Samuli

> 
> -- 
> Ton
> 
> On 31-10-19 13:04, Samuli Seppänen wrote:
>> Hi,
>>
>> We recently found out that the code signing certificate the 2.4.8
>> Windows installers use expired a couple of weeks ago. I will get a new
>> certificate today evening (~6 hours) and push out new installers.
>>
>> This problem only seems to affect the prompt you get when you
>> double-click on the installer executable. You probably see "Unknown
>> publisher" there. Besides that Windows seems to be perfectly happy with
>> the executables and libraries. That is the main reason why a problem
>> such as this was able to slip through testing.
>>
>> Samuli
>>
>> Il 31/10/19 12:27, Samuli Seppänen ha scritto:
>>> The OpenVPN community project team is proud to release OpenVPN 2.4.8. It
>>> can be downloaded from here:
>>>
>>> 
>>>
>>> This is primarily a maintenance release with bugfixes and improvements.
>>> The Windows installers (I601) have several improvements compared to the
>>> previous release:
>>>
>>> * New tap-windows6 driver (9.24.2) which fixes some suspend and resume
>>> issues
>>> * Latest OpenVPN-GUI
>>> * Considerable performance boost due to new compiler optimization flags
>>>
>>> A summary of all included changes is available here:
>>>
>>> 
>>>
>>> A full list of changes is available here:
>>>
>>> 
>>>
>>> Please note that LibreSSL is not a supported crypto backend. We accept
>>> patches and we do test on OpenBSD 6.0 which comes with LibreSSL, but if
>>> newer versions of LibreSSL break API compatibility we do not take
>>> responsibility to fix that.
>>>
>>> Also note that  Windows installers have been built with NSIS version
>>> that has been patched against several NSIS installer code execution and
>>> privilege escalation problems:
>>>
>>> 
>>>
>>> Based on our testing, though, older Windows versions such as Windows 7
>>> might not benefit from these fixes. We thus strongly encourage you to
>>> always move NSIS installers to a non-user-writeable location before
>>> running them. Our long-term plan is to migrate to using MSI installers
>>> instead.
>>>
>>> Compared to OpenVPN 2.3 this is a major update with a large number of
>>> new features, improvements and fixes. Some of the major features are
>>> AEAD (GCM) cipher and Elliptic Curve DH key exchange support, improved
>>> IPv4/IPv6 dual stack support and more seamless connection migration when
>>> client's IP address changes (Peer-ID). Also, the new --tls-crypt feature
>>> can be used to increase users' connection privacy.
>>>
>>> OpenVPN GUI bundled with the Windows installer has a large number of new
>>> features compared to the one bundled with OpenVPN 2.3. One of major
>>> features is the ability to run OpenVPN GUI without administrator privileges.
>>>
>>> For full details, look here:
>>>
>>> 
>>>
>>> The new OpenVPN GUI features are documented here:
>>>
>>> 
>>>
>>> Please note that OpenVPN 2.4 installers will not work on Windows XP.
>>>
>>> For generic help use these support channels:
>>>
>>> Official documentation:
>>> 
>>> Wiki: 
>>> Forums: 
>>> User mailing list: 
>>> User IRC channel: #openvpn at irc.freenode.net
>>>
>>> Please report bugs and ask development questions here:
>>>
>>> Bug tracker and wiki: 
>>> Developer mailing list: 
>>> Developer IRC channel: #openvpn-devel at irc.freenode.net (requires
>>> Freenode registration)
>>>
>>>
>>> Samuli
>>>
>>>

Re: [Openvpn-devel] OpenVPN 2.4.8 released

[Ton van Vliet]

Hi,

A sincere 'Thank You' to all developers for their continuous work done 
on OpenVPN !


Both the 2.4.8-I601-Win7 and 2.4.8-I602-Win7 executables fail with 'An 
error occurred installing the TAP device drivers.'


After running the 2.4.8 installer, all of my (named) TAP devices had 
disappeared (I have more than one!)


Reinstalling the previous 2.4.7-Win7 version (twice) brought them all 
back to life again.


Is there a way I can get more detailed information about what could be 
causing this. It is the first time that I encounter this error.


--
Ton

On 31-10-19 13:04, Samuli Seppänen wrote:

Hi,

We recently found out that the code signing certificate the 2.4.8
Windows installers use expired a couple of weeks ago. I will get a new
certificate today evening (~6 hours) and push out new installers.

This problem only seems to affect the prompt you get when you
double-click on the installer executable. You probably see "Unknown
publisher" there. Besides that Windows seems to be perfectly happy with
the executables and libraries. That is the main reason why a problem
such as this was able to slip through testing.

Samuli

Il 31/10/19 12:27, Samuli Seppänen ha scritto:

The OpenVPN community project team is proud to release OpenVPN 2.4.8. It
can be downloaded from here:



This is primarily a maintenance release with bugfixes and improvements.
The Windows installers (I601) have several improvements compared to the
previous release:

* New tap-windows6 driver (9.24.2) which fixes some suspend and resume
issues
* Latest OpenVPN-GUI
* Considerable performance boost due to new compiler optimization flags

A summary of all included changes is available here:



A full list of changes is available here:



Please note that LibreSSL is not a supported crypto backend. We accept
patches and we do test on OpenBSD 6.0 which comes with LibreSSL, but if
newer versions of LibreSSL break API compatibility we do not take
responsibility to fix that.

Also note that  Windows installers have been built with NSIS version
that has been patched against several NSIS installer code execution and
privilege escalation problems:



Based on our testing, though, older Windows versions such as Windows 7
might not benefit from these fixes. We thus strongly encourage you to
always move NSIS installers to a non-user-writeable location before
running them. Our long-term plan is to migrate to using MSI installers
instead.

Compared to OpenVPN 2.3 this is a major update with a large number of
new features, improvements and fixes. Some of the major features are
AEAD (GCM) cipher and Elliptic Curve DH key exchange support, improved
IPv4/IPv6 dual stack support and more seamless connection migration when
client's IP address changes (Peer-ID). Also, the new --tls-crypt feature
can be used to increase users' connection privacy.

OpenVPN GUI bundled with the Windows installer has a large number of new
features compared to the one bundled with OpenVPN 2.3. One of major
features is the ability to run OpenVPN GUI without administrator privileges.

For full details, look here:



The new OpenVPN GUI features are documented here:



Please note that OpenVPN 2.4 installers will not work on Windows XP.

For generic help use these support channels:

Official documentation:

Wiki: 
Forums: 
User mailing list: 
User IRC channel: #openvpn at irc.freenode.net

Please report bugs and ask development questions here:

Bug tracker and wiki: 
Developer mailing list: 
Developer IRC channel: #openvpn-devel at irc.freenode.net (requires
Freenode registration)


Samuli



___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel





___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel


___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Re: [Openvpn-devel] OpenVPN 2.4.8 released

[Samuli Seppänen]

Hi,

We recently found out that the code signing certificate the 2.4.8
Windows installers use expired a couple of weeks ago. I will get a new
certificate today evening (~6 hours) and push out new installers.

This problem only seems to affect the prompt you get when you
double-click on the installer executable. You probably see "Unknown
publisher" there. Besides that Windows seems to be perfectly happy with
the executables and libraries. That is the main reason why a problem
such as this was able to slip through testing.

Samuli

Il 31/10/19 12:27, Samuli Seppänen ha scritto:
> The OpenVPN community project team is proud to release OpenVPN 2.4.8. It
> can be downloaded from here:
> 
> 
> 
> This is primarily a maintenance release with bugfixes and improvements.
> The Windows installers (I601) have several improvements compared to the
> previous release:
> 
> * New tap-windows6 driver (9.24.2) which fixes some suspend and resume
> issues
> * Latest OpenVPN-GUI
> * Considerable performance boost due to new compiler optimization flags
> 
> A summary of all included changes is available here:
> 
> 
> 
> A full list of changes is available here:
> 
> 
> 
> Please note that LibreSSL is not a supported crypto backend. We accept
> patches and we do test on OpenBSD 6.0 which comes with LibreSSL, but if
> newer versions of LibreSSL break API compatibility we do not take
> responsibility to fix that.
> 
> Also note that  Windows installers have been built with NSIS version
> that has been patched against several NSIS installer code execution and
> privilege escalation problems:
> 
> 
> 
> Based on our testing, though, older Windows versions such as Windows 7
> might not benefit from these fixes. We thus strongly encourage you to
> always move NSIS installers to a non-user-writeable location before
> running them. Our long-term plan is to migrate to using MSI installers
> instead.
> 
> Compared to OpenVPN 2.3 this is a major update with a large number of
> new features, improvements and fixes. Some of the major features are
> AEAD (GCM) cipher and Elliptic Curve DH key exchange support, improved
> IPv4/IPv6 dual stack support and more seamless connection migration when
> client's IP address changes (Peer-ID). Also, the new --tls-crypt feature
> can be used to increase users' connection privacy.
> 
> OpenVPN GUI bundled with the Windows installer has a large number of new
> features compared to the one bundled with OpenVPN 2.3. One of major
> features is the ability to run OpenVPN GUI without administrator privileges.
> 
> For full details, look here:
> 
> 
> 
> The new OpenVPN GUI features are documented here:
> 
> 
> 
> Please note that OpenVPN 2.4 installers will not work on Windows XP.
> 
> For generic help use these support channels:
> 
> Official documentation:
> 
> Wiki: 
> Forums: 
> User mailing list: 
> User IRC channel: #openvpn at irc.freenode.net
> 
> Please report bugs and ask development questions here:
> 
> Bug tracker and wiki: 
> Developer mailing list: 
> Developer IRC channel: #openvpn-devel at irc.freenode.net (requires
> Freenode registration)
> 
> 
> Samuli
> 
> 
> 
> ___
> Openvpn-devel mailing list
> Openvpn-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openvpn-devel
> 




signature.asc
Description: OpenPGP digital signature
___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

[Openvpn-devel] OpenVPN 2.4.8 released

[Samuli Seppänen]

The OpenVPN community project team is proud to release OpenVPN 2.4.8. It
can be downloaded from here:



This is primarily a maintenance release with bugfixes and improvements.
The Windows installers (I601) have several improvements compared to the
previous release:

* New tap-windows6 driver (9.24.2) which fixes some suspend and resume
issues
* Latest OpenVPN-GUI
* Considerable performance boost due to new compiler optimization flags

A summary of all included changes is available here:



A full list of changes is available here:



Please note that LibreSSL is not a supported crypto backend. We accept
patches and we do test on OpenBSD 6.0 which comes with LibreSSL, but if
newer versions of LibreSSL break API compatibility we do not take
responsibility to fix that.

Also note that  Windows installers have been built with NSIS version
that has been patched against several NSIS installer code execution and
privilege escalation problems:



Based on our testing, though, older Windows versions such as Windows 7
might not benefit from these fixes. We thus strongly encourage you to
always move NSIS installers to a non-user-writeable location before
running them. Our long-term plan is to migrate to using MSI installers
instead.

Compared to OpenVPN 2.3 this is a major update with a large number of
new features, improvements and fixes. Some of the major features are
AEAD (GCM) cipher and Elliptic Curve DH key exchange support, improved
IPv4/IPv6 dual stack support and more seamless connection migration when
client's IP address changes (Peer-ID). Also, the new --tls-crypt feature
can be used to increase users' connection privacy.

OpenVPN GUI bundled with the Windows installer has a large number of new
features compared to the one bundled with OpenVPN 2.3. One of major
features is the ability to run OpenVPN GUI without administrator privileges.

For full details, look here:



The new OpenVPN GUI features are documented here:



Please note that OpenVPN 2.4 installers will not work on Windows XP.

For generic help use these support channels:

Official documentation:

Wiki: 
Forums: 
User mailing list: 
User IRC channel: #openvpn at irc.freenode.net

Please report bugs and ask development questions here:

Bug tracker and wiki: 
Developer mailing list: 
Developer IRC channel: #openvpn-devel at irc.freenode.net (requires
Freenode registration)


Samuli
Antonio Quartulli (1):
  mbedtls: fix segfault by calling mbedtls_cipher_free() in 
cipher_ctx_free()

Arne Schwabe (1):
  Remove -no-cpp-precomp flag from Darwin builds

David Sommerseth (3):
  cleanup: Remove RPM openvpn.spec build approach
  docs: Update INSTALL
  build: Package missing mock_msg.h

Gert Doering (5):
  repair windows builds (2.4)
  Increase listen() backlog queue to 32
  Force combinationation of --socks-proxy and --proto UDP to use IPv4.
  Fix IPv6 routes on tap interfaces on OpenSolaris/OpenIndiana
  preparing release v2.4.8 (ChangeLog, version.m4, Changes.rst)

Gisle Vanem (1):
  Wrong FILETYPE in .rc files

Hilko Bengen (1):
  Do not set pkcs11-helper 'safe fork mode'

Ilya Shipitsin (2):
  travis-ci: add "linux-ppc64le" to build matrix, change trusty image to 
xenial, update osx to xcode9.4 and modernize brew management
  travis-ci: fix osx builds

Kyle Evans (1):
  tests/t_lpback.sh: Switch sed(1) to POSIX-compatible regex.

Lev Stipakov (1):
  Fix various compiler warnings

Matthias Andree (1):
  Fix regression, reinstate LibreSSL support.

Michal Soltys (1):
  man: correct the description of --capath and --crl-verify regarding CRLs

Mykola Baibuz (1):
  Fix typo in NTLM proxy debug message

Richard Bonhomme (1):
  Ignore --pull-filter for --mode server

Rosen Penev (1):
  openssl: Fix compilation without deprecated OpenSSL 1.1 APIs

Selva Nair (3):
  Better error message when script fails due to script-security setting
  Correct the return value of cryptoapi RSA signature callbacks
  Handle PSS padding in cryptoapicert

Steffan Karger (1):
  cmocka: use relative paths

Thomas Quinot (1):
  Fix documentation of tls-verify script argument



signature.asc
Description: OpenPGP digital signature
___
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel