All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Restrict access to certain ips.
Date: Thu, 01 May 2003 03:24:11 +0000	[thread overview]
Message-ID: <marc-lartc-105175953809860@msgid-missing> (raw)


Thilo,

Did you ever receive an answer on this question?

Also--a question of clarification....

  Do you mean that only UID 1001 should be allowed to bind to 192.168.1.11
  for outbound packets?

If so, then, why not try this:

  iptables -I OUTPUT -o $OUTDEV -m owner ! --uid-owner 1001 -j DROP

Is that what you wished to accomplish?

-Martin

 : Hello,
 :
 : I have a machine with several ips. My goal is to only allow access to one ip
 : for a certain user. for example 192.168.1.11 may only be used by UID 1001
 :
 : I have found in the man page for bind following errno numeric:
 : > EACCES The address is protected, and the user is not the super-user.
 :
 : Is it possible to restrict access to certain ips to certain uids?
 :
 :  - Thilo Schulz
 : _______________________________________________
 : LARTC mailing list / LARTC@mailman.ds9a.nl
 : http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
 :

-- 
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2003-05-01  3:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-01  3:24 Martin A. Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-13 20:20 [LARTC] Restrict access to certain ips Thilo Schulz

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=marc-lartc-105175953809860@msgid-missing \
    --to=mabrown-lartc@securepipe.com \
    --cc=lartc@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.