Description: * Sun Jan 2 2005 Greg Houlette - 0:1.1.9-0.fdr.1 - New package version release - Added the --run-application-check command line option to listing in command help - Replaced 'Here' Doc editing of rkhunter.conf file with in-place Perl edit - tweaked rpmbuild -bb Autoclean From upstream release CHANGELOG: * 1.1.9 (28/12/2004) New: - Added RH-Sharpe's rootkit (rootkit) - Added SHV5 rootkit (rootkit) - Added special test for tripwire - Added support for metalog (syslog daemon) - Added support for ALTLinux 2.2 and 2.4 - Added support for CentOS 3.3 - Added support for Gentoo 1.6 - Added support for FreeBSD 4.10 (alpha platform) - Added support for SuSE SLES8. Thanks to Mario Lenz - Added support for SuSE 9.2 (i586) - Added support for Fedora Core 3 - Added support for Red Hat Enterprise Linux ES/WS release 4 - Added hashes for Fedora Core 3. Thanks to Steph - Official port is now available for ALTLinux - Change text when an old software package has been found. This will happen with backporting operating systems (Red Hat, Fedora etc) Changes: - Improved logging for lsof test - Updated hashes for Fedora Core 1 - Updated hashes for Debian woody - Updated hashes for Red Hat Enterprise Linux ES/WS release 3 - Updated hashes for Slackware 9 - Updated hashes for Slackware 10 - Updated hashes for SuSE 9.1 - Updated wishlist/todo, updated readme and manpage. - Code cleanup (added more remarks, cleanup of old/buggy things).. - Improved logging Bugfixes: - Changed binary search path due typo. Thanks to Bertrand
Source RPM signed digests: http://download.tekarmory.com/fedora/rkhunter-1.1.9-0.fdr.1.src.md5
ERROR 403: Forbidden.
> ERROR 403: Forbidden. O.K... My fubar... New site... etc., etc. I'll put a page there so the server knows what to do...
Well... that was interesting... My hosting provider and I have been in a cage match about who should fix what. First I had to deal with the stupid 32 character filename limit. Geez! Even Windoze95 had support for long file names... Now the issue is the 403 error from serving up *_ANY_* non-graphical binary file via HTTP... (I've told them it is a server configuration issue, they told me that I should just serve them from the FTP side) I pointed out to them that I could download the RPMs via HTTP from the management console (from which I uploaded them as well). Their response? "We will look into this and reply you soon" In the meantime, I've changed the URL here to a TinyURLized version. (Hope you client can handle a HTTP->FTP redirect...)
Source RPM signed digests: http://tinyurl.com/4w4re/public/fedora/rkhunter-1.1.9-0.fdr.1.src.md5
Imported into CVS as rkhunter-1.1.9-1 because the 0.fdr prefix is no longer used. Moved the "Packager" entry into the %changelog where it belongs.
Seems reasonable. Pulled down the mod'ed .spec file and rebuilt both source and binary RPMs to verify release change did not break anything. (I didn't really expect it would) Uploaded new files to server. Source RPM signed digests: http://tinyurl.com/4w4re/public/fedora/rkhunter-1.1.9-1.src.md5 What's next? Does it get build automatically from CVS?
No automated builds yet, since this is pre-Extras. Seth Vidal triggers FC3 builds when you post to fedora-extras-list.
Do we have a template for fedora-extras-list announcements? Do we just use fedora-pkgannfmt? (BTW, my hosting provider got 'pinned to the mat' this afternoon. "We were denying access to a specific file type but instead we were stopping any file ending with pm.") ERROR 403: Forbidden. FIXED
There's an automated "Recent Packages" news feed: http://fedoraproject.org/infofeed/inputs/fc3-extras.xml fedora-extras-list is for general discussion. fedora-extras-announce-list is not in use yet. Haven't seen a single package announcement there.