The latest SpamAssassin release comes with a patch for razor that makes the library work when perl's taint mode (-T) is turned on. The patch is very simple (it just untaints a couple variables), but it is required to avoid a fatal error when an application calls the library with taint mode enabled. I'll attach the razor patch and an ebuild patch to use it.
Created attachment 18004 [details, diff] The razor patch from Mail-SpamAssassin Tweaked by me to remove the prefixed comments and to add the full path of the files we're changing.
Created attachment 18005 [details, diff] Patch for both the razor-2.36.ebuild and the razor-2.20.ebuild. This patch not only adds a src_unpack() section to apply the razor-taint.patch (found in attachment 18004 [details, diff]), but it also makes the minor change of setting "P" instead of "S" (since we need to refer to the modified P value in several places and S depends on P, so it's easier this way). The fix should be applied to both 2.36 and 2.20: cd /usr/portage/net-mail/razor patch -p0 <razor-ebuild.patch patch -p0 razor-2.20.ebuild <razor-ebuild.patch
The attached patch against Razor is an older one. There's now a revisited one in the SpamAssassin 2.60-final tarball.
Created attachment 18269 [details, diff] The untaint patch from Mail-SpamAssassin 2.60 (final) Updated the patch to the version from Mail-SpamAssassin's final 2.60 release. Also updated the line numbers to match the 2.36 release's files.
One extra note: if the untaint patch is used with the 2.20 release, it will generate some *.orig files (since the line numbers aren't quite the same) and they will be installed into the perl library dir. Thus, the 2.20 ebuild would need the patch command to be tweaked to add the --no-backup-if-mismatch option to avoid this.
2.36 is patched in -r1.
guess rac forgot to close out this bug ;)
