On Sat, 2005-01-29 at 15:09 +0100, Stefan Schweizer wrote: > On Sat, 29 Jan 2005 12:29:14 +0100, Johan Andersson <[EMAIL PROTECTED]> wrote: > > Hi, > > > > Is net-fs/openafs ebuids actively maintained? > > The latest ebuild is 1.2.11, from Jun 25 2004. This version contains > > some serious bugs, including a critical DoS. It should be updated to > > 1.2.13. Additionally, the init script and install paths are seriously > > broken in this ebuild. > > > > I have a working openafs ebuild for 1.2.13. I also have ebuilds for the > > afs-krb5 migration kit, needed to use openafs with mit-krb5. > > Can you please have a look at these open bugs? > http://tinyurl.com/6zyhr > > It would be nice if we could get these patches/version > bumps/fixes/security problem together into some patches in one bug, so > that they can be tracked easier. > > Then maybe the maintainer or security people could commit it easier :) > > I suggest you to bug the maintainer in IRC, if he does not react on > the bugs, I am sure there is a reason. > > good luck in getting openafs fixed, > > kind regards, > Stefan > > -- > [email protected] mailing list >
Most of these bugs are caused by the broken init script. Others are solved in new versions of openafs, so jumping to 1.2.13 should solve them. The 1.2.x branch is the stable branch, no additional features are added there, so there should be little need to backport things to 1.2.11-r1 or something. One more problem with the current ebuild is that it installs things into weird locations, for example /usr/afsws. Normally, the server stuff is in /usr/afs, and the client stuff is in /usr/vice. To have things in weird locations just makes it difficult to use the normal openafs how-to's. /Johan Andersson -- [email protected] mailing list
