similar to: [Bug 1941] New: ssh -6 prevents ipv4 forwarding

https://bugzilla.mindrot.org/show_bug.cgi?id=2029 Priority: P5 Bug ID: 2029 Assignee: unassigned-bugs at mindrot.org Summary: ssh connection failure error message confusing when talking to dual IPv4/6 host Severity: normal Classification: Unclassified OS: Linux Reporter: sklist at kitterman.com

http://bugzilla.mindrot.org/show_bug.cgi?id=1247 Summary: ssh-agent prevents use of group permissions to control access to agent socket Product: Portable OpenSSH Version: 4.4p1 Platform: ix86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: ssh-agent

http://bugzilla.mindrot.org/show_bug.cgi?id=1040 Summary: SSH only believes 127.0.0.1 is IPV4 localhost, not 127/8 Product: Portable OpenSSH Version: 3.8.1p1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: bitbucket at mindrot.org

http://bugzilla.mindrot.org/show_bug.cgi?id=244 Summary: Remote port forwarding on solaris 8x86 doesn't work Product: Portable OpenSSH Version: 3.1p1 Platform: ix86 OS/Version: Solaris Status: NEW Severity: major Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org

http://bugzilla.mindrot.org/show_bug.cgi?id=326 Summary: Bug in AFS token forwarding Product: Portable OpenSSH Version: -current Platform: ix86 OS/Version: Linux Status: NEW Severity: normal Priority: P4 Component: ssh AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: alfw at

http://bugzilla.mindrot.org/show_bug.cgi?id=333 Summary: X11 forwarding not working in OpenSSH 3.4p1 Product: Portable OpenSSH Version: -current Platform: ix86 OS/Version: Linux Status: NEW Severity: major Priority: P2 Component: ssh AssignedTo: openssh-unix-dev at mindrot.org ReportedBy:

https://bugzilla.mindrot.org/show_bug.cgi?id=1539 Summary: double-free when failing to parse a forwarding specification given using ~C Product: Portable OpenSSH Version: 5.1p1 Platform: ix86 URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=50533 0 OS/Version: Linux Status:

http://bugzilla.mindrot.org/show_bug.cgi?id=832 Summary: X forwarding crashes on some applications Product: Portable OpenSSH Version: 3.8p1 Platform: ix86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: openssh-bugs at mindrot.org ReportedBy: ktaylor

https://bugzilla.mindrot.org/show_bug.cgi?id=1938 Bug #: 1938 Summary: EscapeChar sometimes don't work when using ControlMaster Classification: Unclassified Product: Portable OpenSSH Version: 5.8p1 Platform: ix86 OS/Version: Linux Status: NEW Severity: normal Priority: P2

http://bugzilla.mindrot.org/show_bug.cgi?id=185 Summary: --with-ipv4-default breaks X11-forwarding on HP-UX 10.20 Product: Portable OpenSSH Version: 3.1p1 Platform: HPPA OS/Version: HP-UX Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org

http://bugzilla.mindrot.org/show_bug.cgi?id=185 ------- Additional Comments From koenig at science-computing.de 2002-03-27 01:28 ------- I found a possible workaround for my problem: adding X11UseLocalhost no in sshd_conf for HP-UX 10.20 avoids the X11-forwarding problems. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the

hi everybody I'd like to ask how libvirtd influences net.ipv4.conf.all.forwarding, would you know? I've noticed that if I use host's bridge, therefor there is no <forward mode= > in my network then "net.ipv4.conf.all.forwarding" goes back to 0. Is this intended I wonder? Looks like libvirt decides it's user responsibility now. many thanks

Hi, I was just looking at the "CRAN Daily Package Check Results" [http://cran.r-project.org/src/contrib/checkSummary.html], and realized there are 1000 packages on CRAN as of today (look at row 3 in the table below). Yet another quite extraordinary milestone in R history. Last updated on 2007-04-12 11:48:32 Results for installing and checking packages using the three current flavors

Hi all. I've recently uploaded a package (bnlearn) to CRAN. It builds fine on both Linux (32 and 64 bit) and Windows, but fails on MacOSX ix86 because of C90 vs C99 issues: http://www.r-project.org/nosvn/R.check/r-patched-macosx-ix86/bnlearn-00install.html Since I've no MacOSX machine at hand, I would like to ask you: why is C99 not the default for gcc on MacOSX ix86? Is it safe to

https://bugzilla.mindrot.org/show_bug.cgi?id=1651 Summary: Possible race condition using local port forwarding with short lived connections Product: Portable OpenSSH Version: 5.2p1 Platform: ix86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: ssh

http://bugzilla.mindrot.org/show_bug.cgi?id=1267 Summary: PermitOpen - Multiple forwards don't works Product: Portable OpenSSH Version: v4.5p1 Platform: ix86 OS/Version: Cygwin on NT/2k Status: NEW Severity: security Priority: P2 Component: sshd AssignedTo: bitbucket at mindrot.org

I've been having a recurring problem using ssh and then scp. I've got 2 machines, client A and server B. I'm using OpenSSH on both. I've got a port-forward from server B in client A's "~/.ssh/config" file. Normally I login to server B via ssh from client A. With this session open (and a port forwarded) sometimes I go to a different terminal on client A and

http://bugzilla.mindrot.org/show_bug.cgi?id=530 Summary: problems with port forwarding Product: Portable OpenSSH Version: 3.5p1 Platform: ix86 OS/Version: FreeBSD Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: gilbert at

Dear list, I'd like to get rid off a couple of warnings that have appeared in checking my package on CRAN (I did not find them on my local machine before submission). What puzzles me is that different platforms return different warnings, only one of which I recognise as my obvious mistake. The check results are at http://cran.r-project.org/web/checks/check_results_planar.html

Hi, Has any one know how to skip ix86 packages from installation in Centos kickstart? Most of our machines have 64bit Intel/AMD CPUs, and it make non-sense to still keep 32bit compatibility. Even worse of i*86 packages is, when upgrade we have to recompile both ix86 version and x86_64 version to get an automatic yum upgrade. I know we could use 'exclude' option to exclude i*86 packages