summaryrefslogtreecommitdiff
path: root/regress/proxy-connect.sh
diff options
context:
space:
mode:
authorBen Lindstrom <mouring@eviladmin.org>2002-08-01 01:21:56 +0000
committerBen Lindstrom <mouring@eviladmin.org>2002-08-01 01:21:56 +0000
commit3ed6640532ea53bc37182262141c9e917a448025 (patch)
tree88ad1d4bbb9cd865c154f24ad12feafd7e302ccd /regress/proxy-connect.sh
parent18d2b5d399a6ee97c65a058c14054fd2da2b891a (diff)
- markus@cvs.openbsd.org 2002/07/24 16:11:18
[hostfile.c hostfile.h sshconnect.c] print out all known keys for a host if we get a unknown host key, see discussion at http://marc.theaimsgroup.com/?t=101069210100016&r=1&w=4 the ssharp mitm tool attacks users in a similar way, so i'd like to pointed out again: A MITM attack is always possible if the ssh client prints: The authenticity of host 'bla' can't be established. (protocol version 2 with pubkey authentication allows you to detect MITM attacks)
Diffstat (limited to 'regress/proxy-connect.sh')
0 files changed, 0 insertions, 0 deletions