search

OrchidTechnologies / orchid

Orchid: VPN, Personal Firewall
https://www.orchid.com/
GNU Affero General Public License v3.0
655 stars 102 forks source link

Segfault with single OpenVPN hop #30

Closed brandoncurtis closed 4 years ago

brandoncurtis commented 4 years ago

Describe the bug Orchid VPN crashes silently when using a single OpenVPN hop. The app says that the VPN is active, but the key icon disappears from the system bar and no traffic shows up in the traffic tab.

To Reproduce Steps to reproduce the behavior:

  1. Remove all existing hops
  2. Configure a known-good OpenVPN hop
  3. Activate the VPN
  4. The key icon will appear in the system bar, and after a few seconds it will disappear
  5. Do this repeatedly to receive an Android system message that "Orchid keeps stopping" and an invitation to submit a bug report

Expected behavior A single hop with a known-good OpenVPN connection should work fine. (connections work fine in the Android OpenVPN Connect app)

Screenshots N/A

Device information:

Additional context N/A

saurik commented 4 years ago

Did you happen to submit that bug report? Maybe can you provide the crashlog? I'm just fascinated by this being a segfault... like if this were an assertion/exception I'd just say "oh, there's probably some awkward thing where OpenVPN3 requires a subtle tweak to your OVPN file vs. the OpenVPN2 which that Connect app is likely using", but an honest-to-goodness segmentation fault indicates something much more sinister that I'll need more context to debug. Maybe you can at least tell me what OpenVPN service provider you are using?

saurik commented 4 years ago

This seems to be an app front-end configuration file sterilization bug; if you replace all the newlines in your OpenVPN configuration file with "\n" and enter it as a single line it works ;P. This will be fixed soon, at which point I will close this issue.

saurik commented 4 years ago

This issue was fixed at some point and at some point sufficiently later than that to be surprising--but not so long for it to be ludicrous--this fix was shipped. If this is still not working for you, please re-open this issue ;P.