Hi
> There is a way to overflow / filesystem even is quota is enabled.
>
> Just make many hard links (for example /bin/sh) to /tmp/
>
> for ($q=0;$q<10;$q++){
> system ("ln /bin/sh /tmp/ln$q");
> }
>
> Because /tmp directory usually owned by root that why quotas has no effect.
> *Directory*
Are you aware that, due to nature of hardlinks the only extra space is
same that for an empty file? Due to this, how many empty files do you
think it takes to eat the whole space of / ?
I'm I loosing something?
Regards.
En un mensaje anterior, Dmitry Valdov escribió:
> Hi!
>
> There is a way
On Wed, 17 Mar 1999, Jay Tribick wrote:
> Date: Wed, 17 Mar 1999 11:49:32 +
> From: Jay Tribick
> To: Dmitry Valdov
> Cc: freebsd-current@FreeBSD.ORG, freebsd-secur...@freebsd.org
> Subject: Re: disk quota overriding
>
> Hi
>
> > There is a way to overflow
On Wed, 17 Mar 1999, Fernando Schapachnik wrote:
> Date: Wed, 17 Mar 1999 08:50:50 -0300 (GMT)
> From: Fernando Schapachnik
> To: Dmitry Valdov
> Cc: freebsd-current@FreeBSD.ORG, freebsd-secur...@freebsd.org
> Subject: Re: disk quota overriding
>
> Are you aware t
Hi!
I think that there is only one way to fix it - it's to disable making
*hard*links to directory with mode 1777.
On Wed, 17 Mar 1999, Dmitry Valdov wrote:
> Date: Wed, 17 Mar 1999 14:42:46 +0300 (MSK)
> From: Dmitry Valdov
> To: freebsd-current@freebsd.org, freebsd-secur...@freebsd.org
> Sub
> -Original Message-
> From: Dmitry Valdov [SMTP:d...@dv.ru]
> Sent: Wednesday, March 17, 1999 1:37 PM
> To: freebsd-current@freebsd.org; freebsd-secur...@freebsd.org
> Subject: Re: disk quota overriding
>
> Hi!
>
>
> I think that there is only one w
=I think that there is only one way to fix it - it's to disable making
=*hard*links to directory with mode 1777.
Would not it be easier and more practical to make those directories belong
to, say, nobody? And make sure nobody's quota is small enough?
=> Because /tmp directory usually owned by roo
On Wed, 17 Mar 1999, Ladavac Marino wrote:
> Date: Wed, 17 Mar 1999 14:37:32 +0100
> From: Ladavac Marino
> To: 'Dmitry Valdov' , freebsd-current@freebsd.org,
> freebsd-secur...@freebsd.org
> Subject: RE: disk quota overriding
>
> > -Original Message-
In message <97a8ca5bf490d211a94ff6c2e55d097...@s-lmh-wi-900.corpnet.at>, La
davac Marino wrote:
} BTW, has chown been "fixed" to the ludicrous SysV semantics that
} the root and owner can chown a file? If so, the latter has to be
} disabled in presence of quotas on the volume--otherwis
On Wed, 17 Mar 1999, Jon Hamilton wrote:
> } touch big_file
> } chmod 777 big_file
> } chown root:wheel big_file
> } cat /dev/zero >>big_file
> } This joke used to work on HPUX 10.something which kept the
> } owner-may-chown semantics even in presence of quotas. It was not fun
Dmitry Valdov wrote:
> There is a way to overflow / filesystem even is quota is enabled.
>
> Just make many hard links (for example /bin/sh) to /tmp/
>
> for ($q=0;$q<10;$q++){
> system ("ln /bin/sh /tmp/ln$q");
> }
>
> Because /tmp directory usually owned by root that why quotas has no effe
On Wed, 17 Mar 1999, Fernando Schapachnik wrote:
> Are you aware that, due to nature of hardlinks the only extra space is
> same that for an empty file? Due to this, how many empty files do you
> think it takes to eat the whole space of / ?
They take *less* space than an empty file, just the direc
On Wed, 17 Mar 1999, Dmitry Valdov wrote:
> I think that there is only one way to fix it - it's to disable making
> *hard*links to directory with mode 1777.
I'm wondering: are you concerned this is possible, or that you really have
a user doing it? I have kicked users off the system for less when
Dmitry Valdov wrote:
>
> Hi!
>
> I think that there is only one way to fix it - it's to disable making
> *hard*links to directory with mode 1777.
*IF* you are using quotas.
Otherwise, it could break things for people.
--
Daniel C. Sobral(8-DCS)
d...@newsguy.com
d...@fre
Jay Tribick wrote:
>
> > There is a way to overflow / filesystem even is quota is enabled.
> >
> > Just make many hard links (for example /bin/sh) to /tmp/
> >
> > for ($q=0;$q<10;$q++){
> > system ("ln /bin/sh /tmp/ln$q");
> > }
> >
> > Because /tmp directory usually owned by root that why qu
> We all know that there are oodles of security problems associated with
> file giveaways. As I recall, all the texts I have ever read on the subject
> say that unless there is a very good reason to allow giveaways, they
> should be disabled.
You can play games with quotas anyway, because you are
On Wed, 17 Mar 1999, Ladavac Marino wrote:
> chown root:wheel big_file
AFAIK, only root can 'give ownership away' on most modern Unix'.
Later,
-Mike
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the bod
On Wed, 17 Mar 1999, Jon Hamilton wrote:
:Under HP-UX 9.x, the behavior you describe was the default, and it
:was changable by altering a kernel config parameter and relinking the
:kernel. The same tunable is available under 10.x, but I'm less certain
:what the default behavior is there. Whether
On Wed, 17 Mar 1999, James Wyatt wrote:
> Now a small amount of anything multiplied by a large number can amount to
> something. If you have a small root, I can see where you could overwhelm
> it. It will also take longer and longer to ann the links and lookups in
> /tmp will take forever.
On an
> Dmitry Valdov wrote:
> > I think that there is only one way to fix it - it's to disable making
> > *hard*links to directory with mode 1777.
I don't use quotas, and don't know a great deal about how they operate, but I
think there's another disk filling DOS involving hard links lurking which the
Andrew McNaughton wrote:
>
> I don't use quotas, and don't know a great deal about how they operate, but I
> think there's another disk filling DOS involving hard links lurking which the
> above measure would also solve.
>
> If a user starts making hard links to (large and growing) log files, w
On Fri, 19 Mar 1999, Andrew McNaughton wrote:
> > Dmitry Valdov wrote:
> > > I think that there is only one way to fix it - it's to disable making
> > > *hard*links to directory with mode 1777.
>
> I don't use quotas, and don't know a great deal about how they operate,
> but I think there's anoth
>Date: Wed, 17 Mar 1999 20:00:17 -0500 (EST)
>From: "David H. Brierley"
>On any machine which allows general users to log in, I strongly
>recommend making separate file systems for /, /usr, /tmp, and /home,
>
I'll merely point out (since the relevance to -current, per se, is
minimal at this
On Fri, 19 Mar 1999, Andrew McNaughton wrote:
> > Dmitry Valdov wrote:
> > > I think that there is only one way to fix it - it's to disable making
> > > *hard*links to directory with mode 1777.
>
> I don't use quotas, and don't know a great deal about how they
> operate, but I think there's anoth
On Thu, 18 Mar 1999, Robert Watson wrote:
> The linking behavior in conjunction with quotas makes a lot of sense: if a
> user wants to consume someone else's quota, she just hard links to their
> files so they cannot delete them. And if she are mean, she links to them
> in private directories so t
Fernando Schapachnik writes:
> Are you aware that, due to nature of hardlinks the only extra space is
> same that for an empty file? Due to this, how many empty files do you
No, it's actually 128 bytes less.
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-curren
26 matches
Mail list logo
