Mailing List Archive: IPv6 support in OpenBSD CVS

IPv6 support in OpenBSD CVS

Jan 6, 2000, 6:56 PM

Post #1 of 7 (1968 views)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

A couple of days ago, Markus Friedl merged IPv6 support into the
OpenBSD CVS tree. This is a welcome addition, but it presents a few
potential problems for the port.

The main problem is the lack IPv6 support in most Unices. OpenBSD has
it, as do recent versions of NetBSD (presumably), Solaris and Linux
but others may not.

This could be worked around by liberal use of #ifdefs through the
code, but this is something that I am loathe to do. One of my goals
has been to keep the _source_ differences as small as possible between
the OpenBSD source and my own.

For the short term I propose not to merge the IPv6 updates from the
OpenBSD tree, but to continue to pick up other changes.

Comments?

Damien Miller

- --
| "Bombay is 250ms from New York in the new world order" - Alan Cox
| Damien Miller - http://www.mindrot.org/
| Email: djm@mindrot.org (home) -or- djm@ibs.com.au (work)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE4dVXXormJ9RG1dI8RAjb7AKCq3cH3uptW2T3VCzVPBEjbwIMq9ACeN67f
R644l5+zfuU8tPLfLNjMTys=
=CYqP
-----END PGP SIGNATURE-----

Re: IPv6 support in OpenBSD CVS [ In reply to ]

gem at rellim

Jan 6, 2000, 7:16 PM

Post #2 of 7 (1944 views)

Permalink

Yo Damien!

This has been discussed a lot on linux-ipsec. It seems that if the
ipv6 changes are done properly it should be limited to just a few
function call. Of course one guys "proper" is anothers "kludge".

If it can be handled by putting in the stubs for the ipv6 now than
that seems to me to be the way to go. Once the trees diverge it
is always a bummer to get them back together...

So back to you, how much has changed in the openBSD version?

RGDS
GARY

On Fri, 7 Jan 2000, Damien Miller wrote:

> A couple of days ago, Markus Friedl merged IPv6 support into the
> OpenBSD CVS tree. This is a welcome addition, but it presents a few
> potential problems for the port.
[...]
> Comments?

---------------------------------------------------------------------------
Gary E. Miller Rellim 20340 Empire Ave, Suite E-3, Bend, OR 97701
gem@rellim.com Tel:+1(541)382-8588 Fax: +1(541)382-8676

Re: IPv6 support in OpenBSD CVS [ In reply to ]

jmknoble at pobox

Jan 6, 2000, 10:20 PM

Post #3 of 7 (1943 views)

Permalink

På 2000-Jan-07 klokka 13:56:19 +1100 skrivet Damien Miller:

: A couple of days ago, Markus Friedl merged IPv6 support into the
: OpenBSD CVS tree. This is a welcome addition, but it presents a few
: potential problems for the port.

[...]

: This could be worked around by liberal use of #ifdefs through the
: code, but this is something that I am loathe to do. One of my goals
: has been to keep the _source_ differences as small as possible between
: the OpenBSD source and my own.

Damien, is this something that could be worked around using wrapper
functions or macro definitions instead? That's the sort of thing i'd
recommend, if it's possible.

--
jim knoble
jmknoble@pobox.com

Re: IPv6 support in OpenBSD CVS [ In reply to ]

djm at mindrot

Jan 6, 2000, 10:34 PM

Post #4 of 7 (1944 views)

Permalink

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 7 Jan 2000, Jim Knoble wrote:

> : This could be worked around by liberal use of #ifdefs through the
> : code, but this is something that I am loathe to do. One of my goals
> : has been to keep the _source_ differences as small as possible between
> : the OpenBSD source and my own.
>
> Damien, is this something that could be worked around using wrapper
> functions or macro definitions instead? That's the sort of thing i'd
> recommend, if it's possible.

Possibly, this is the route I would prefer to take.

Just to be clear - I _do_ want our port of OpenSSH to be IPv6 capable,
just not for the 1.2.1.0 release. I feel that getting this working
cross-platform would take too long. As always, I would be happy to be
proved wrong :)

Another complication is that I don't have IPv6 up yet to perform
testing, this is still a couple of weekends away for me.

Regards,
Damien

- --
| "Bombay is 250ms from New York in the new world order" - Alan Cox
| Damien Miller - http://www.mindrot.org/
| Email: djm@mindrot.org (home) -or- djm@ibs.com.au (work)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE4dYkDormJ9RG1dI8RAkHDAJ9cqm0QHGtw8vQj2Fp54/Ci+ePJZQCgmtNe
cJliqbzcxd2QkuxN9GAUaPA=
=Rap8
-----END PGP SIGNATURE-----

Re: IPv6 support in OpenBSD CVS [ In reply to ]

mouring at pconline

Jan 7, 2000, 12:06 AM

Post #5 of 7 (1957 views)

Permalink

On Fri, 7 Jan 2000, Damien Miller wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Fri, 7 Jan 2000, Jim Knoble wrote:
>
> > : This could be worked around by liberal use of #ifdefs through the
> > : code, but this is something that I am loathe to do. One of my goals
> > : has been to keep the _source_ differences as small as possible between
> > : the OpenBSD source and my own.
> >
> > Damien, is this something that could be worked around using wrapper
> > functions or macro definitions instead? That's the sort of thing i'd
> > recommend, if it's possible.
>
> Possibly, this is the route I would prefer to take.
>
> Just to be clear - I _do_ want our port of OpenSSH to be IPv6 capable,
> just not for the 1.2.1.0 release. I feel that getting this working
> cross-platform would take too long. As always, I would be happy to be
> proved wrong :)
>

About how much of the code put into our version of the OpenASSH
port migrates back into the main CVS souce tree? If most of
it then at this point it should be easy to provide a patch
set to IPv6 and provide it out to the list for those who
want to attempt the inital port. Even if it's just locating
and building stubs into our current version to support IPv6
down the road.

Re: IPv6 support in OpenBSD CVS [ In reply to ]

djm at mindrot

Jan 7, 2000, 12:13 AM

Post #6 of 7 (1954 views)

Permalink

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, 7 Jan 2000, Ben Lindstrom wrote:

> About how much of the code put into our version of the OpenASSH
> port migrates back into the main CVS souce tree?

Any changes that are not for the sole purposes of portability I submit
back to the OpenBSD folks. There haven't been many, because I have
been keeping changes in seperate files wherever possible.

I don't want something like the forest of #ifdefs that the commercial
ssh-1.2.x was.

> If most of it then at this point it should be easy to provide a
> patch set to IPv6 and provide it out to the list for those who want
> to attempt the inital port. Even if it's just locating and building
> stubs into our current version to support IPv6 down the road.

An excellent idea. I can make this available when 1.2.1.0 is
released. If anyone wants to do it before now, all you need to do
is a checkout of the OpenBSD CVS source and a
"cvs diff -D 20000103" in the directory.

Regards,
Damien

- --
| "Bombay is 250ms from New York in the new world order" - Alan Cox
| Damien Miller - http://www.mindrot.org/
| Email: djm@mindrot.org (home) -or- djm@ibs.com.au (work)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE4daA/ormJ9RG1dI8RAigEAJ0WhtSFMBRVHJgFqAUVNW530MU/hACgrUBl
PTexna/9RZa94JFIKtN/3m4=
=uU7e
-----END PGP SIGNATURE-----

Re: IPv6 support in OpenBSD CVS [ In reply to ]

markus.friedl at informatik

Jan 7, 2000, 2:13 AM

Post #7 of 7 (1960 views)

Permalink

On Fri, Jan 07, 2000 at 02:06:38AM -0600, Ben Lindstrom wrote:
> Even if it's just locating
> and building stubs into our current version to support IPv6
> down the road.

my IPv6 changes consist mostly of a replacement of the calls to
gethostbyname/inet_ntoa with the new getaddrinfo/getnameinfo API
from rfc 2553. sockaddr_in is replaced with sockaddr_storage
or sockaddr.

there is already a getaddrinfo-emulation for 'older' systems
in the original ipv6-patch from
ftp://ftp.kyoto.wide.ad.jp/pub/security/ssh/IPv6/
look for gai.h getaddrinfo.c getnameinfo.c and the configure
changes.

-markus