Package Details: perimeter81 8.1.0.778-1

Git Clone URL: https://aur.archlinux.org/perimeter81.git (read-only, click to copy)
Package Base: perimeter81
Description: Perimeter81 agent application
Upstream URL: https://support.perimeter81.com/docs/downloading-the-agent
Licenses: custom:LICENSE
Submitter: mikeroll
Maintainer: ttrmw
Last Packager: ttrmw
Votes: 3
Popularity: 0.000490
First Submitted: 2021-10-01 15:02 (UTC)
Last Updated: 2024-02-19 06:39 (UTC)

Latest Comments

« First ‹ Previous 1 2

asimag commented on 2022-08-08 15:35 (UTC)

Thanks @mikroll I started the service:

sudo systemctl restart perimeter81helper.service But now the problem is after I disconnect from VPN. My system internet does not work. I had to restart Network Manager udo systemctl restart NetworkManager I had also updated the version to 8.0.3.654 inside build files and removed md5sums. As perimeter does not allow you to connect unless you update it. Very annoying. But my company uses it.

mikeroll commented on 2022-07-16 21:56 (UTC) (edited on 2022-07-16 21:56 (UTC) by mikeroll)

Updated to the latest version and fixed the md5sums.

@ufo_driver I haven't yet connected any specific problems to the use of debs, but if you're sure your implementation with rpms works better I'd be happy to transfer the package.

@asimag Sounds like you might have forgotten to start the perimeter81helper service?

ufo_driver commented on 2022-07-05 12:42 (UTC)

I think the problems we have is due to using deb package which may be built against old glibc etc.

I tried to use Fedora RPMs in my PKGBUILD instead and it worked without any problems I had with debs. But now I have problem with package versioning - I simply don't know how to extract version string from RPM package.

asimag commented on 2022-07-05 09:04 (UTC) (edited on 2022-07-05 09:06 (UTC) by asimag)

I have added third 'SKIP' in md5 section in build package files. Now it compiles and installs. But it still does not run. It gives me following error: error: Error: connect ENOENT /tmp/app.p81helper at PipeConnectWrap.afterConnect [as oncomplete] (net.js:1054:14) { errno: 'ENOENT', code: 'ENOENT', syscall: 'connect', address: '/tmp/app.p81helper' } connection closed p81helper /tmp/app.p81helper Infinity tries remaining of Infinity disconnected from p81helper

ufo_driver commented on 2022-06-11 18:18 (UTC) (edited on 2022-06-11 18:18 (UTC) by ufo_driver)

Another small issue ==> ERROR: Integrity checks (md5) differ in size from the source array.

LICENSE needs it's own SKIP.

mikeroll commented on 2022-05-27 15:53 (UTC)

Thanks @ufo_driver, added the dependency.

No crashes on launch for me, but I run it under XWayland on sway.

ufo_driver commented on 2022-05-25 11:32 (UTC) (edited on 2022-05-25 11:34 (UTC) by ufo_driver)

Also new perimeter requires netcat to work. Tested both gnu-netcat and openbsd-netcat to work successfully. So adding netcat as a dependency should be fine.

ufo_driver commented on 2022-05-25 10:58 (UTC)

Version 8.0.2.592-1 crashes on launch for me, saying something compositor crashing too often. Adding --disable-gpu --in-process-gpu fixes that.

mikeroll commented on 2022-04-29 09:25 (UTC) (edited on 2022-04-29 09:26 (UTC) by mikeroll)

Thanks @jiko!

I suppose I should have indicated that this is a hacky initial packaging attempt to bring the app to a working state without having to wrangle a deb/rpm manually. I made sure to not include the questionable commands the upstream packages run in postinstall scripts (those are pretty frivolous with your system), but I didn't go as far as preventing the app from misbehaving during runtime.

I might have a look later but can't promise. Feel free to send a pkgbuild patch if you do instead.

jiko commented on 2022-04-29 08:41 (UTC)

At some point this application installs a certificate at the root level as a trusted X.509 anchor. That file is not part of the manifest and is not deleted upon removal.

ls -l /usr/local/share/ca-certificates/perimeter81/perimeter81.crt
.rw-r--r-- 15 root root 10 Jan 09:18 /usr/local/share/ca-certificates/perimeter81/perimeter81.crt

You should know this before installing the package as there are implications.

The AUR should also have an extra step to remove this file, at least on uninstall.