search for: 1ecf

...ent from *BSD. > > Stig > _______________________________________________ > openssh-unix-dev at mindrot.org mailing list > http://www.mindrot.org/mailman/listinfo/openssh-unix-dev > > -- Hideaki YOSHIFUJI @ USAGI Project <yoshfuji at linux-ipv6.org> GPG FP: 9022 65EB 1ECF 3AD1 0BDF 80D8 4807 F894 E062 0EEA

hi i have problems with the X11 forwarding, TCP port forwarding works fine: the tcp ports bind to ipv4 and ipv6 localhost, but the X11 port (6010) binds ONLY to the ipv6 localhost, which does not work with the normal ipv4 programs :-( is this a bug, or is this an hidden feature mfg hermann redhat 7.1: openSSH 3.2.2: [mrq1 at xxxx mrq1]$ ssh -X -L 10000:localhost:22 localhost Last login: Thu

Hello! I hope this is the right mailinglist ;) At the moment, I use IPv6 for IRC only, because of too less software wich provides IPv6. It would be very nice if OpenSSH would support IPv6. AFAIK isn't it yet implemented, so it would be nice if someone could implement this. Please send a copy of your answers to openssh-dev at oscarminus.de too, because I'm not subscriped on this

Hi, I've made a patch to support IPv6 ACL. Patch is available at <ftp://ftp.linux-ipv6.org/pub/usagi/misc/rsync-2_5_5-v6auth-20021016.patch.gz> Thanks in advance. -- Hideaki YOSHIFUJI @ USAGI Project <yoshfuji@linux-ipv6.org> GPG FP: 9022 65EB 1ECF 3AD1 0BDF 80D8 4807 F894 E062 0EEA

On Tue, Nov 05, 2002 at 08:37:00AM -0800, Martin Pool wrote: > On 10 Oct 2002, "Green, Paul" <Paul.Green@stratus.com> wrote: > > No new CVS messages have appeared on the rsync-cvs archives since August > > 30th. This seems rather odd-- perhaps a daemon stopped working? If there > > has truly been no activity since that date, I apologize for > >

Hi, I am running sshd (openssh-2.9p2) on a power-pc LynxOS box, and am connecting from a ssh client (openssh-2.9p2) on an x86 Linux box. This works fine for ssh protocol version 1, but am getting the below error for ssh v2: Disconnecting: Bad packet length -857542839. I am also attaching the complete debug traces from sshd & ssh below. I am not sure if this is an "endian" issue.