Re: ssh: default configuration breaks IPv6

2001-01-02 Thread horape
¡Hola! > > Package: ssh > > Version: 2.2.0p1-1.1 > > Severity: important > > /etc/ssh/sshd.conf has the line: > > ListenAddress 0.0.0.0 > > This avoids ssh listening on IPv6 addresses. If the admin want not to > > restrict > > ssh to IPv4 clients, there should not be any ListenAddress directiv

Re: ssh: default configuration breaks IPv6

2001-01-02 Thread Mark W. Eichin
> gripe against debian packaging system, where are the .orig from? only the > maintainer knows), i've notice that in Jan/2000 the bug i'm reporting was FYI the upstream location of the .orig is *supposed* to be documented in the "copyright" file (debian/copyright in the diffs, /usr/share/doc/PACK

Re: ssh: default configuration breaks IPv6

2001-01-02 Thread Arkadiusz Miskiewicz
On/Dnia Tue, Jan 02, 2001 at 02:03:59PM -0300, [EMAIL PROTECTED] wrote/napisał(a) > > |ListenAddress 0.0.0.0 > > |#ListenAddress :: > > That's not a solution. Because in IPv4 only machines ListenAddress :: doesn't > work. don't put ListenAddress at all. That's right solution. > Horacio J. Peńa

Re: ssh: default configuration breaks IPv6

2001-01-02 Thread horape
Sorry, i believe copyright had just the license, so i never looked there. On Tue, Jan 02, 2001 at 01:35:45PM -0500, Mark W. Eichin wrote: > > > gripe against debian packaging system, where are the .orig from? only the > > maintainer knows), i've notice that in Jan/2000 the bug i'm reporting was >

Re: ssh: default configuration breaks IPv6

2001-01-02 Thread horape
That was what i proposed as fix. But the maintainer didn't like to correct that, because he didn't think breaking IPv6 was a bug. On Tue, Jan 02, 2001 at 06:52:32PM +0100, Arkadiusz Miskiewicz wrote: > On/Dnia Tue, Jan 02, 2001 at 02:03:59PM -0300, [EMAIL PROTECTED] > wrote/napisa?(a) > > > |List

Re: Bug#80503: ssh: default configuration breaks IPv6

2001-01-02 Thread horape
[I'm CC'ing to debian-ipv6 again, sorry for not adding the notice before] ¡Hola! > > ListenAddress shouldn't be set by default. ListenAddress is to be used > > when you want to bind only some addresses. The admin is who should add > > that directive if it's needed. > Well, but debian should provi

Re: Bug#80503: ssh: default configuration breaks IPv6

2001-01-02 Thread Christian Kurz
On 01-01-02 [EMAIL PROTECTED] wrote: > [I'm CC'ing to debian-ipv6 again, sorry for not adding the notice before] Thanks, I keep the Cc now. > > > ListenAddress shouldn't be set by default. ListenAddress is to be used > > > when you want to bind only some addresses. The admin is who should add > >

Re: Bug#80503: ssh: default configuration breaks IPv6

2001-01-02 Thread horape
¡Hola! > > Really, i don't believe that's that way. There is an upstream package, a > > "mediumstream" package and debian package. The "mediumstream" patch > > breaks something. Maybe debian should fix what "mediumstream" has broken. > Well, you must consider that the upstream package is a pure o

Re: Bug#80503: ssh: default configuration breaks IPv6

2001-01-02 Thread James Antill
Christian Kurz <[EMAIL PROTECTED]> writes: > On 01-01-02 [EMAIL PROTECTED] wrote: > > [I'm CC'ing to debian-ipv6 again, sorry for not adding the notice before] > > Thanks, I keep the Cc now. > > > > > ListenAddress shouldn't be set by default. ListenAddress is to be used > > > > when you want to

Re: Bug#80503: ssh: default configuration breaks IPv6

2001-01-02 Thread horape
¡Hola! > > > Openssh provides the admin a good chosen default (that's activated when > > > no ListenAddress directive is present) I don't understand why D.Miller has > > > changed it. > > Well, maybe we will find it out. :) > AFAIK if the DNS ipv6 reverse lookup times out then the entire > rever

Re: ssh: default configuration breaks IPv6

2001-01-02 Thread Mark W. Eichin
umm, I thought I saw somewhere that IPv6 support was a "release goal", or at least a general Debian goal; perhaps they need to be reminded of that...

Re: Bug#80503: ssh: default configuration breaks IPv6

2001-01-02 Thread James Antill
[EMAIL PROTECTED] writes: > ¡Hola! > > > > > Openssh provides the admin a good chosen default (that's activated when > > > > no ListenAddress directive is present) I don't understand why D.Miller > > > > has > > > > changed it. > > > Well, maybe we will find it out. :) > > > AFAIK if the DNS i

Re: Bug#80503: ssh: default configuration breaks IPv6

2001-01-02 Thread Dancer Vesperman
I'm actually starting to feel a trifle guilty about submitting this bug (almost...what...a year ago?) in the first place, considering the wrangle it seems to be causing now. Put simply: At the time, openssh defaulted to working 'out of the box' for ipv6 and ipv4...that is, the configuration wor

IPv6 support in Debian

2001-01-02 Thread Brian May
Hello, I have posted this to both -ipv6 and -devel mailing lists, as I think it is an important issue to Debian as a whole. Is IPv6 a release goal for any future release of Debian ? The reason I ask is because in bug #80503, one of the responses was that IPv6 is not a release goal. However, I c

Re: IPv6 support in Debian

2001-01-02 Thread Dancer Vesperman
I was under the impression that ipv6 was a release goal for woody. Not necessarily a _total_ showstopper, but more on the 'extremely desirable' sort of priority range. Certainly we have things like exim, lftp, ssh that work 'out of the box' with v6...and apps that work with v6 work (equally) fl

Re: IPv6 support in Debian

2001-01-02 Thread Anthony Towns
On Wed, Jan 03, 2001 at 01:30:50PM +1100, Brian May wrote: > Is IPv6 a release goal for any future release of Debian ? Debian doesn't do "release goals" per se. I for one would love to have Debian work out of the box with IPv6, but the only way for that to happen is for someone to actually do the

Re: broken IPv6 code

2001-01-02 Thread Peter Cordes
On Sun, Dec 31, 2000 at 09:18:18PM +0900, YOSHIFUJI Hideaki / [EMAIL PROTECTED](B wrote: > > On USAGI linux24 kernels, you can bind both ipv6 and ipv4 socket to the > same port number by CONFIG_IPV6_DOUBLE_BIND option. > Its hehavior is like KAME's freebsd3's one. For example, > if there's onl