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>] [day] [month] [year] [list]
Message-ID: <46995671.5080503@simon.arlott.org.uk>
Date:	Sun, 15 Jul 2007 00:04:17 +0100
From:	Simon Arlott <simon@...e.lp0.eu>
To:	netdev@...r.kernel.org
Subject: open() on sockets (sock_no_open)

There are sockets in /proc/<pid>/fd/, but they can't be opened because
of this function:

/*
 *  In theory you can't get an open on this inode, but /proc provides
 *  a back door. Remember to keep it shut otherwise you'll let the
 *  creepy crawlies in.
 */
static int sock_no_open(struct inode *irrelevant, struct file *dontcare)


How would I make it possible to open existing sockets?

It's possible to duplicate access to the same socket using fork(), but I
just seem to be creating a mess when I try to make open() work because
it breaks after calling socket_close... is there a way to do this so it
works properly?

-- 
Simon Arlott
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ