From: "Paul Rolland" <rol@as2917.net>
To: "'Helge Hafting'" <helgehaf@aitel.hist.no>,
"'Jesse Pollard'" <jesse@cats-chateau.net>
Cc: "'Fredrik Tolf'" <fredrik@dolda2000.cjb.net>,
<linux-kernel@vger.kernel.org>
Subject: Re: PTY DOS vulnerability?
Date: Wed, 2 Jul 2003 08:42:18 +0200 [thread overview]
Message-ID: <028001c34065$15777250$4100a8c0@witbe> (raw)
In-Reply-To: <20030701195323.GA15483@hh.idb.hist.no>
Hello,
> > second, just providing a user limit doesn't prevent a denial of
> > service.. Just have more connections than ptys and you are
> in the same
> > situation.
>
> Isn't this something a improved sshd could do? I.e. if the
> connection using up the last (or one of the last) pty's logs
> in as non-root - just kill it.
Why restricting this to SSH ? I mean, this can occur even if you
are not using SSH.
Some per-user limit seems to be good... but if we do that, what about
also limiting the number of TCP/UDP ports used on a per-user basis ?
In fact, all the resources that are available should be per-user limited
if you want to avoid a single one causing a complete DoS...
- CPU
- Memory
- Network
- Disk
- Pty
- ...
Paul
next prev parent reply other threads:[~2003-07-02 6:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-30 14:18 PTY DOS vulnerability? Fredrik Tolf
2003-06-30 17:55 ` Alan Cox
2003-06-30 21:31 ` Fredrik Tolf
2003-06-30 21:36 ` Alan Cox
2003-07-01 12:15 ` Jesse Pollard
2003-07-01 13:41 ` Timothy Miller
2003-07-01 6:22 ` Oleg Drokin
2003-07-01 11:57 ` Jesse Pollard
2003-07-01 19:53 ` Helge Hafting
2003-07-02 6:42 ` Paul Rolland [this message]
2003-07-03 1:14 ` Jesse Pollard
2003-07-03 1:52 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2003-07-08 23:11 Clayton Weaver
2003-07-09 10:08 ` Svein Ove Aas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='028001c34065$15777250$4100a8c0@witbe' \
--to=rol@as2917.net \
--cc=fredrik@dolda2000.cjb.net \
--cc=helgehaf@aitel.hist.no \
--cc=jesse@cats-chateau.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.