Project

General

Profile

Actions

Bug #1898

closed

Client Export on 2.0 Release creates corrupted Windows installers

Added by Dim Hatz about 13 years ago. Updated about 12 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
OpenVPN
Target version:
-
Start date:
09/22/2011
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0
Affected Architecture:

Description

The first few bytes of the corrupted executable are

.Warning: Missing argument 8 for openvpn_client_export_installer(), called in /usr/local/www/vpn_openvpn_export.php on line 336 and defined in /usr/local/pkg/openvpn-client-export.inc on line 278.MZ..........

This message doesn't appear in the working executable.

Issue is discussed and a possible fix is proposed in http://forum.pfsense.org/index.php/topic,41180.0.html

Actions #1

Updated by Jim Pingle about 13 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

Applied in changeset commit:6be59d2855f40efaae5b2823df8f79a9a5d8a1df.

Actions #2

Updated by Chris Buechler over 12 years ago

  • Status changed from Feedback to Resolved
Actions #3

Updated by c c about 12 years ago

This issue is appearing again on 2.0.1 with the new 0.26 client export. Was working previously on 0.24, uninstalled and updated to 0.26 and all exported executables are corrupted. When run from console, I get "program too big to fit in memory" (Windows XP x86, with either 2.2 or 2.3 beta export).

Actions #4

Updated by c c about 12 years ago

Also, as with the error above, here is the first few line of the generated executable when viewed from notepad:

Warning: rename(openvpnmanager/openvpn-postinstall.exe,openvpn-postinstall.exe): No such file or directory in /usr/local/pkg/openvpn-client-export.inc on line 525 MZ ÿÿ ¸ @ ø º ´ Í!¸LÍ!This program cannot be run in DOS mode.

Actions #5

Updated by Jim Pingle about 12 years ago

Can you reinstall the package and try again? The server that runs files.pfsense.org was switched the other day and I think the one that's active now had an out-of-date version of that archive. I uploaded a fresh copy just now.

Actions #6

Updated by c c about 12 years ago

Update the second, it looks like removing the top two lines of the executable down to "on line 525" uncorrupts the exe.

Actions #7

Updated by c c about 12 years ago

Jim,
Thanks, that did it.

Actions

Also available in: Atom PDF