From owner-freebsd-current Tue May 30 11:36:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from peace.mahoroba.org (peace.calm.imasy.or.jp [202.227.26.34]) by hub.freebsd.org (Postfix) with ESMTP id 2658337B5FB; Tue, 30 May 2000 11:36:33 -0700 (PDT) (envelope-from ume@mahoroba.org) Received: from localhost (IDENT:isz59wVOZJrwawUtINyTmfFJIth34Xrv5MJF00YBzUJR9Hb5MNOaYO+bSMHWlCmA@localhost [::1]) by peace.mahoroba.org (8.10.1/3.7W-peace) with ESMTP id e4UIUOS49066; Wed, 31 May 2000 03:30:25 +0900 (JST) (envelope-from ume@mahoroba.org) Date: Wed, 31 May 2000 03:30:25 +0900 (JST) Message-Id: <200005301830.e4UIUOS49066@peace.mahoroba.org> To: itojun@iijlab.net Cc: Cy.Schubert@uumail.gov.bc.ca, alex@big.endian.de, ume@bisd.hitachi.co.jp, andrews@technologist.com, stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: ftp(1) breakage w/ passive mode? In-Reply-To: <779.959673915@lychee.itojun.org> References: <200005300644.e4U6idT19592@cwsys.cwsent.com> <779.959673915@lychee.itojun.org> X-Mailer: xcite1.20> Mew version 1.94.2 on Emacs 20.6 / Mule 4.0 =?iso-2022-jp?B?KBskQjJWMWMbKEIp?= X-PGP-Public-Key: http://www.imasy.org/~ume/publickey.asc X-PGP-Fingerprint: 6B 0C 53 FC 5D D0 37 91 05 D0 B3 EF 36 9B 6A BC X-URL: http://www.imasy.org/~ume/ X-OS: FreeBSD 5.0-CURRENT Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: Hajimu UMEMOTO (=?ISO-2022-JP?B?GyRCR19LXBsoQiA=?= =?ISO-2022-JP?B?GyRCSCUbKEI=?=) X-Dispatcher: imput version 20000228(IM140) Lines: 30 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> On Tue, 30 May 2000 17:05:15 +0900 >>>>> Jun-ichiro itojun Hagino said: >> ume and I discussed it a little bit, directly. >Tested the patch on a 4.0S system against KRB5 tunnelled through VPN >(pipsecd for now) then NATed (using IP Filter at the remote side) to my >employer's network. Kerberos rlogin and KRB5 telnet now work however >KRB5 ftp still has problems. itojun> I personally believe the patch to getaddrinfo(3) by ume is itojun> not very relevant - the patch may change part of its API, itojun> and it can choke some of the callers. I personally prefer fixing itojun> ftp(1) and other callers if necessary. Yes. the patch convert all IPv4 mapped IPv6 address returned into IPv4 address. If someone announce mapped address using AAAA RR, it also converted. So, caller have no chance to know whether returned address is mapped address or native IPv4 address. However, I think this is rare case in at least now. After correcting getaddrinfo()'s search order, in some case, A RR is accidentaly converted into mapped address without expectation of caller. This may confuse IPv4 people and force inconvenience. I worry about this. Fixing ftp(1) and other caller is also important. But, it is another issue. -- Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan ume@mahoroba.org ume@bisd.hitachi.co.jp ume@FreeBSD.org http://www.imasy.org/~ume/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message