caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Nicolas George <nicolas.george@ens.fr>
To: caml-list@inria.fr
Cc: tom hawkins <tomahawkins@yahoo.com>
Subject: Re: [Caml-list] Setting unix socket options.
Date: Tue, 14 Jan 2003 00:12:43 +0100	[thread overview]
Message-ID: <20030113231243.GA22200@clipper.ens.fr> (raw)
In-Reply-To: <20030113225141.23405.qmail@web20010.mail.yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]

Le quartidi 24 nivôse, an CCXI, tom hawkins a écrit :
> I just started playing with sockets through Ocaml, but I'm 
> having difficultly setting options on a socket.
> I can get the options just fine (getsockopt), but
> when I try to set an option I get "permission denied".
> 
> What am I doing wrong?

You are doing wrong that you are trying to set an option that obviously
requires superuser privileges. If you are using Linux, by exemple, you
can see in the source code:

                case SO_DEBUG:  
                        if(val && !capable(CAP_NET_ADMIN))
                        {
                                ret = -EACCES;
                        }
                        else
                                sk->debug=valbool;
                        break;

and the manpage says:

       SO_DEBUG
              Enable  socket  debugging.  Only  allowed for processes with the
              CAP_NET_ADMIN capability or an effective user id of 0.

In fact, _you_ are not doing anything wrong: the Linux kernel is wrong,
because the Single Unix Specification does not mention EACCES as a
permitted exit value for setsockopt, nor the fact that SO_DEBUG should
be restricted.

[-- Attachment #2: Type: application/pgp-signature, Size: 185 bytes --]

      reply	other threads:[~2003-01-13 23:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-13 22:51 tom hawkins
2003-01-13 23:12 ` Nicolas George [this message]

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=20030113231243.GA22200@clipper.ens.fr \
    --to=nicolas.george@ens.fr \
    --cc=caml-list@inria.fr \
    --cc=tomahawkins@yahoo.com \
    /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 NNTP newsgroup(s).