Searched hist:"82 b276cd2b0bacd58e7c307bf8856925a68c4d14" (Results 1 – 6 of 6) sorted by relevance
| /linux/net/ipv6/ |
| H A D | ping.c | diff 82b276cd2b0bacd58e7c307bf8856925a68c4d14 Mon Jan 20 05:16:39 CET 2014 Hannes Frederic Sowa <hannes@stressinduktion.org> ipv6: protect protocols not handling ipv4 from v4 connection/bind attempts
Some ipv6 protocols cannot handle ipv4 addresses, so we must not allow
connecting and binding to them. sendmsg logic does already check msg->name
for this but must trust already connected sockets which could be set up
for connection to ipv4 address family.
Per-socket flag ipv6only is of no use here, as it is under users control
by setsockopt.
Signed-off-by: Hannes Frederic Sowa <hannes@stressinduktion.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| H A D | datagram.c | diff 82b276cd2b0bacd58e7c307bf8856925a68c4d14 Mon Jan 20 05:16:39 CET 2014 Hannes Frederic Sowa <hannes@stressinduktion.org> ipv6: protect protocols not handling ipv4 from v4 connection/bind attempts
Some ipv6 protocols cannot handle ipv4 addresses, so we must not allow
connecting and binding to them. sendmsg logic does already check msg->name
for this but must trust already connected sockets which could be set up
for connection to ipv4 address family.
Per-socket flag ipv6only is of no use here, as it is under users control
by setsockopt.
Signed-off-by: Hannes Frederic Sowa <hannes@stressinduktion.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| H A D | raw.c | diff 82b276cd2b0bacd58e7c307bf8856925a68c4d14 Mon Jan 20 05:16:39 CET 2014 Hannes Frederic Sowa <hannes@stressinduktion.org> ipv6: protect protocols not handling ipv4 from v4 connection/bind attempts
Some ipv6 protocols cannot handle ipv4 addresses, so we must not allow
connecting and binding to them. sendmsg logic does already check msg->name
for this but must trust already connected sockets which could be set up
for connection to ipv4 address family.
Per-socket flag ipv6only is of no use here, as it is under users control
by setsockopt.
Signed-off-by: Hannes Frederic Sowa <hannes@stressinduktion.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| /linux/net/l2tp/ |
| H A D | l2tp_ip6.c | diff 82b276cd2b0bacd58e7c307bf8856925a68c4d14 Mon Jan 20 05:16:39 CET 2014 Hannes Frederic Sowa <hannes@stressinduktion.org> ipv6: protect protocols not handling ipv4 from v4 connection/bind attempts
Some ipv6 protocols cannot handle ipv4 addresses, so we must not allow
connecting and binding to them. sendmsg logic does already check msg->name
for this but must trust already connected sockets which could be set up
for connection to ipv4 address family.
Per-socket flag ipv6only is of no use here, as it is under users control
by setsockopt.
Signed-off-by: Hannes Frederic Sowa <hannes@stressinduktion.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| /linux/net/ipv4/ |
| H A D | ping.c | diff 82b276cd2b0bacd58e7c307bf8856925a68c4d14 Mon Jan 20 05:16:39 CET 2014 Hannes Frederic Sowa <hannes@stressinduktion.org> ipv6: protect protocols not handling ipv4 from v4 connection/bind attempts
Some ipv6 protocols cannot handle ipv4 addresses, so we must not allow
connecting and binding to them. sendmsg logic does already check msg->name
for this but must trust already connected sockets which could be set up
for connection to ipv4 address family.
Per-socket flag ipv6only is of no use here, as it is under users control
by setsockopt.
Signed-off-by: Hannes Frederic Sowa <hannes@stressinduktion.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| /linux/include/net/ |
| H A D | ipv6.h | diff 82b276cd2b0bacd58e7c307bf8856925a68c4d14 Mon Jan 20 05:16:39 CET 2014 Hannes Frederic Sowa <hannes@stressinduktion.org> ipv6: protect protocols not handling ipv4 from v4 connection/bind attempts
Some ipv6 protocols cannot handle ipv4 addresses, so we must not allow
connecting and binding to them. sendmsg logic does already check msg->name
for this but must trust already connected sockets which could be set up
for connection to ipv4 address family.
Per-socket flag ipv6only is of no use here, as it is under users control
by setsockopt.
Signed-off-by: Hannes Frederic Sowa <hannes@stressinduktion.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
|