Date: Thu, 25 Nov 1999 22:44:31 -0500 (EST) From: Spidey <beaupran@iro.umontreal.ca> To: relapz <relapz@purefusion.com> Cc: freebsd-security@FreeBSD.ORG Subject: Re: Fwd: ssh-1.2.27 remote buffer overflow - exploitable (VD#7) Message-ID: <14398.543.747440.547183@anarcat.dyndns.org> References: <199911160357.UAA01885@harmony.village.org> <Pine.BSF.4.10.9911161121130.676-100000@frosty.purefusion.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--- Big Brother told relapz to write, at 11:27 of November 16: > seeing as we are on the OpenSSH/ssh front, i've decided to ditch ssh in > favour of OpenSSH. > > However, I seem to be getting some odd errors when someone connects to the > new OpenSSH server daemon: > > Nov 16 11:18:35 <4.4> frosty sshd[1146]: set class 'default' resource > limit datasize: Operation not permitted > Nov 16 11:18:35 <4.4> frosty sshd[1146]: set class 'default' resource > limit stacksize: Operation not permitted > Nov 16 11:18:35 <4.4> frosty sshd[1146]: set class 'default' resource > limit maxproc: Operation not permitted > Nov 16 11:18:35 <4.4> frosty sshd[1146]: set class 'default' resource > limit openfiles: Operation not permitted > > Can someone shed some light on what exactly causes these? Should i be > worried about a misconfig or is this normal. thanx, I found out that putting 'UseLogin yes' in the config file solved the problem. Does anybody knows the implications of using that options? Thanks the AnarCat -- Si l'image donne l'illusion de savoir C'est que l'adage pretend que pour croire, L'important ne serait que de voir Lofofora To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14398.543.747440.547183>