| Git Clone URL: | https://aur.archlinux.org/nessus-agent.git (read-only, click to copy) |
|---|---|
| Package Base: | nessus-agent |
| Description: | Nessus vulnerability scanner agent |
| Upstream URL: | https://www.tenable.com/downloads/nessus-agents |
| Keywords: | scanner security vulnerability |
| Licenses: | custom |
| Conflicts: | nessus |
| Submitter: | noraj |
| Maintainer: | noraj |
| Last Packager: | noraj |
| Votes: | 6 |
| Popularity: | 0.64 |
| First Submitted: | 2022-03-30 18:50 (UTC) |
| Last Updated: | 2025-01-06 20:13 (UTC) |
Hi Noraj,
So, I think it has something to do with the context package() is running in. All write operations run inside $pkgdir. Only the symlink action is absolute. Not sure, but as far as I remeber there is an other option for doing "post-install" actions. Creating the symlink can not be part of the "package()" build thing, imho. What do you think @noraj?, Rgds, SJ
Hi noraj,
yay f.e. can not create the symlink, if there is no sudo, since you do not run yay as root. But I am wondering, why the rest is still working w/o sudo...
Hi the-sj,
it seems you only added sudo to the script? Why would that be needed? makepkg or any helper already ask you for privilege elevation.
Hi noraj,
Could you please fix the symlink workaround?
diff --git a/PKGBUILD b/PKGBUILD
index 6c99c7e..e761678 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -34,6 +34,6 @@ package() {
install -Dm644 LICENSE "$pkgdir/usr/share/licenses/$pkgname/LICENSE"
# Fix path for /usr/lib/systemd/system/nessusagent.service
- ln -s /opt/$pkgname/ /opt/${_pkgname}
+ sudo ln -s /opt/$pkgname/ /opt/${_pkgname}
}
Rgds, SJ
Hello,
the package needs an update. The following changes in the PKGBUILD need to be applied to install Version 10.2.1:
pkgver=10.2.1
source=("NessusAgent-${pkgver}-fc20.${arch}.rpm::https://www.tenable.com/downloads/api/v1/public/pages/${pkgname}s/downloads/17749/download?i_agree_to_tenable_license_agreement=true"
LICENSE)
b2sums=('0ccf286ed446e5542dbb2cedcf1b5774455e0e1484b50580e1f68876ded6c9e6a437e47b4cc262d286ac1354336064fc4397e81f42e74e1fb041f7e014af319f'
'2c68d4f30686a711fbf5c77b70d9b307f9fdcc8095cea79d8c310edfeea87563d94b9106fce35fc53685e6703afb729b9d81f504a1983c367621605690ea03e1')
Cheers
Hello,
the package needs to be updated. Version 10.1.4 is no longer available for download. The following changes in the PKGBUILD need to be applied to install Version 10.2.0:
pkgver=10.2.0
source=("NessusAgent-${pkgver}-fc20.${arch}.rpm::https://www.tenable.com/downloads/api/v1/public/pages/${pkgname}s/downloads/17239/download?i_agree_to_tenable_license_agreement=true"
LICENSE)
b2sums=('c004e1aad2914b54b8e4961a985bf7398c335869362a524d1e6132e21e73b17cd4b72a486c0e19fda0caf19914db1a4c3634b011cc5a80fd6d73e892f0214d78'
'2c68d4f30686a711fbf5c77b70d9b307f9fdcc8095cea79d8c310edfeea87563d94b9106fce35fc53685e6703afb729b9d81f504a1983c367621605690ea03e1')
Furthermore the systemd Unit is looking at the wrong place for the binary. To able to fix the service startup it could either be done in post_install by symlink /opt/nessus_agent to /opt/nessus-agent or change the path in the nessusagent.service
Experimental package, kindly adapted from the nessus package by neale
Pinned Comments
noraj commented on 2025-01-02 20:09 (UTC)
I'm experimenting dynamic release: dynamically updating $source and $sha256sums as well as using a pkgver(), so that the PKGBUILD will work with nessus-agent newer version without manually updating the unique source link that leads to HTTP 404 error for each new version before. As the crawling script was already written, better use it to automate the process. However, the method used is highly unconventional, so if you experiment any issue or have an idea to suggest cleaner / more elegant solution, please contact me.