Wed, 4 Apr 2012 18:24:07 +0100
On 4 April 2012 18:08, Russ Allbery <email@example.com> wrote:
> Stephen Quinney <firstname.lastname@example.org> writes:
>> I've seen a few discussions on this mailing list about using mod_waklog,
>> particularly regarding x86_64. I've recently had the chance to spend
>> some time looking at it and now have it working on RHEL6 for both i386
>> and x86_64.
>> I took the latest code from the git repository (details at
>> http://www.modwaklog.org/download.php) and started by applying the 3
>> patches from http://userpages.umbc.edu/~aaronk/waklog/ which have been
>> mentioned on this list before.
>> To get it working with Kerberos 1.8 and newer without globally setting
>> the allow_weak_crypto option to true I had to add a call to
>> krb5_allow_weak_crypto() in mod_waklog.c, I think this could be done
>> better as the code now won't work on machines with older versions of
>> I also had to modify the set of libraries which are linked against so
>> that only libafsrpc and libafsauthent are used.
> This all sort of implies that modwaklog may be orphaned. =A0Has anyone be=
> able to get in touch with the current maintainers? =A0Are they accepting =
> people on the maintenance team? =A0Are they looking for someone else to p=
> up maintenance?
> The last change pushed to their Git repository was two and a half years
> Every Apache module requires modifications, in some cases extensive, for
> Apache 2.4, which has just recently been released.
Certainly the impression I have got is that everyone has their own
collections of patches and there isn't really anything happening
"upstream". It's on sourceforge so I guess it should be easy enough
for the maintainers to open up write access to others. I'll send in my
patches and see if they are interested in opening up write access to