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
| ||
|
Date: Thu, 01 May 2014 13:38:25 +0200 From: Daniel Borkmann <dborkman@...hat.com> To: netdev@...r.kernel.org Subject: Fwd: [Bug 75221] New: CONFIG_PROC_SYSCTL is required for networking -------- Original Message -------- Subject: [Bug 75221] New: CONFIG_PROC_SYSCTL is required for networking Date: Thu, 01 May 2014 10:17:24 +0000 From: bugzilla-daemon@...zilla.kernel.org To: dborkman@...hat.com https://bugzilla.kernel.org/show_bug.cgi?id=75221 Bug ID: 75221 Summary: CONFIG_PROC_SYSCTL is required for networking Product: Networking Version: 2.5 Kernel Version: 3.14.2 Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Other Assignee: shemminger@...ux-foundation.org Reporter: stefan@...ink.de Regression: No I am in the proces of building an embedded kernel which I wanted to limit in both functionality and memory. For this reason I disabled CONFIG_PROC_SYSCTL. I have figured out the hard way that this functionality implements the successful randomisation of source ports, it might be responsible for the initialisation of net.ipv4.ip_local_port_range. Effectively, booting a kernel with ip=dhcp works. Ping-pong (ICMP) to and from an address works. DNS queries (UDP/53) don't because the source port remains 0, a connection to a typical webserver also seems to result in a no reply situation. -- You are receiving this mail because: You are watching the assignee of the bug. -- 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