http://rkhunter.sourceforge.net/ Announced that 1.3.0 was released Copying and renaming the 1.2.9 ebuild from portage doesn't work, though. Reproducible: Always
Created attachment 132677 [details] Diff between 1.2.9 ebuild and a working 1.3.0 ebuild Using this it installs on my x86 box but I had to comment out the couple epatch lines from the original since they failed to patch.
rkhunter --versioncheck http://rkhunter.sourceforge.net/rkhunter_latest.dat Rootkit Hunter 1.2.9, copyright Michael Boelen This version: 1.2.9 Latest version: 1.3.2 Update available anyone read this bug-report ? ;) thanks
It seems there is a (temporary?) shortage of developers in forensics herd: both strerror (MIA by feb 23rd) and dragonheart (should return on apr 26th) are actually away. I'm sure that they will take a look at this as soon as they can.
Created attachment 151704 [details] Ebuild for rkhunter 1.3.2 This is an ebuild for 1.3.2 release. Please check. It is tested on my amd64 machine.
Created attachment 151705 [details, diff] tmpdir patch modified for 1.3.2
Created attachment 151706 [details] bash completion for 1.3.2 The options changed a lot since the 1.3 release, so a new bash completion must be made.
Created attachment 151708 [details, diff] ppc64 patch I don't know if this patch is needed anymore...
Hi King Chi, (I hope that's your first name ;) ) thanks for those ebuilds, unfortunately it says: rkhunter --update Invalid INSTALLDIR configuration option - no installation directory specified. when trying to update it via rkhunter --update does an installation directory needs to be specified during that update or during install ? any ideas ? I'll have a look at it later, thanks :)
(In reply to comment #8) > rkhunter --update > Invalid INSTALLDIR configuration option - no installation directory specified. > Are you using the diff by Chris? It has that problem. That's why I'm making my own. The INSTALLDIR option lies in rkunter.conf, which is new in 1.3.2. Have you etc-update'd ? >Hi King Chi, > >(I hope that's your first name ;) ) I'm a Chinese. The first name is "Wong" ;)
>>(I hope that's your first name ;) ) >I'm a Chinese. The first name is "Wong" ;) 對不起 (hope that's the right thing for sorry) ;) so this time I'm doing it right: Hi Wong, >Are you using the diff by Chris? It has that problem. >That's why I'm making my own. >The INSTALLDIR option lies in rkunter.conf, which is new in 1.3.2. >Have you etc-update'd ? seemingly yes, I mistakenly emerged the version from the ycarus-overlay, corrected it and now it's working flawlessly for me :) thanks a lot - you did a great job ! Regards Mat P.S.: what does the forensics herd say about this ? is it ok for inclusion in the portage-tree ?
rkhunter-1.3.2 should be in portage (maybe for testing first). rkhunter-1.3.2 works fine here since a few months (amd64).
All, what is the latest on this? I would also like to see it in portage. :-) Thanks, William
Please make sure you do not introduce security bug 235798 which is present on rkhunter 1.3 and later to the tree. Before bumping, either check the code/changelog or consult with the Security Team.
http://bugs.gentoo.org/show_bug.cgi?id=253720 New version released!
*** Bug 253720 has been marked as a duplicate of this bug. ***
bug #253720 has ebuilds for 1.3.4
Hrm. rkhunter 1.3.4 is in ~x86, but I get the same problem as in bug comment #8. Yep, I did etc-update, but INSTALLDIR isn't in /etc/rkhunter.conf. Thanks.
Created attachment 177564 [details] rkhunter-1.3.4.ebuild (In reply to comment #17) > Hrm. rkhunter 1.3.4 is in ~x86, but I get the same problem as in bug comment > #8. Yep, I did etc-update, but INSTALLDIR isn't in /etc/rkhunter.conf. Thanks. > this version should work, seems that the author has changed the DBDIR value or so.. i've also renamed the tmpdir patch to rkhunter-create-tmpdir.patch and ppc patch to rkhunter-ppc64.patch.
hm, maybe we should talk a bit about the directories.. i think /usr/lib/ isn't the right place for DBDIR or TMPDIR. i'd suggest at least /var/lib, what do you think?
I get the same, what exactly is the solution? Invalid INSTALLDIR configuration option - no installation directory specified.
I have the same error on an amd64 system. Installed today in ~amd64.
(In reply to comment #20) > I get the same, what exactly is the solution? > > Invalid INSTALLDIR configuration option - no installation directory specified. > Same problem on amd64. What's up? What do we need to do?
(In reply to comment #20) > I get the same, what exactly is the solution? > > Invalid INSTALLDIR configuration option - no installation directory specified. > here as well, i've double-checked dispatch-conf... and nothing. there's no man page. What should be changed ? where ? interestingly a google search lead to this page.
Here's the solution: http://bugs.gentoo.org/show_bug.cgi?id=254100
i close this bug because 1.3.4 is now in the tree and there is allready an open bug for problems with this version, bug 254100.
