Opened 11 years ago
Closed 10 years ago
#287 closed Bug / Defect (fixed)
Missing "build-key-pass.bat" file
| Reported by: | wamiduku | Owned by: | Samuli Seppänen |
|---|---|---|---|
| Priority: | minor | Milestone: | release 2.3.4 |
| Component: | Generic / unclassified | Version: | OpenVPN 2.3.1 (Community Ed) |
| Severity: | Not set (select this one, unless your'e a OpenVPN developer) | Keywords: | |
| Cc: |
Description
The guide on http://openvpn.net/index.php/open-source/documentation/howto.html refers to "build-key-pass.bat". That file does not exist in the OpenVPN distribution (http://swupdate.openvpn.org/community/releases/openvpn-install-2.3.1-I001-x86_64.exe).
Change History (7)
comment:1 Changed 11 years ago by
| Owner: | set to Samuli Seppänen |
|---|---|
| Status: | new → assigned |
comment:2 Changed 11 years ago by
| Milestone: | → release 2.4 |
|---|---|
| Owner: | changed from Samuli Seppänen to Samuli Seppänen |
| Priority: | major → minor |
| Status: | assigned → accepted |
comment:3 Changed 11 years ago by
| Milestone: | release 2.4 → release 2.3.3 |
|---|
comment:4 Changed 11 years ago by
2.3.3 is "soonish". So? Anything to include, or postpone to 2.3.4?
comment:5 Changed 10 years ago by
| Milestone: | release 2.3.3 → release 2.3.4 |
|---|
So, what about this? Close, fix, postpone to 2.3.5?
comment:6 Changed 10 years ago by
This is a trivial fix in the Windows installer, no need to postpone. I'll try to get updated Windows installers (2.3.3-I002) out this week.
comment:7 Changed 10 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | accepted → closed |
This bug has been fixed in openvpn-install-2.3.3-I002-*.exe:
Note: See
TracTickets for help on using
tickets.
This seems to be the case in OpenVPN 2.3.2 too: build-key-pass.bat is not included even if chooses to install easy-rsa in the OpenVPN Windows installer.
However, the easy-rsa 2.x branch does seem to have that file, both for Unix and Windows:
OpenVPN 2.4 installers might include the easy-rsa 3.0 branch, if it's mature enough at that point, so there would be no need to fix this. However, if the fix is trivial and safe, then it would make sense to fix this for an upcoming 2.3.x release. I will look into this.