lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20090720174941.6251bbcf@lxorguk.ukuu.org.uk>
Date:	Mon, 20 Jul 2009 17:49:41 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Rafael Almeida <almeidaraf@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: using ioctl to change the interface's IP

On Mon, 20 Jul 2009 13:39:21 -0300
Rafael Almeida <almeidaraf@...il.com> wrote:

> Hello,
> 
> I was studying ioctl recently and I found out that, in order to change
> the IP of a certain interface, you have to create a dummy socket with
> socket(2) and use the returned file descriptor in the ioctl call. That
> seems strange to me because the IP is not changed only for that
> particular descriptor, but globally. Why wasn't a new system call
> created for handling situations such as that?

You would have to ask the people who invented the Unix interface in
question about thirty years ago 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ