linux-kernel - Re: Issues with knfsd + solaris clients

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20070328172310.GC21221@fieldses.org>
Date:	Wed, 28 Mar 2007 13:23:10 -0400
From:	"J. Bruce Fields" <bfields@...ldses.org>
To:	Phy Prabab <phyprabab@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Issues with knfsd + solaris clients

On Tue, Mar 27, 2007 at 01:34:21PM -0700, Phy Prabab wrote:
> Here is a little bit more information on my issue with slowlaris and

Could you just use their name?  It's a little distracting otherwise.

> knfs 2.6.21-rc4/5 (actually appears in 2.4.20.x).  Running this from
> the client (x.org source code):
> >ls -l xc/lib/Xmu/Xct.h
> -rw-rw-r-- 1 phy bdf 0 2006-01-09 06:59 xc/lib/Xmu/Xct.h
> >file xc/lib/Xmu/Xct.h
> xc/lib/Xmu/Xct.h:       cannot read: Is a directory
> >rm -rf xc/lib/Xmu/Xct.h
> rm: cannot remove `xc/lib/Xmu/Xct.h': Not owner
> >uname -a
> SunOS mm3 5.10 Generic_118855-14 i86pc i386 i86pc Solaris
> >chmod 777 xc/lib/Xmu/Xct.h
> >rm -rf xc/lib/Xmu/Xct.h
> rm: cannot remove `xc/lib/Xmu/Xct.h': Not owner
> >
> 
> I would think the file would not be directory and if I tried to remove
> it, I should be able as owner and permissions are correct.  This is on
> a solaris 10 on intel, but I also see this problem on solaris 8, 9 and
> 10 on sparc.  Again, AIX5303 and 04 and all linux clients (2.4.x,
> 2.6.x) seem to be fine.

Would it be possible to get a trace showing what the rpc traffic during
the above test?  You could run something like

	tcpdump -s0 -wTMP host my-client.example.com

and then post a copy of TMP someplace.  Or look at it yourself in
wireshark--what you're looking for is how the server replied to the
rpc's generated by the commands above, and whether the server's replies
were consistent.

--b.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/