Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OpenVPN 2.5: How to add his own config file to the msi file #177

Open
ikreb7 opened this issue Jul 17, 2020 · 1 comment
Open

OpenVPN 2.5: How to add his own config file to the msi file #177

ikreb7 opened this issue Jul 17, 2020 · 1 comment
Labels
msi related to MSI installer question

Comments

@ikreb7
Copy link
Contributor

ikreb7 commented Jul 17, 2020

Hello guys,

I want to add my ovpn config file to the new 2.5 OpenVPN installer. Is there already any documentation on how I could test this?

I opened the msi file (here OpenVPN-2.5-20200304-amd64-signed.msi) with Microsoft Orca. I tried the following:

  1. Add a row to Component Table.
    Component: config.my_config.ovpn
    ComponentId: {12CA....}
    Directory: CONFIG_DIR
    Attributes: 256
    Condition:
    KeyPath: my_config.ovpn

  2. Add a row to Feature Component Table:
    Feature: OpenVPN.Service
    Component: my_config.ovpn

  3. Add a row to File:
    File: config.my_config.ovpn
    Component.config.my_config.ovpn
    FileName: my_config.ovpn|myconfig.ovp
    FileSize: 8192
    Version:
    Language:
    Attributes: 512
    Sequence: 41

  4. Modify LastSequence to 41 at the Media table.

If I start the modified msi file I get a corruption error. Do you have any ideas about what I could forget?

Best regards
Robert

@flichtenheld flichtenheld added question msi related to MSI installer labels Dec 12, 2022
@Phhere
Copy link

Phhere commented Apr 23, 2024

I also would like to see a easy option to add an additional ovpn-config file to the msi installer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
msi related to MSI installer question
Projects
None yet
Development

No branches or pull requests

3 participants