public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Tyler Littlefield" <tyler@tysdomain.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: making secure limitations for non-root users
Date: Fri, 19 Sep 2008 15:28:08 -0600	[thread overview]
Message-ID: <000901c91a9e$9d232190$4200a8c0@tdsportable> (raw)
In-Reply-To: <60EC16C3E6284C1F88ED52622355D343@ZEUS>

hello,
the service is going to be a mud based service, there are many muds out 
there, and people might install patches, etc.

Thanks,
_|_|_|_|_|  _|        _|_|_|_|
    _|      _|_|_|    _|          _|_|_|
    _|      _|    _|  _|_|_|    _|
    _|      _|    _|  _|        _|
    _|      _|    _|  _|_|_|_|    _|_|_|
Visit TDS for quality software and website production
http://tysdomain.com
msn: tyler@tysdomain.com
aim: st8amnd2005
skype: st8amnd127
----- Original Message ----- 
From: "Tom Moore" <tom@tomstroubleshooting.com>
To: "'Speakup is a screen review system for Linux.'" 
<speakup@braille.uwo.ca>
Sent: Friday, September 19, 2008 3:14 PM
Subject: RE: making secure limitations for non-root users


>I don't quite remember the name of a kernel patch that has some things in 
>it
> that will allow you to tighten down your system far better than the normal
> kernel when it comes to limiting users.
>
> First off, you shouldn't allow users to run server type processes unless 
> you
> have too. You should run them, then grant the user access to read log 
> files
> from the processes and such. This is so that you know all services /
> processes that are running on your machine.
>
> Tom
>
> -----Original Message-----
> From: speakup-bounces@braille.uwo.ca 
> [mailto:speakup-bounces@braille.uwo.ca]
> On Behalf Of Tyler Littlefield
> Sent: Thursday, September 18, 2008 2:40 PM
> To: Speakup is a screen review system for Linux.
> Subject: making secure limitations for non-root users
>
> Hello,
> I've got a quick couple of questions:
> First, I'd like to allow users to connect and host a mud on my system.
> I would, however like to limit them in disk space (I can figure that one
> out), in port usage (not sure how to do this one, would like to limit what
> ports they can open), programs they can run, and also what they can view 
> on
> the system.
> Any ideas?
>
>
> Thanks,
> _|_|_|_|_|  _|        _|_|_|_|
>    _|      _|_|_|    _|          _|_|_|
>    _|      _|    _|  _|_|_|    _|
>    _|      _|    _|  _|        _|
>    _|      _|    _|  _|_|_|_|    _|_|_|
> Visit TDS for quality software and website production
> http://tysdomain.com
> msn: tyler@tysdomain.com
> aim: st8amnd2005
> skype: st8amnd127
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> __________ NOD32 3457 (20080919) Information __________
>
> This message was checked by NOD32 antivirus system.
> http://www.eset.com
>
> 


  reply	other threads:[~ UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Tyler Littlefield
 ` Tom Moore
   ` Tyler Littlefield [this message]
 ` Gregory Nowak
   ` Tyler Littlefield
     ` Tom Moore
     ` Jim Kutsch
       ` Tyler Littlefield
 ` Tony Baechler

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='000901c91a9e$9d232190$4200a8c0@tdsportable' \
    --to=tyler@tysdomain.com \
    --cc=speakup@braille.uwo.ca \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).