On Tue, 20 Nov 2007, Marcus Meissner wrote:-
<snip>
The 1.3.0 one does not know either unless I patch another stupid 1 liner into
its config file to detect 10.3.
If you're referring to the os.dat file, it's unused by anything other
than check_update.sh.
I've been running 1.3.0, from the CVS release in July when I added bug
#1713985 to the rkhunter/sourceforge bugzilla[0], and it's been fine on
the various systems I've used it on[1][2].
One thing I did need to do after installation, and probably something
that should have been added to the %post of the spec is to call
"rkhunter --propupd" to create the rkhunter.dat database.
[0]
http://sourceforge.net/tracker/index.php?func=detail&aid=1713985&gro
up_id=155034&atid=794187>
[1] 10.0 x86_64, where I initially found the script path bug, 10.1
x86_64, and more recently 10.3PPC.
[2] I've just built the release version from sourceforge.net and
installed it upon a 10.3 x86 system and there's no complaints about
unknown OS versions there either.
Regards,
David Bolt
--
Team Acorn: http://www.distributed.net/ OGR-P2 @ ~100Mnodes RC5-72 @ ~15Mkeys
| SUSE 10.1 32bit | openSUSE 10.2 32bit | openSUSE 10.3 32bit
SUSE 10.0 64bit | SUSE 10.1 64bit | openSUSE 10.2 64bit |
RISC OS 3.11 | RISC OS 3.6 | TOS 4.02 | openSUSE 10.3 PPC
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org
For additional commands, e-mail: opensuse-factory+help@opensuse.org