similar to: [Bug 454] SSH doesn't consider distinguish ports for host-key verification

Displaying 20 results from an estimated 60000 matches similar to: "[Bug 454] SSH doesn't consider distinguish ports for host-key verification"

2002 Dec 09
0
[Bug 454] New: SSH doesn't consider distinguish ports for host-key verification
http://bugzilla.mindrot.org/show_bug.cgi?id=454 Summary: SSH doesn't consider distinguish ports for host-key verification Product: Portable OpenSSH Version: 3.4p1 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: ssh AssignedTo:
2002 Dec 10
2
[Bug 454] SSH doesn't consider distinguish ports for host-key verification
http://bugzilla.mindrot.org/show_bug.cgi?id=454 ------- Additional Comments From markus at openbsd.org 2002-12-10 20:14 ------- hm, i think about adding ManglePort=yes to the options. This option will create Hostkeyaliases on the fly if the port is != 22, and use 'foor.bar.com at portXXX' as an alias. ------- You are receiving this mail because: ------- You are the assignee for
2005 Apr 21
0
[Bug 454] SSH doesn't consider distinguish ports for host-key verification
http://bugzilla.mindrot.org/show_bug.cgi?id=454 djm at mindrot.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |DUPLICATE ------- Additional Comments From djm at mindrot.org 2005-04-21
2004 Jun 11
2
[Bug 454] SSH doesn't consider distinguish ports for host-key verification
http://bugzilla.mindrot.org/show_bug.cgi?id=454 ------- Additional Comments From robbat2 at gentoo.org 2004-06-11 15:34 ------- will this ever be implemented, or is it waiting for somebody to send in code for it? existing $HOME/.ssh/known_hosts file has the following format: 'host keytype keydata' where host is a either an IP or a name that resolves to the IP of the machine in
2005 Feb 25
0
[Bug 454] SSH doesn't consider distinguish ports for host-key verification
http://bugzilla.mindrot.org/show_bug.cgi?id=454 dave at dave.clendenan.ca changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dave at dave.clendenan.ca ------- You are receiving this mail because: ------- You are the assignee for the bug, or are
2006 Oct 07
0
[Bug 454] SSH doesn't consider distinguish ports for host-key verification
http://bugzilla.mindrot.org/show_bug.cgi?id=454 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED ------- Comment #11 from dtucker at zip.com.au 2006-10-07 11:35 ------- Change all RESOLVED bug to CLOSED with the exception
2003 Mar 27
1
[Bug 454] SSH doesn't consider distinguish ports for host-key verification
http://bugzilla.mindrot.org/show_bug.cgi?id=454 djm at mindrot.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |misiek at pld.org.pl ------- Additional Comments From djm at mindrot.org 2003-03-27 21:35 ------- *** Bug 523 has been marked as a
2003 Feb 07
0
[Bug 454] SSH doesn't consider distinguish ports for host-key verification
http://bugzilla.mindrot.org/show_bug.cgi?id=454 ------- Additional Comments From august at dce.chalmers.se 2003-02-07 21:03 ------- This feature would be useful for another issue as well: I have a dlink nat/gateway/switch/dhcp thingy, and a static IP. Behind it are about 3-5 machines. I can specify one IP on the inside that gets connections made to port 22 from the outside. But if I want
2004 Nov 23
0
[Bug 910] known_hosts port numbers
http://bugzilla.mindrot.org/show_bug.cgi?id=910 foomzilla at fuhm.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX | ------- Additional Comments From foomzilla at fuhm.net 2004-11-23 11:15
2005 Apr 21
11
[Bug 910] known_hosts port numbers
http://bugzilla.mindrot.org/show_bug.cgi?id=910 djm at mindrot.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |foomzilla at fuhm.net ------- Additional Comments From djm at mindrot.org 2005-04-21 18:16 ------- *** Bug 454 has been marked as a
2004 May 23
7
[Bug 872] SSH client fails for non-root users with "Host key verification failed"
http://bugzilla.mindrot.org/show_bug.cgi?id=872 Summary: SSH client fails for non-root users with "Host key verification failed" Product: Portable OpenSSH Version: 3.8.1p1 Platform: ix86 OS/Version: Linux Status: NEW Severity: major Priority: P2 Component: ssh
2009 Mar 19
2
ssh - alternate ports, and host verification
I have a centos box that will need to ssh into 2 other centos boxes (with keys). Now one of these boxes is a firewall, and another is a system behind the firewall. I have rules in my firewall to punch into the system behind the FW. Now if i connect to the IP (sine the public one is shared), anytime i connect to the other system, I get the host verification failed error and have to
2003 Oct 08
1
[Bug 734] Misleading error message when host key verification is impossible / SSH_ASKPASS impossible.
http://bugzilla.mindrot.org/show_bug.cgi?id=734 Summary: Misleading error message when host key verification is impossible / SSH_ASKPASS impossible. Product: Portable OpenSSH Version: 3.6.1p2 Platform: All OS/Version: Linux Status: NEW Severity: trivial Priority: P5 Component: ssh
2023 Mar 03
2
[Bug 3546] New: Use SHA2 in ssh-keygen key verification
https://bugzilla.mindrot.org/show_bug.cgi?id=3546 Bug ID: 3546 Summary: Use SHA2 in ssh-keygen key verification Product: Portable OpenSSH Version: 8.7p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: ssh-keygen Assignee: unassigned-bugs at
2002 Oct 18
3
Host Key Verification failed - ssh via cgi
hi, my scenario is this: i have a cgi (on host1) that executes ssh (as userxyz) to a remote server (host2), executes a command to retrieve some data and outputs them to the local browser. on host1: #!/usr/bin/perl -w ... $output = `/usr/local/bin/ssh -l userxyz -x host2 ls -l` ... but i get "Host Key Verification failed" on my apache's error_log. i can do it on the command line,
2013 Feb 23
5
[Bug 2074] New: Host key verification incorrectly handles IPv6 addresses
https://bugzilla.mindrot.org/show_bug.cgi?id=2074 Bug ID: 2074 Summary: Host key verification incorrectly handles IPv6 addresses Classification: Unclassified Product: Portable OpenSSH Version: 6.1p1 Hardware: All OS: Linux Status: NEW Keywords: needs-release-note
2008 Jan 04
2
[Bug 1426] New: ssh key verification hint (on remote side)
https://bugzilla.mindrot.org/show_bug.cgi?id=1426 Summary: ssh key verification hint (on remote side) Classification: Unclassified Product: Portable OpenSSH Version: 4.7p1 Platform: Other OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: sshd AssignedTo: bitbucket at
2012 Mar 16
1
Host Key verification issue
Hello, I have script that I run remotely on a server, using ssh config with a 'command' call in the authorized keys file. I can successfully run this from one of my servers, but when I try from 2 other machines, I receive a Host Key Verification Failed error. When I remove the 'command' from the call from authorized keys on the remote server, I can successfully connect to the
2006 Mar 09
0
If you become the error message: "Host key verification failed". then is this help is for you
Hello, Dom0 = Debian_Base (192.168.0.1) DomU = Debian_SQL (192.168.0.2) DomU = Debian_WEB (192.168.0.3) Debian_Base -> Debian_SQL [OK] Debian_Base -> Debian_WEB [OK] Debian_SQL -> Debian_Base [ERROR] Debian_WEB -> Debian_Base [ERROR] Debian_SQL <-> Debian_WEB [ERROR] [ERROR] = ssh "Host key verification failed" Check your entry in /etc/inittab and check this
2023 Aug 18
1
Host key verification (known_hosts) with ProxyJump/ProxyCommand
On 18/8/23 15:39, Darren Tucker wrote: >> Host mytarget >> Hostname 172.16.1.2 >> ProxyJump user2 at bastion2 > I think you just need "HostKeyAlias mytarget" here. Ahh, in my scanning through the `ssh_config` manpage, I missed this, and change logs seem to indicate this feature has been around since at least 2017, so should not cause