[21854] in bugtraq
RE: permission probs with Arkeia
daemon@ATHENA.MIT.EDU (Thomas Broniecki)
Wed Jul 25 15:25:38 2001
Reply-To: <tb@joslyn.org>
From: "Thomas Broniecki" <tb@joslyn.org>
To: <bugtraq@securityfocus.com>
Date: Tue, 24 Jul 2001 15:41:05 -0500
Message-ID: <001301c1147f$144bd240$0700a8c0@joslyn.org>
MIME-Version: 1.0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
In-Reply-To: <B782029D.6FB%daniel-wittenberg@uiowa.edu>
Well, I have 644, 755 permissions mainly. Although in the /usr/knox/arkeia
dir there are 13 or so files arkeia_0x.j12 or .lck that have 666
permissions, many haven't been written to in a long while. In
/usr/knox/arkeia/dbase one file o3master.lck.
Check your user management in the gui interface, make sure it is set to
admin. I've also found that if you hand edit your periodic backups, they are
much more prone to strange issues. I recommend using the wizard to configure
your periodic backups. It sound strange, but helped me many times in fits of
frustration.
I have been running Arkeia for some time and completed many upgrades (both
tar and rpm, I use rpm now), so I can't tell you from a clean install
perspective.
I can tell that from my experience Knox is very slow to release patches and
fixes. In the past I've fought backing up NT 4.0 servers while loosing
network connections from clients during backups and only with periodic
backups, not interactive. That was going on for over 1/2 year and repeated
phone calls and e-mails. The NT 4.0 patch just came out!
Good luck.
tb.
> -----Original Message-----
> From: Daniel Wittenberg [mailto:daniel-wittenberg@uiowa.edu]
> Sent: Monday, July 23, 2001 4:35 PM
> To: bugtraq@securityfocus.com
> Subject: Re: permission probs with Arkeia
> Importance: Low
>
>
> I have seen this on at least 3 default-installs for arkeia.
> One person as
> over 1/4 million files, some 0 length, some not. This is on
> RH 6.2, 2.2.17,
> 2.2.19, and 2.2.16. So you have _no_ files with 666? Have
> you done a find
> for files in the /usr/knox with permissions of at least 666?
> nlserved is
> running as root, and root:root is who owns all the files in
> /usr/knox/*
> Knox finally responded to me and told me they saw it as a
> known "oversight"
> and it would be fixed in 5.0, some day, but they don't know
> when that will
> be released. I wouldn't consider that acceptable for a
> security patch.
>
> Dan
>
> =========================
> Daniel Wittenberg
> System Administrator
> University of Iowa
> http://dan.its.uiowa.edu
