Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong path for curl/wget on FreeBSD 11 #237

Closed
philippetrov opened this issue Jun 16, 2017 · 4 comments
Closed

Wrong path for curl/wget on FreeBSD 11 #237

philippetrov opened this issue Jun 16, 2017 · 4 comments
Assignees
Labels

Comments

@philippetrov
Copy link

philippetrov commented Jun 16, 2017

It should be related to #200

`root@srv2:/ # maldet -u
Linux Malware Detect v1.6.1
(C) 2002-2017, R-fx Networks proj@rfxn.com
(C) 2017, Ryan MacDonald ryan@rfxn.com
This program may be freely redistributed under the terms of the GNU GPL v2

maldet(1303): {sigup} performing signature update check...
maldet(1303): {sigup} could not determine signature version

root@srv2:/ # uname -v
FreeBSD 11.0-RELEASE-p2 #0: Mon Oct 24 06:55:27 UTC 2016 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC`

@philippetrov
Copy link
Author

philippetrov commented Jun 16, 2017

It looks like it's a FreeBSD related issue:
{internal} could not find curl or wget binaries for remote file downloads, fatal error!

The correct paths in freebsd are:
wget: /usr/local/bin/wget curl: /usr/local/bin/curl

@waja
Copy link
Contributor

waja commented Jun 29, 2017

@philippetrov would be cool if you could adjust the subject to something like "Wrong path for curl/wget on FreeBSD 11" or something.

Anyway .. is this just an issue on FreeBSD 11 or also some older versions?

@philippetrov philippetrov changed the title Signature update fails (again) Wrong path for curl/wget on FreeBSD 11 Jul 2, 2017
@philippetrov
Copy link
Author

Renamed. I am pretty sure it's valid for older versions as well.

@rfxn rfxn self-assigned this Jul 14, 2017
@rfxn rfxn added the bug label Jul 14, 2017
rfxn added a commit that referenced this issue Jul 14, 2017
@rfxn
Copy link
Owner

rfxn commented Jul 14, 2017

This has been fixed in the latest commit against 1.6.2 due for release this evening.

Thanks for reporting the issue.

@rfxn rfxn closed this as completed Jul 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants