GlobalProtect-openconnect VS darling

In order to reach a client's domain for a project, my team needs to use a VPN and the instructions were pretty clear regarding which tool to use - GlobalProtect VPN - so I've installed https://github.com/yuezk/GlobalProtect-openconnect and was able to connect successfully.

Use this one instead https://github.com/yuezk/GlobalProtect-openconnect

Sometimes you may want to use some software in your project, but the maintainer(s) may have some functional affiliation(s) that makes it difficult to use without significant security assessment effort.

Example here: GlobalProtect is VPN software from Palo Alto Networks, but the maintainer of this open source client is based in China. He may be a fine, upstanding person, the code may be pristine, but there's systemic risk that needs to be bought down.

What are your tools of choice to assess something like this?

https://github.com/yuezk/GlobalProtect-openconnect

Ooh yes I recently went through this. This is the one that finally worked: https://github.com/yuezk/GlobalProtect-openconnect

I've seen this on Linux too, specifically with this VPN application https://github.com/yuezk/GlobalProtect-openconnect

Closing it via the "x" will minimize to tray and hide (which is the behavior I want, but an example nonetheless)

I work for a Uni running eduroam. Mine isn't hostile to Linux, but it is definitely a second class citizen. I run Linux where I can. I don't know where you are, but openconnect can probably work for you. Specifically, I use https://github.com/yuezk/GlobalProtect-openconnect/ on top of openconnect for SAML auth. Might be worth the try for you.

I'm not familiar with the service and software can only be downloaded and installed via the customer portal. Would something like GlobalProtect-openconnect or gp-saml-gui suffice?

Solution to the GlobalProtect problem is to install the non-official client https://github.com/yuezk/GlobalProtect-openconnect and follow the fix in issue #142 on the github repo.

There is actually a Wine-like transplier called Darling. The problem is that development is very slow because there is not as much need for MacOS programs on Linux, and there is a huge shortage of volunteers and manpower. And it has been rendered almost obsolete because Apple moved to ARM. Additionally 90% of Apple's API is closed source despite Apple claiming to champion open source.

Unfortunately not. Darling [0] is still at the point that it can only run command line applications. Only the most basic GUI applications are supported. That's still a massive accomplishment that I don't want to diminish, but it's nowhere near the point that WINE was at even quite a long time ago.

[0] https://www.darlinghq.org/

xcodebuild CLI to compile iOS apps without a Mac. Seems possible in theory, although there's an ongoing issue some are seeing apparently: https://github.com/darlinghq/darling/issues/488

I wonder if there's opportunity for overlap with darling (https://www.darlinghq.org/) here, somewhat like using WINE on top of actual Windows.

Hi guys, just wanted to make a quick shoutout to Darling since not a lot people seem to know about it, which is a compatibility layer like Wine for Linux, but it allows for MacOS applications instead of Windows apps to be able to run on Linux!