I've searched bugs.g.o and google in an attempt to find out why ldap is disabled when sftplogging is enabled but have been unable to find the reason. I went ahead and removed the check and found that there were no compile issues and after preliminary testing no runtime issues either - that is, both lpk and sftplogging seem to be working fine. If there is some problem waiting to rear it's head, can it be documented here and referenced from the ebuild please? If it's a past problem that is no longer relevant, can the check be disabled please?
the patches dont apply correctly together this is a non issue with openssh-4.4 (which is in stable now) as upstream integrated sftplogging support so i'm not going to bother working on anything older
As I said, the patches applied fine together (4.3p2-r5) and both seem to be working correctly. But if sftplogging has been included upstream and lpk will be updated for 4.4 or works as-is then I guess no explanation is really necessary. As I would prefer to have both features until 4.4 (with lpk) hits stable, the reasoning why ldap was/is disabled when sftplogging was/is disabled would still be preferable though. IE, I don't care if this is a WONTFIX but I do care that there's no information at all as to why these two patches are presently considered exclusive.
i said 4.4 already is stable ... in older versions they didnt apply together for sure, so that's probably just a hold over into 4.3
Hmm.. my (chosen) upstream rsync server must be lagging again. But ok, that serves well enough for me. :)
Created attachment 102369 [details] openssh-4.4_p1-r7.ebuild w/ sftplogging support openssh-4.4_p1-r7; this new ebuild brings back the much beloved "sftplogging" USE flag to openssh. Applies the "openssh-4.4p1.sftplogging-v1.5.patch" (available on http://sftplogging.sourceforge.net/) which adds more detailed logging of sftp activites, and allows you to control chown, chmod or umask settings in the sshd_config.
http://thread.gmane.org/gmane.linux.gentoo.devel/44269/focus=44318
