search for: rfc3493

Displaying 3 results from an estimated 3 matches for "rfc3493".

2016 Nov 09
7
[Bug 2636] New: Fix X11 forwarding, when ::1 is not configured
https://bugzilla.mindrot.org/show_bug.cgi?id=2636 Bug ID: 2636 Summary: Fix X11 forwarding, when ::1 is not configured Product: Portable OpenSSH Version: 7.3p1 Hardware: Sparc OS: Solaris Status: NEW Severity: minor Priority: P5 Component: sshd Assignee: unassigned-bugs at
2024 Jul 15
1
Request for a Lockdown option
...uite nice, but in retrospective, it was one |of the truly bad ideas in IPv6 socket API design - and I do applaud the |OpenBSD people for being stubborn here. All the BSDs (started off) use(ing) the KAME stack, which has a nice read in https://github.com/kame/kame/blob/master/IMPLEMENTATION RFC3493: Basic Socket Interface Extensions for IPv6 * IPv4 mapped address (3.7) and special behavior of IPv6 wildcard bind socket (3.8) are, - supported and turned on by default on KAME/FreeBSD[34] and KAME/BSDI4, - supported but turned off by default on KAME/N...
2024 Jul 15
1
Request for a Lockdown option
Hi, On Sun, Jul 14, 2024 at 10:25:46AM +0100, Brian Candler wrote: > On 14/07/2024 03:49, Steffen Nurpmeso wrote: > > I have read > > > > https://datatracker.ietf.org/doc/html/draft-cmetz-v6ops-v4mapped-api-harmful-01 > > > > but as an application developer i find it ugly not to be able to > > "simply do it", and get back a mapped address.