First off some background. I have a central server with NFS running, which makes user home directories among other directories available to client machines via Automount + NFS. Logwatch is running on the server and I get mailed reports daily. In the Logwatch reports, I will see the following every once in a while: --------------------- Mountd Begin ------------------------ Attemts to mount nonexisting files or directories: /home/rodo:260 Time(s) /home/sragavan:10 Time(s) ---------------------- Mountd End ------------------------- When I first saw this I thought someone had either broken into the server or was attempting to but the logs, chkrootkit, qcheck and qfile did not support this. I also recursively searched through /usr/portage to possibly identify an ebuild that referenced those two home directories but did not find any. At this point, I just discounted the mount attempts as some anomaly in Gentoo. ----- After seeing the mount errors again today, I decided to search Google for those two home directories and the common denominator between the two is paths with 'ooo-build' in them. I unpacked the latest Openoffice sources (2.3.1) and did a recursive grep on then for rodo and sragavan and found several matching files. While I now know where the mount errors are coming from, I believe this needs to be fixed. While this bug report can have a severity of 'minor' because *we know* the source of the errors, I believe this is a security related matter to Gentoo users that care about the security of their systems and this bug report should have a severity of 'major' or 'critical' because false positives are just as important as true positives.
Please submit such stuff upstream, we won't fix this.
So what your saying is you will not work with upstream or, for that matter, even report it upstream like other developers do?
(In reply to comment #2) > So what your saying is you will not work with upstream or, for that matter, > even report it upstream like other developers do? > This seems to have gone the wrong way here, sorry. Also sorry, that I respond that late... Sure we work with upstream, and also sure Anyway: This sounds like a simple oversight by some Novell-developers (rodo an sragavan are working for Novell on OOo). Please report this upstream, also give them the ooo-build-release-version you built your OOo with (this info is found in the about-screen) thanks for reporting this
Advice given, no reaction, bug closed
