Package Details: globalprotect-openconnect-git 2.1.4-2

Git Clone URL: https://aur.archlinux.org/globalprotect-openconnect-git.git (read-only, click to copy)
Package Base: globalprotect-openconnect-git
Description: A GUI for GlobalProtect VPN, based on OpenConnect, supports the SSO authentication method.
Upstream URL: https://github.com/yuezk/GlobalProtect-openconnect
Keywords: globalprotect openconnect saml vpn
Licenses: GPL3
Conflicts: globalprotect-openconnect
Provides: globalprotect-openconnect, gpauth, gpclient, gpgui, gpservice
Submitter: yuezk
Maintainer: yuezk
Last Packager: yuezk
Votes: 4
Popularity: 0.73
First Submitted: 2021-10-16 07:43 (UTC)
Last Updated: 2024-04-11 12:07 (UTC)

Latest Comments

1 2 Next › Last »

yuezk commented on 2024-02-07 02:52 (UTC)

GUI - costs money, stuck using CLI TLS errors on real, valid certificates

@howardtopher

The CLI supports the --ignore-tls-errors option to ignore all tls errors. Have you tried it?

Anyway, you can install the old version using globalprotect-openconnect package.

howardtopher commented on 2024-02-07 01:53 (UTC)

This package has been bumped up to version 2.0.0. Is it possible to go back to the previous version or create a different AUR package for the older version? It's a real shame what's happened with this package.

GUI - costs money, stuck using CLI TLS errors on real, valid certificates

The new version sucks but at this point I'm stuck using it because I can't log into work without it.

Eothred commented on 2023-12-08 11:48 (UTC)

@archisman Add #branch=project_branch to the end of the source url (similar to what is right now done with commit hash), see https://wiki.archlinux.org/title/VCS_package_guidelines

On that note, may I propose to add pkgver() function since this is a git package, something along the lines of

pkgver() {
    cd GlobalProtect-openconnect
    git describe --long --tags | sed 's/^v//;s/-/.r/;s/-/./'
}

This will e.g. right now set the pkgver to 1.4.9.r7.gedc13ed. I see you have locked this package to a specific commit at the moment, I guess maybe there was a reason for that and this is why you do not want this right now.

archisman commented on 2023-08-07 13:32 (UTC)

The new refactor branch written in Rust is going to replace the master branch soon https://github.com/yuezk/GlobalProtect-openconnect/tree/refactor Can someone tell me how to edit the PKGBUILD to use that?

marrs commented on 2023-07-14 10:00 (UTC) (edited on 2023-07-14 13:02 (UTC) by marrs)

I tried logging onto my VPN today and found that the client would not open a login window. Instead it just hangs at "connecting...". I had to manually log in using openconnect --protocol=gp https://myvpn.example.com. After following the login procedure in my browser, gpclient would successfully connect when I ran it a second time.

Edit: I think this is likely an issue with the VPN's TLS certificate. I think it is related to the issue reported here: https://github.com/yuezk/GlobalProtect-openconnect/issues/226

Update: Issue resolved by itself.

menny commented on 2023-01-09 14:07 (UTC)

indeed! Thank you!

yuezk commented on 2023-01-08 12:28 (UTC) (edited on 2023-01-08 12:28 (UTC) by yuezk)

@menny It should be fixed now.

menny commented on 2023-01-05 14:33 (UTC) (edited on 2023-01-05 14:35 (UTC) by menny)

I get an error when updating to the latest yay package:

CMake Error at /usr/lib/cmake/Qt5/Qt5Config.cmake:28 (find_package):
  Could not find a package configuration file provided by "Qt5LinguistTools"
  with any of the following names:

    Qt5LinguistToolsConfig.cmake
    qt5linguisttools-config.cmake

  Add the installation prefix of "Qt5LinguistTools" to CMAKE_PREFIX_PATH or
  set "Qt5LinguistTools_DIR" to a directory containing one of the above
  files.  If "Qt5LinguistTools" provides a separate development package or
  SDK, be sure it has been installed.
Call Stack (most recent call first):
  CMakeLists.txt:78 (find_package)

yuezk commented on 2022-05-08 13:58 (UTC)

@kyechou Problem resolved.

kyechou commented on 2022-03-04 14:56 (UTC)

Hi @yuezk, yes, exactly! Thanks @zayatura for the explanation.